#slaac — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #slaac, aggregated by home.social.
-
About fucking time... Android finally doing proper DHCPv6. When this is live on my phone I can turn off SLAAC, and not have Windows insist on using it (yes, there's meant to be ways to stop Windows from using SLAAC, so it only uses DHCPv6, but I never saw any of them work). *I* don't want 'random' addresses, I want predictable ones for firewalling and ACLs: https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
-
About fucking time... Android finally doing proper DHCPv6. When this is live on my phone I can turn off SLAAC, and not have Windows insist on using it (yes, there's meant to be ways to stop Windows from using SLAAC, so it only uses DHCPv6, but I never saw any of them work). *I* don't want 'random' addresses, I want predictable ones for firewalling and ACLs: https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
-
About fucking time... Android finally doing proper DHCPv6. When this is live on my phone I can turn off SLAAC, and not have Windows insist on using it (yes, there's meant to be ways to stop Windows from using SLAAC, so it only uses DHCPv6, but I never saw any of them work). *I* don't want 'random' addresses, I want predictable ones for firewalling and ACLs: https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
-
About fucking time... Android finally doing proper DHCPv6. When this is live on my phone I can turn off SLAAC, and not have Windows insist on using it (yes, there's meant to be ways to stop Windows from using SLAAC, so it only uses DHCPv6, but I never saw any of them work). *I* don't want 'random' addresses, I want predictable ones for firewalling and ACLs: https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
-
About fucking time... Android finally doing proper DHCPv6. When this is live on my phone I can turn off SLAAC, and not have Windows insist on using it (yes, there's meant to be ways to stop Windows from using SLAAC, so it only uses DHCPv6, but I never saw any of them work). *I* don't want 'random' addresses, I want predictable ones for firewalling and ACLs: https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html?m=1
-
A fun hour or so of troubleshooting #IPv6 just to realise that I'd forgotten to reconfigure the #dhcpPrefixDelegation onto the #vif after making it #vlanaware #edgerouter #slaac #ubiquity
-
A fun hour or so of troubleshooting #IPv6 just to realise that I'd forgotten to reconfigure the #dhcpPrefixDelegation onto the #vif after making it #vlanaware #edgerouter #slaac #ubiquity
-
A fun hour or so of troubleshooting #IPv6 just to realise that I'd forgotten to reconfigure the #dhcpPrefixDelegation onto the #vif after making it #vlanaware #edgerouter #slaac #ubiquity
-
A fun hour or so of troubleshooting #IPv6 just to realise that I'd forgotten to reconfigure the #dhcpPrefixDelegation onto the #vif after making it #vlanaware #edgerouter #slaac #ubiquity
-
Service:
Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:
Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".
Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.
-
Service:
Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:
Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".
Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.
-
Service:
Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:
Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".
Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.
-
Service:
Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:
Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".
Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.
-
Service:
Hin und wieder wird bei DYNDNS eine stabile Host-ID verlangt:
Linux allgemein:
man ip-token
ip token set ::3000 dev eth0
oder im NetworkManager:
https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/nm-settings-nmcli.html[ipv6]
addr-gen-mode=eui64
method=auto
token=::3333Damit kommt man ohne DHCPv6 aus und die Hosts müssen nicht ihre MAC-Adresse "verraten".
Wenn jemand die äquivalenten Einstellungen für andere OS oder Tools kennt, kann ja gern damit darauf antworten.
-
I had a presentation about registering #hostname on #ipv6, when #SLAAC is used. Is there any attempt to register name to local #dns server, when I am on IPv6 only network? I think dynamic update over TCP would be similar to #dhcp based registration Dnsmasq does automatically. Is there any system attempting it already?
-
I had a presentation about registering #hostname on #ipv6, when #SLAAC is used. Is there any attempt to register name to local #dns server, when I am on IPv6 only network? I think dynamic update over TCP would be similar to #dhcp based registration Dnsmasq does automatically. Is there any system attempting it already?
-
I had a presentation about registering #hostname on #ipv6, when #SLAAC is used. Is there any attempt to register name to local #dns server, when I am on IPv6 only network? I think dynamic update over TCP would be similar to #dhcp based registration Dnsmasq does automatically. Is there any system attempting it already?
-
I had a presentation about registering #hostname on #ipv6, when #SLAAC is used. Is there any attempt to register name to local #dns server, when I am on IPv6 only network? I think dynamic update over TCP would be similar to #dhcp based registration Dnsmasq does automatically. Is there any system attempting it already?
-
I had a presentation about registering #hostname on #ipv6, when #SLAAC is used. Is there any attempt to register name to local #dns server, when I am on IPv6 only network? I think dynamic update over TCP would be similar to #dhcp based registration Dnsmasq does automatically. Is there any system attempting it already?
-
It was really cumbersome to configure IPv6 on my proxmox playground box.
Yes I do want this box to act as a router for the hosted VMs, but yes I also want SLAAC to get the default route and DNS!
Long story short, in a pre-up I had to add a "echo 0" to the forwarding sysctl for the wan interface.
But from my understanding, this interface is still forwarding IPv6 packets for the VMs.At least now it's working, and also tested that the configuration is also correctly applied upon a reboot.
-
It was really cumbersome to configure IPv6 on my proxmox playground box.
Yes I do want this box to act as a router for the hosted VMs, but yes I also want SLAAC to get the default route and DNS!
Long story short, in a pre-up I had to add a "echo 0" to the forwarding sysctl for the wan interface.
But from my understanding, this interface is still forwarding IPv6 packets for the VMs.At least now it's working, and also tested that the configuration is also correctly applied upon a reboot.
-
It was really cumbersome to configure IPv6 on my proxmox playground box.
Yes I do want this box to act as a router for the hosted VMs, but yes I also want SLAAC to get the default route and DNS!
Long story short, in a pre-up I had to add a "echo 0" to the forwarding sysctl for the wan interface.
But from my understanding, this interface is still forwarding IPv6 packets for the VMs.At least now it's working, and also tested that the configuration is also correctly applied upon a reboot.
-
It was really cumbersome to configure IPv6 on my proxmox playground box.
Yes I do want this box to act as a router for the hosted VMs, but yes I also want SLAAC to get the default route and DNS!
Long story short, in a pre-up I had to add a "echo 0" to the forwarding sysctl for the wan interface.
But from my understanding, this interface is still forwarding IPv6 packets for the VMs.At least now it's working, and also tested that the configuration is also correctly applied upon a reboot.
-
It was really cumbersome to configure IPv6 on my proxmox playground box.
Yes I do want this box to act as a router for the hosted VMs, but yes I also want SLAAC to get the default route and DNS!
Long story short, in a pre-up I had to add a "echo 0" to the forwarding sysctl for the wan interface.
But from my understanding, this interface is still forwarding IPv6 packets for the VMs.At least now it's working, and also tested that the configuration is also correctly applied upon a reboot.
-
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.
-
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.
-
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.
-
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.
-
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.
-
@txt_file Looking at the end of pg 3 of
https://www.rfc-editor.org/rfc/rfc2464
"An IPv6 address prefix used for stateless autoconfiguration [ACONF]
of an Ethernet interface must have a length of 64 bits."So you are right. If you are not using #ethernet then #SLAAC might work on different prefix that /64
-
@txt_file Looking at the end of pg 3 of
https://www.rfc-editor.org/rfc/rfc2464
"An IPv6 address prefix used for stateless autoconfiguration [ACONF]
of an Ethernet interface must have a length of 64 bits."So you are right. If you are not using #ethernet then #SLAAC might work on different prefix that /64
-
Embrace IPv6 before its too late? - Many hackers have familiar sayings in their heads, such as “If it ain’t broke, don... - https://hackaday.com/2024/06/08/embrace-ipv6-before-its-too-late/ #routeradvertisement #homenetworking #networkhacks #slaac #ipv4 #ipv6
-
Embrace IPv6 before its too late? - Many hackers have familiar sayings in their heads, such as “If it ain’t broke, don... - https://hackaday.com/2024/06/08/embrace-ipv6-before-its-too-late/ #routeradvertisement #homenetworking #networkhacks #slaac #ipv4 #ipv6
-
Embrace IPv6 before its too late? - Many hackers have familiar sayings in their heads, such as “If it ain’t broke, don... - https://hackaday.com/2024/06/08/embrace-ipv6-before-its-too-late/ #routeradvertisement #homenetworking #networkhacks #slaac #ipv4 #ipv6
-
Embrace IPv6 before its too late? - Many hackers have familiar sayings in their heads, such as “If it ain’t broke, don... - https://hackaday.com/2024/06/08/embrace-ipv6-before-its-too-late/ #routeradvertisement #homenetworking #networkhacks #slaac #ipv4 #ipv6
-
Embrace IPv6 before its too late? - Many hackers have familiar sayings in their heads, such as “If it ain’t broke, don... - https://hackaday.com/2024/06/08/embrace-ipv6-before-its-too-late/ #routeradvertisement #homenetworking #networkhacks #slaac #ipv4 #ipv6
