Messages

There is a text sizing problem on Services: DHCPv6: Leases. Depending on the zoom setting of the browser, the text goes off the screen.

Here is a screen capture:

After I updated my system, the Windows 10 computer I'm using on it had no IPv6 address. I had to disable and enable the adapter, then everything was normal.

I am currently running this release:

OPNsense 18.7.r_10-amd64
FreeBSD 11.1-RELEASE-p11
OpenSSL 1.0.2o 27 Mar 2018

When I click check for updates, I get this message: This software release has reached its designated end of life. The next major release is: 18.7.r1

Often when I click check for updates, there is a message that the package manager is not running. If I click it again, the message goes away.

Right now, it's saying there are 10 packages. If I upgrade them, it's as if I didn't upgrade. It still gives the message, This software release has reached its designated end of life, the next major release is 18.7.r1.

Is something wrong with my installation? I was previously running the release version. Maybe when I switched to the development version it did not install properly?

I'm not asking a rhetorical question or trying to start a controversy, but I'm wondering if someone would provide an explanation of why one would go with OPNsense rather than pfSense. I gather there are some philosophical differences, functionality differences, different objectives, etc., but these are not obvious merely by comparing the GUIs of OPNsense and pfSense. I would be interested to have a better understanding of this.

For the record, the gateway status widget has worked fine on pfsense for as long as I've been using it. Considering neither the ipv4 or ipv6 gateways are reporting valid data, I think something is wrong.

Here is the result from pinging the gateway using its link-local address from the opnsense wan using its link-local address as the source. As you can see, it works fine.

PING6(56=40+8+8 bytes) fe80::215:5dff:fe5c:e233%hn0 --> fe80::ea4:2ff:fe29:5001%hn0
16 bytes from fe80::ea4:2ff:fe29:5001%hn0, icmp_seq=0 hlim=255 time=4.632 ms

--- fe80::ea4:2ff:fe29:5001%hn0 ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 4.632/4.632/4.632/0.000 ms

On my system, the gateway status widget seems to be not working. For both the ipv4 and ipv6 gateways, the RTT is zero, which isn't possible. On my pfsense systems, it's around 6 ms for both. Also, the ipv6 gateway doesn't show the address of the gateway, which should be a link-local address.

DHCPv6 does not appear to be working. IPv6 is working on the client, but it has a SLAAC address, not a DHCPv6 address / lease.

There is no manual dhcpd config for IPv6 when using track6, it causes issues. However as a couple of others have requested this I've started working on it... keep your VM warm for some testing. I'll pm you when I'm ready to send you something.

Thanks for the explanation. I would be happy to do some testing. I'm currently running 18.1.8. Should I switch over the development version?

I'm not a fan of the new forum either.

I'm a pfsense user, taking a first look at OPNsense. I'm running pfsense and OPNsense on Windows Server 2012R2 Hyper-V. All of the vms are connected to a shared virtual switch, which is connected to a physical NIC. The NIC is connected to a port of my modem, which is bridged. My ISP is Telus and their edge router delegates /56 prefixes. The edge router is configured to require the "directly send solicit" setting. It will not respond to an RS until it has delegated a prefix. I have one live pfsense system, running 2.4.3-p1, one test pfsense system running 2.4.4 development and one OPNsense system running 18.1.8. (Four /56 prefixes including the modem.) The client is a vm running windows 10. It's connected to the OPNsense LAN using a virtual switch.

I'm posting to report my feedback from installing OPNsense.

The "easy" installer hung. The work-around was to change the font from the default to 8x14. I found the work-around using google.

I initially ended up with OPNsense running off the CD, not actually installed. Maybe this is due to the above issue.

DHCPv6 does not appear to be working. IPv6 is working on the client, but it has a SLAAC address, not a DHCPv6 address / lease.

Other than those issues, it seems to be working okay. I will provide other feedback after I spend more time looking at the GUI.