OPNsense Forum

English Forums => General Discussion => Topic started by: bimmerdriver on June 03, 2018, 02:00:37 am

Title: New OPNsense User
Post by: bimmerdriver on June 03, 2018, 02:00:37 am
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.
Title: Re: New OPNsense User
Post by: marjohn56 on June 03, 2018, 09:22:12 am
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.
Title: Re: New OPNsense User
Post by: bimmerdriver on June 03, 2018, 07:13:19 pm
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?
Title: Re: New OPNsense User
Post by: marjohn56 on June 03, 2018, 07:46:29 pm
Yes, you will need to switch to 18.7.b, and keep it up to date. Should have something to test over the next week or so, I'll pm you with info as and when.