Archive > 20.1 Legacy Series

IPV6 - RA stopped announcing gateway to windows clients

(1/1)

Quiksmage:
Hi,
I recently setup VLANs and was trying to get IPV6 working on each one.
Originally, by default my WAN was set to DHCPv6 with a prefix delegation size of 64
My LAN was to track WAN with ID 0.

This worked great and RA worked for me just fine. IPv6 worked great on the LAN.

I noticed that my LAN was given a /56 address and was reading up to hand a /64 out to each vlan.

Since it was handing a /56 to my LAN, I changed the WAN DHCVPv6 configuration to /56
and kept my LAN settings the same, tracking WAN with ID 0.
I added each VLAN with a corresponding ID 1, 2, 3, 4, 5.

Every interface now has its own /64 and could ping out to an external ipv6 address, great!
What I noticed was that RA wasn't handing out a gateway to my windows clients anymore.
I could manually ping the assigned public IPv6 address on the interface as well as the fe80 address without issue.
If i manually set the gateway of my client to this ipv6 address, everything works well.
I can see that the RA is getting received, since I added DNS entries and those are populating on the client. For whatever reason, the windows clients aren't receiving the fe80 address as their ipv6 gateway.
curiously enough my debian client is working perfectly right now.

Thanks in advance for any help!

Quiksmage:
Evidently restarting my clients fixed the issue... hm. I guess this is resolved :)

Navigation

[0] Message Index