Messages

1

22.7 Legacy Series / Re: OPNSense as Virtual Machine

« on: November 11, 2022, 09:53:52 pm »

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.

2

22.7 Legacy Series / Re: OPNSense as Virtual Machine

« on: November 09, 2022, 05:34:06 pm »

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.

3

22.7 Legacy Series / Re: WAN_DHCP6 Gateway Stuck Pending

« on: November 06, 2022, 09:25:35 pm »

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.

4

22.7 Legacy Series / WAN_DHCP6 Gateway Stuck Pending

« on: November 05, 2022, 05:22:46 am »

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.

5

22.7 Legacy Series / Re: Development versions: Alpha, Beta and Release Candidate explained

« on: February 09, 2022, 07:16:51 pm »

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.

6

21.7 Legacy Series / Re: ICMPv6 /RFC4890 4.3.1 & 4.3.2

« on: November 13, 2021, 11:12:20 pm »

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.

7

21.7 Legacy Series / Re: dpinger not running for WAN_DHCP6

« on: October 27, 2021, 05:32:23 pm »

email sent.

8

21.7 Legacy Series / Re: dpinger not running for WAN_DHCP6

« on: October 20, 2021, 06:45:38 pm »

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.

9

21.7 Legacy Series / dpinger not running for WAN_DHCP6

« on: October 15, 2021, 03:33:03 am »

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?

10

21.7 Legacy Series / Re: 21.7.1 on Hyper-V Gen 2

« on: September 17, 2021, 06:45:43 pm »

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.

11

21.7 Legacy Series / Re: Page Unresponsive

« on: August 17, 2021, 05:12:49 pm »

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.

12

21.7 Legacy Series / Page Unresponsive

« on: August 14, 2021, 06:21:14 pm »

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.

13

21.7 Legacy Series / Re: Regarding IPv6 support

« on: August 11, 2021, 04:14:44 pm »

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.

14

21.1 Legacy Series / Re: Update Problems

« on: May 14, 2021, 04:17:08 pm »

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.

15

21.1 Legacy Series / Re: Update Problems

« on: May 13, 2021, 02:47:06 am »

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?