#radvd — Public Fediverse posts

#radvd 2.21 has been released ( #RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6 / #CVE / #SecurityVulnerability ) https://radvd.litech.org/

#radvd 2.21 has been released ( #RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6 / #CVE / #SecurityVulnerability ) https://radvd.litech.org/

#radvd 2.21 has been released ( #RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6 / #CVE / #SecurityVulnerability ) https://radvd.litech.org/

#radvd 2.21 has been released ( #RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6 / #CVE / #SecurityVulnerability ) https://radvd.litech.org/

#radvd 2.21 has been released ( #RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6 / #CVE / #SecurityVulnerability ) https://radvd.litech.org/

Looks like I had to bump the value for AdvDefaultLifetime from 45 s to 1800 s in #radvd. Now I get a #ipv6 default gateway, let's see if it sticks when I put down my phone for a while.

#IPv6 (zumindest via #radvd) ist bei uns nun temporär deaktiviert wegen #MTU Problemen, scheinbar zu diversen #Microsoft Seiten/Diensten. Dies macht sich dadurch bemerkbar, dass insbesondere größere Dateien/Seiteninhalte hier nicht geladen werden. Zur Zeit sieht es für uns aus, als ob sich #Microsoft nicht an IPv6-Standards hält (und insbesondere ICMPv6 Packet Too Big Nachrichten unkorrekterweise ignoriert). Aber wir sind da dran, das zu klären.

Jetzt nur über IPv4 sollte es aber vorerst gehen.

Help. How do I configure #radvd so my new S25 #android phone gets an #ipv6 default gateway? Or is it a #samsung issue?

#radvd 2.20 has been released (#RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6) https://radvd.litech.org/

#radvd 2.20 has been released (#RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6) https://radvd.litech.org/

#radvd 2.20 has been released (#RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6) https://radvd.litech.org/

#radvd 2.20 has been released (#RouterAdvertisementDaemon / #RouterAdvertisement / #IPv6) https://radvd.litech.org/

Anyone know if it's possible to tell #radvd to use my #WAN as the source of #IPv6 addresses? #Networking #Linux #NixOS

If you have clients periodically lose the IPv6 default route, and are using #radvd to implement #SLAAC, the reason for the trouble can be that the net.ipv6.conf.<laniface>.forwarding is incorrectly configured as 0.

If you have clients periodically lose the IPv6 default route, and are using #radvd to implement #SLAAC, the reason for the trouble can be that the net.ipv6.conf.<laniface>.forwarding is incorrectly configured as 0.

If you have clients periodically lose the IPv6 default route, and are using #radvd to implement #SLAAC, the reason for the trouble can be that the net.ipv6.conf.<laniface>.forwarding is incorrectly configured as 0.

If you have clients periodically lose the IPv6 default route, and are using #radvd to implement #SLAAC, the reason for the trouble can be that the net.ipv6.conf.<laniface>.forwarding is incorrectly configured as 0.

If you have clients periodically lose the IPv6 default route, and are using #radvd to implement #SLAAC, the reason for the trouble can be that the net.ipv6.conf.<laniface>.forwarding is incorrectly configured as 0.

Is it just me or is #radvd "::/64" prefix autodiscovery broken since it doesn't limit the prefix length to 64? If the ISP offers a wider than 64-bit block the autodiscovery will just pick that value as-is and advertise it. At least macOS and iOS will reject such overly wide RA.

One fix for this is to just use explicit prefix stanza with "address::/64" but this requires that the radvd.conf is generated runtime based on the prefix obtained from the ISP.

Since I didn't feel like having to keep regenerating the radvd.conf dynamically I just patched the send.c to limit the xprefix.PrefixLen to 64.

I'm sure there's a better way but this problem looked like a nail to me.

#IPv6 #SLAAC

Is it just me or is #radvd "::/64" prefix autodiscovery broken since it doesn't limit the prefix length to 64? If the ISP offers a wider than 64-bit block the autodiscovery will just pick that value as-is and advertise it. At least macOS and iOS will reject such overly wide RA.

One fix for this is to just use explicit prefix stanza with "address::/64" but this requires that the radvd.conf is generated runtime based on the prefix obtained from the ISP.

Since I didn't feel like having to keep regenerating the radvd.conf dynamically I just patched the send.c to limit the xprefix.PrefixLen to 64.

I'm sure there's a better way but this problem looked like a nail to me.

#IPv6 #SLAAC

Is it just me or is #radvd "::/64" prefix autodiscovery broken since it doesn't limit the prefix length to 64? If the ISP offers a wider than 64-bit block the autodiscovery will just pick that value as-is and advertise it. At least macOS and iOS will reject such overly wide RA.

One fix for this is to just use explicit prefix stanza with "address::/64" but this requires that the radvd.conf is generated runtime based on the prefix obtained from the ISP.

Since I didn't feel like having to keep regenerating the radvd.conf dynamically I just patched the send.c to limit the xprefix.PrefixLen to 64.

I'm sure there's a better way but this problem looked like a nail to me.

#IPv6 #SLAAC

Is it just me or is #radvd "::/64" prefix autodiscovery broken since it doesn't limit the prefix length to 64? If the ISP offers a wider than 64-bit block the autodiscovery will just pick that value as-is and advertise it. At least macOS and iOS will reject such overly wide RA.

One fix for this is to just use explicit prefix stanza with "address::/64" but this requires that the radvd.conf is generated runtime based on the prefix obtained from the ISP.

Since I didn't feel like having to keep regenerating the radvd.conf dynamically I just patched the send.c to limit the xprefix.PrefixLen to 64.

I'm sure there's a better way but this problem looked like a nail to me.

#IPv6 #SLAAC

Is it just me or is #radvd "::/64" prefix autodiscovery broken since it doesn't limit the prefix length to 64? If the ISP offers a wider than 64-bit block the autodiscovery will just pick that value as-is and advertise it. At least macOS and iOS will reject such overly wide RA.

One fix for this is to just use explicit prefix stanza with "address::/64" but this requires that the radvd.conf is generated runtime based on the prefix obtained from the ISP.

Since I didn't feel like having to keep regenerating the radvd.conf dynamically I just patched the send.c to limit the xprefix.PrefixLen to 64.

I'm sure there's a better way but this problem looked like a nail to me.

#IPv6 #SLAAC