Messages

The problem does not occur on the license page.

There are no errors, other than the pop-up from chrome. I don't see this on xxsense or any other functioning website and it didn't used to occur for OPNsense. If it walks like a bug and quacks like a bug, it's probably a bug.

Thanks for the reply.

I think if there was an expired cookie, chrome would report it. The GUI allows not logging out, so it should work. In fact it used to work. It hasn't always exhibited this behaviour.

For a test, I switched to the license page to see if the same thing happens.

For quite some time now (months), I've been experiencing a "Page Unresponsive" message from Chrome when I try to refresh the dashboard after disuse. (I leave it logged in.) This is consistent and it takes approximately 2 minutes from when I refresh to when the message clears and the display actually refreshes.

I'm running OPNsense on a Windows Hyper-V Server 2022 and the client is Windows 10 Pro running on the same server. There are no other clients. The OPNsense VM has plenty of resources and the server is also not heavily loaded.

A screen capture is attached.

I'm happy to report that this is fixed!

Thank you.

No problem, I've been away also.

I downloaded the most recent iso and did a clean install. The version is 23.7.

I switched to development and did an update. The version is 23.7.r_56. Is that 23.7-RC1?

Sorry for the delay on my part. I haven't had much time lately to look at this.

Over the past few days, I updated my test systems to the latest version. The problem is the same for the release version and the development version.

In both cases, unless I manually enter the gateway address, dpinger will report that the gateway is offline. Also, in both cases, the address of the WAN_DHCP6 gateway is reported as ~.

Would you like to test the latest release version or development version? I can provide either.

As others have said, if you want to use OPNsense as a router / firewall for other devices, you need a dedicated WAN interface. If you're running it on a laptop with only one ethernet port, you could get a USB ethernet interface.

To be honest, a laptop is far from an ideal computer to run a router, unless you are only using it with virtual clients.

Is it possible to install OPNSense as a Virtual Machine running on a Windows 10 PC? Can someone send me a link on how to do it.

It runs on Hyper-V, so yes, it should be able to run on a PC running Windows 10 Pro.

I'm with the same ISP. The only difference is gigabit GPON rather than VDSL. The gateway has a different address, but it's still a Nokia, as it was before. This ISP requires the DHCPv6 solicit / advertise, request / reply sequence to take place before the ICMP router solicitation / router advertisement sequence. The router will not respond to RS with RA if a prefix has not been delegated.

The behaviour I'm observing is the same for the release version and the development version. I think it started when BSD was upgraded to version 14. I think it may have something to do with the M and O flags not being set in the RA message.

If you would like to take a look at the system, it can be arranged.

I changed internet service from VDSL to fibre recently and was reminded there is still a problem with OPNsense not being able to determine the IPV6 gateway address, resulting in the WAN_DHCP6 gateway not working unless the monitor IP address is manually set to the address of the gateway. When my service was upgraded, the IP address was still pointing at the address of the old gateway, which is no longer pingable. I cleared the address and rebooted to see if OPNsense could determine the address and it could not, so again, I had to manually set the address in gateway settings. I still have a pfSense system running and since it upgraded to BSD 14, it's having the same problem.

If there is anything I can do to help determine why this is happening, let me know.

It would be great if the change log included a reference to the opnsense version so it would more obvious if it's new. Currently, there is no obvious way to know (at least not obvious to me). Lately, I've inadvertently reinstalled the same version several times.

For the windows firewall, I enable the existing rule, "Virtual Machine Monitoring (Echo Request - ICMPv6-In)".

With that and a rule in OPNsense to allow ICMP echo requests, I get 20/20.

email sent.

Hi Franco,

I installed the patch and rebooted. The behaviour is the same.

Previously, I had reverted to the previous checkpoint and upgraded again. dpinger started properly after the initial reboot immediately after the upgrade. When I rebooted it again, dpinger did not start.

Let me know if I can provide any further information or if you want, you can take a look at the system remotely.

Cheers.

I updated my test system from 21.7.r_210 to 21.7.r_228 and dpinger is not running. I can't start it from the dashboard and rebooting doesn't help. To be sure nothing had gotten corrupted, I restored to the r_210 checkpoint. The problem didn't exist. I upgraded it to r_228 again. dpinger worked until the first reboot, then after rebooting, it would not start again.

This is in the log:

/status_services.php: The WAN_DHCP6 IPv6 gateway address could not be found, skipping.   

Any suggestions?