On Wed, Feb 20, 2013 at 01:11:10AM +, Stuart Henderson wrote:
Someone trying to replace some latvian boxes with bgpd/npppd mentioned
a problem with v6 on carp interfaces in 'backup' state where their
address was used as source address, despite there being an address
on the carpdev which
On Wed, Feb 20, 2013 at 12:36:13AM -0600, Todd T. Fries wrote:
The source address selection mechanism in IPv4 is to my understanding:
the first address on the interface associated with the route
to the remote host
The source address selection mechanism in IPv6 is to my understanding:
Someone trying to replace some latvian boxes with bgpd/npppd mentioned
a problem with v6 on carp interfaces in 'backup' state where their
address was used as source address, despite there being an address
on the carpdev which was up.
I don't have a proper v6 carp setup handy to test but got a
The source address selection mechanism in IPv4 is to my understanding:
the first address on the interface associated with the route
to the remote host
The source address selection mechanism in IPv6 is to my understanding:
for each of the global addresses on a system, turn it into an integer