[SOLVED] IPv6 working only on one interface

Started by chris42, January 19, 2023, 08:26:30 PM

Previous topic - Next topic
January 19, 2023, 08:26:30 PM Last Edit: January 19, 2023, 10:26:40 PM by chris42
Hi there,
I have a bit of a trouble pinning down an issue.
Configured IPv6 and normally it was working on 2 interfaces. A LAN with physical connection and a WLAN_GUEST, based on a vlan coming from an access point.

I get an IPv6 from my ISP and a /56 prefix. Can easily ping IPv6 addresses from opnsense.
Also I get IPV6 working in the WLAN_GUEST. Devices get an IPv6 and can communicate with websites on that.

But for some reason devices in the LAN are not getting any IPv6. I compared all the configs and they seem to be the same.
Only difference is the different Prefix ID.

I know IPv6 was working in LAN before but I have no clue on how to debug this now. Does anyone has a hint?

Kind regards
  Chris

So I checked a few logs and suspect that it is a routing problem.

In dhcpd logs I get everytime LAN device (Prefix ID 2) asks for an IP:

[meta sequenceId="1"] Solicit message from fe80::xxx:1c96 port 546, transaction ID 0x54B07100
[meta sequenceId="2"] Picking pool address 2001:xxx:5002::2000
[meta sequenceId="3"] Advertise NA: address 2001:xxx5002::2000 to client with duid xxx iaid = xxx valid for 7200 seconds
[meta sequenceId="4"] Sending Advertise to fe80::xxx:1c96 port 546
[meta sequenceId="5"] send_packet6: No route to host


Checking the routes there is actually a difference:

ipv4 192.168.2.0/24 link#10 U NaN 1500 bridge0 LAN
ipv4 192.168.3.0/24 link#8 U NaN 1500 igb1_vlan3 WLAN_AP_GUEST
ipv6 2001:xxx:5002::/64 link#10 U NaN 1500 bridge0 LAN
ipv6 2001:xxx:5003::/64 link#8 U NaN 1500 igb1_vlan3 WLAN_AP_GUEST
ipv6 fe80::%igb1_vlan3/64 link#8 U NaN 1500 igb1_vlan3 WLAN_AP_GUEST


All routes are automatically generated and I am too much of a noob to figure what that means.

Ok, following the white rabbit to github I found the solution in:
https://github.com/opnsense/core/issues/5651

LAN network is build on a bridge to combine different ports. The bridge needs to have link-local addresses enables. After that a reboot sets everything in order.

Apparently I did not need help on debugging.  ;D