Difference between pages "Portage's bashrc" and "Talk:IPv6 Networking"

(Difference between pages)
(Usefulness of bashrc)
 
m (re: radvd: forgot my sig)
 
Line 1: Line 1:
== bashrc's locations ==
+
== zeroconf and addressing ==
If there is more than one bashrc files, each will be sourced before the ebuild is executed in the following order:
+
  
* <tt>/etc/portage/bashrc</tt> - Global bashrc file which applied to all packages
+
Sorry to keep bringing this up but I hope it helps get correct information on the page.
Per-package:
+
* <tt>/etc/portage/env/${CATEGORY}/${PN}</tt>
+
* <tt>/etc/portage/env/${CATEGORY}/${PN}:${SLOT}</tt>
+
* <tt>/etc/portage/env/${CATEGORY}/${P}</tt>
+
* <tt>/etc/portage/env/${CATEGORY}/${PF}</tt>
+
  
== Usefulness of bashrc ==
+
For link-local auto-configuration, are routes necessary? These are prefixed by fe80::/80 suffixed with the NIC's MAC address.
With bashrc you will be able to:
+
 
* Set custom variables per package, like <tt>CFLAGS</tt> of <tt>FEATURES</tt>
+
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]).
* Execute code in selected [[Ebuild Functions|ebuild stages]]
+
 
 +
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).
 +
 
 +
-[[User:Apple|Apple]] 13:48, 18 December 2010 (CET)
 +
 
 +
== re: zeroconf and addressing ==
 +
 
 +
My understanding is that link-local addresses are non-routeable (local LAN only) and thus don't require any routes to be set.
 +
 
 +
Yes, we/you can add information about radvd, but it is only used when you are configuring your system to act as a router, at least that it is my understanding.
 +
 
 +
I don't understand the wpa_supplicant issue, but I haven't used IPV6 over wireless with Funtoo yet.
 +
 
 +
-[[User:drobbins|Daniel Robbins]] 13:26, 18 December 2010 (MST)
 +
 
 +
== re: radvd ==
 +
 
 +
I see I misunderstood. I assumed that, as consumer IPv6 tech is not widely available, all users would be running a linux router with radvd. It is possible that other ND/router advertisements do not set routes...
 +
 
 +
-[[User:Apple|Apple]] 04:12, 19 December 2010 (CET)

Latest revision as of 03:12, 19 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)

re: zeroconf and addressing

My understanding is that link-local addresses are non-routeable (local LAN only) and thus don't require any routes to be set.

Yes, we/you can add information about radvd, but it is only used when you are configuring your system to act as a router, at least that it is my understanding.

I don't understand the wpa_supplicant issue, but I haven't used IPV6 over wireless with Funtoo yet.

-Daniel Robbins 13:26, 18 December 2010 (MST)

re: radvd

I see I misunderstood. I assumed that, as consumer IPv6 tech is not widely available, all users would be running a linux router with radvd. It is possible that other ND/router advertisements do not set routes...

-Apple 04:12, 19 December 2010 (CET)