Difference between revisions of "Talk:IPv6 Networking"
From Funtoo Linux
(zeroconf and addressing) |
m (wpa_supplicant) |
||
| Line 6: | Line 6: | ||
For auto-configured, globally routable addresses, <tt>net-misc/radvd</tt> '''*should*''' configure addressing and routing, much like DHCP does in IPv4 ([http://www.rfc-editor.org/rfc/rfc4861.txt RFC4861]). | For auto-configured, globally routable addresses, <tt>net-misc/radvd</tt> '''*should*''' configure addressing and routing, much like DHCP does in IPv4 ([http://www.rfc-editor.org/rfc/rfc4861.txt RFC4861]). | ||
| + | |||
| + | What about IPv6 over secure wireless? wpa_supplicant requires the interface to be up, but addressing requires wpa_supplicant to be connected (right?). If wpa_supplicant connects after a delay (as is normal), does the interface get its address? | ||
Not exactly related, but there is also IPv6 ULA ([http://tools.ietf.org/html/rfc4193 RFC4193], FC00::/7). | Not exactly related, but there is also IPv6 ULA ([http://tools.ietf.org/html/rfc4193 RFC4193], FC00::/7). | ||
-[[User:Apple|Apple]] 13:48, 18 December 2010 (CET) | -[[User:Apple|Apple]] 13:48, 18 December 2010 (CET) | ||
Revision as of 14:04, 18 December 2010
zeroconf and addressing
Sorry to keep bringing this up but I hope it helps get correct information on the page.
For link-local auto-configuration, are routes necessary? These are prefixed by fe80::/80 suffixed with the NIC's MAC address.
For auto-configured, globally routable addresses, net-misc/radvd *should* configure addressing and routing, much like DHCP does in IPv4 (RFC4861).
What about IPv6 over secure wireless? wpa_supplicant requires the interface to be up, but addressing requires wpa_supplicant to be connected (right?). If wpa_supplicant connects after a delay (as is normal), does the interface get its address?
Not exactly related, but there is also IPv6 ULA (RFC4193, FC00::/7).
-Apple 13:48, 18 December 2010 (CET)
