[Solved] Clients don't get an IPv6 address

[tdc]

Just wanted to add that I am having the same problem. This is on a completely fresh installation of 22.1, no upgrade involved. I had clients getting IPv6 addresses when my LAN was on a single interface, but when LAN is configured as a bridge, these clients are no longer getting IPv6 addresses. So at least in my case, the bridge configuration is the proximate cause.

[Rob_H]

I was having a similar issue. Clients weren't getting an IPv6 address from my bridged LAN interface. Solved it by going to bridge settings, turning on Enable link-local address, reboot, and it works.  :)

[ozboss]

I was having a similar issue. Clients weren't getting an IPv6 address from my bridged LAN interface. Solved it by going to bridge settings, turning on Enable link-local address, reboot, and it works.  :)

You are a hero  :D Thank you Rob that fixed it for me as well.
Does anybody know why this is required?

[meyergru]

For example, radvd needs a MAC to assign an EUI-64, because the lower 64 bits are made up based on that.
Since bridges do not have a MAC per default, that assignment cannot be made.

[franco]

For some reason on FreeBSD 13 the link-local setting might be missing from network devices unless explicitly configured leading to these types of errors. That includes bridges that have this optional setting and also parent WAN interfaces that do not have IPv6 configured which lead to interruption of manual prefix tracking on LAN in some cases.


Cheers,
Franco

[reven]

I was having a similar issue. Clients weren't getting an IPv6 address from my bridged LAN interface. Solved it by going to bridge settings, turning on Enable link-local address, reboot, and it works.  :)

I just created an account to say thank you. I've been after this issue for days!

[rookie]

I had this issue too and enabled link-local address on all my bridge interfaces. That solved the issue.

Many Thanks to Rob_H!

[franco]

Or thanks to the contributors of the feature :P


Cheers,
Franco