Messages

The middleware has probably destroyed and recreated the bridge interface. I recommend a reboot after network topology changes.

This should be the case.  But restart a router seems a bit over for this case.

Hi,

I create a bridge with 2 members: OPT1 and OPT2.  I attach a static IPv4 address: 192.168.0.1/24 to the bridge interface.  I also enable the DHCP service for the bridge interface.  Now, hosts connected to opt1 or opt2 can get the IP address lease from the DHCP service.

If I add new member OPT3 to the bridge, I notice the DHCP service stop serving DHCP request although it still active.

I found an error log found in DHCP service: `receive_packet failed on bridge0: Device not configured`

If I restart the DHCP service manually, the DHCP server work as normal.

I am trying NPTv6.  As the windows IPv6 client received both GUA and ULA address, I couldn't confirm if IPv6 traffic was evaluated against NPT rule defined in OPNsense.

My next use case is I have configure a IPv6 load balance multi WAN.  I have 3 WAN connections.  All 3 WAN offered only /64 IPv6 GUA.  I think the only option for internal host to utilize the IPv6 multi wan is via ULA.

Hi,

When configure the IPv6 network access via PPPoE to my ISP, I am able to obtain an GUA IPv6 address (/64) on LAN interface.  The /64 public GUA prefix do advertise to my Windows configure the IPv6 only network.  The Windows OS have a unique GUA IPv6 too.  It can access to IPv6 internet too, so far so good.

Next, I try ULA IPv6.  I configure a virtual IP on the LAN interface with ULA IPv6 fd01:2:3:4::1/64.  Restart the radvd service, the Windows can has both GUA and ULA address.

Can OPNsense configure to advertise only ULA to the Windows client only?