Messages

I haven't tried a clean install for a while, but the last times I've tried, the installation froze at a couple of places, requiring CTL-C and login to proceed. The installer hasn't worked cleanly for a long time. Possibly what you are seeing is related.

This is happening on a consistent basis, every day. It used to be that I would have to login every day. That's not happening, but I'm seeing this page unresponsive message. I wonder if it's related.

I'm running 21.7.r_95 and accessing the GUI using a Windows 10 21H1 client on a hyper-v server using the latest version of chrome. Since updating OPNsense, when I leave the GUI overnight and refresh it the next day, the GUI is hung and chrome displays the message page unresponsive. This has happened several times since I updated. Usually, I just kill the chrome tab and open another one, which works fine.

Today, I left it running and looked more closely. Using the windows task manager, I saw that initially, the system interrupts background process was using 100% of the CPU. Later, this transitioned to the desktop window manager and chrome. After a few minutes, the GUI came back to life. I'm wondering if anyone else is experiencing this.

I've been using IPv6 since I started using OPnsense and I think it works very well. Yes, some of the settings aren't obvious and yes, probably some improvements can be made, but to suggest that it's "not ready for production" isn't reasonable.

IPv6 is stable, so that's not the problem. When I first reported this, the problem appeared to be DNS related. After the reinstallation, DNS is working fine. I did some additional testing and found that I could update from the console, just not from the web GUI.

After I got DNS working by resetting to defaults, I did a clean install of 21.1. Then I tried switching to the development version. After I changed to development, I pressed save. There was a small amount of CPU activity, but the browser did not update. I left it for 30 minutes or so, then rebooted. It changed had changed to the development version. I tried another clean install of 21.1. This time, I updated to 21.1.5, then changed to the development version. The same thing happened. I rebooted and it changed to the development version. I tried to update again and it hangs indefinitely on the update page. DNS is working, but the updater seems to have a problem.

Is there any information such as logs that I can post to understand what is causing this?

Under Interfaces (for LAN), you probably need to tick the box to allow manual adjustment of dhcpv6 for it to show under services.

Thank you for the reply. I did not know about this change in settings. Initially, I just enabled the manual mode and then noticed that DHCPv6 stopped working. I went into the DHCPv6 settings and enabled the server, but it still wasn't working. Finally, I noticed that RA was disabled.

IMO, it would be more straight-forward if enabling manual mode would cause the settings for DHCPv6 and RA to be set to the same settings as they were in auto-mode. They must have been abled in auto-mode, otherwise DHCPv6 would not have been working. Anyway, not a big deal...

I just did a clean reinstall of 21.1. Normally, I prefer to display lease times in local time, not UTC. I found the DHCPv4 [LAN] settings in the usual place, but when I looked for the DHCPv6 settings, I noticed there is no page for [LAN] settings. Have these settings been moved somewhere else?

I saved the settings, then restored default settings, then reloaded only a few settings from the saved settings, such as CA and certificate, then I manually configured the DHCPv6 WAN settings. After that, it's working again. Very strange that this happened, since it was working up to an update in April (a bit over two weeks ago), then it stopped working. Even more strange, since whatever happened seems to have affected both the release and development systems. I haven't made any changes to either of these systems in months, other than keeping them updated.

No changes since installation. Very simple systems, no packages, mostly using default settings.

I can look it up using nslookup, but dns lookup from within opnsense isn't working. I tried restarting unbound, but that made no difference. Really strange.

I have a couple of OPNsense VMs, one running the release version and the other running the development version. This morning, I tried to update the development version from the web user interface and encountered errors with the repository. I tried to update the release version with the web user interface and encountered similar errors. I've attached screen captures. Is there a problem with my systems?

Going to System / Access / Users / root and saving fixed it. I didn't change anything and nothing changed in the config.xml. :o

(I saw the same behavior when using the local VGA console and echo $shell told me that it was actually running /bin/csh.)

Cheers

Maurice

I'm experiencing the same problem and saving the root user did not make any difference.

For what it's worth, I noticed that the most recent update before this happened was that the SSH package was reinstalled.

I updated my development system to OPNsense 21.7.a_314. After the update, when I login to the console, it goes directly into shell mode. There are no obvious other problems. I've never encountered this before. Is this a known problem?

That means Netgate convinced FreeBSD to do what Scott Long suggested. Oh man, get ready for more shit in the next couple of years. This is just the beginning of the drama.


Cheers,
Franco

I'm not sure which is worse, that Netgate rammed their broken implementation of Wireguard into FreeBSD a few weeks before a release, expecting it to be part of the release, or that FreeBSD let them. It's amazing.