From: David Ahern
Date: Thu, 16 Jun 2016 16:24:23 -0700
> IPv6 address selection is currently messed up for several use cases such
> as unnumbered deployments with global addresses on the VRF device and none
> on the enslaved devices.
>
> Update the source address selection to consider the real
IPv6 address selection is currently messed up for several use cases such
as unnumbered deployments with global addresses on the VRF device and none
on the enslaved devices.
Update the source address selection to consider the real output route as
opposed to the VRF route that sends packets to the V
next-20150714 w/ one ethernet commit reverted. -0706 w/ same revert works.
"ip addr show" for the wireless says:
5: wlp3s0b1: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether bc:85:56:1f:4f:6d brd ff:ff:ff:ff:ff:ff
inet 172.30.42.75/27 brd 172.30.42.95 scope global dy
Hello,
My network has several IPv6 addresses and they don't route between
themselves, due to the current source address selection it means that
many times the network is simply not operational since Linux will choose
an address for a different network than targeted for the connection.
I have seen
YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <[EMAIL PROTECTED]> (at Thu, 22 Jun 2006 00:57:56 +0200), Lukasz
> Stelmach <[EMAIL PROTECTED]> says:
>
>> Lukasz Stelmach wrote:
>>> Lukasz Stelmach wrote:
[]
>>
>> fd24:6f44:46bd:face:EUI64 fd24:6f44:46bd:face:RANDOM
>> and
>> 2002:531f:d667:face
From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Date: Thu, 22 Jun 2006 01:12:57 +0900 (JST)
> I think it is trivial enough to push this to -stable as well.
>
> Signed-off-by: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Ok, done.
Thanks a lot!
-
To unsubscribe from this list: send the line "unsubscribe ne
In article <[EMAIL PROTECTED]> (at Thu, 22 Jun 2006 00:57:56 +0200), Lukasz
Stelmach <[EMAIL PROTECTED]> says:
> Lukasz Stelmach wrote:
> > Lukasz Stelmach wrote:
> >
> >> [...] when trying to connect to
> >>
> >> 2001:200:0:8002:203:47ff:fea5:3085 (www.kame.net)
> >>
> >> with two global addres
Lukasz Stelmach wrote:
> Lukasz Stelmach wrote:
>
>> [...] when trying to connect to
>>
>> 2001:200:0:8002:203:47ff:fea5:3085 (www.kame.net)
>>
>> with two global addresses assigned to the ethernet card
>>
>> fd24:6f44:46bd:face::254
>> 2002:531f:d667:face::254
>>
>> rule 8 does not work and the f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --- linux/net/ipv6/addrconf.c.orig2006-06-21 11:41:22.0 +0200
+++ linux/net/ipv6/addrconf.c 2006-06-21 17:18:56.0 +0200
@@ -862,6 +862,8 @@ static int inline ipv6_saddr_label(const
*2002::/16 2
*::/9
In article <[EMAIL PROTECTED]> (at Wed, 21 Jun 2006 15:42:11 +0200), Lukasz
Stelmach <[EMAIL PROTECTED]> says:
> --- /usr/src/linux/net/ipv6/addrconf.c~ 2006-06-21 11:41:22.0
> +0200
> +++ /usr/src/linux/net/ipv6/addrconf.c2006-06-21 15:33:26.0
> +0200
> @@ -862,6
In article <[EMAIL PROTECTED]> (at Tue, 20 Jun 2006 23:38:46 +0200), Lukasz
Stelmach <[EMAIL PROTECTED]> says:
> Greetings.
>
> net/ipv6/addrconf.c:971 is
> /* Rule 2: Prefer appropriate scope */
> if (hiscore.rule < 2) {
> hiscore.scope = __ipv6_addr_src_scope(hiscore.addr_type);
>
Lukasz Stelmach wrote:
> I found it when I was trying to figure out why when trying to connect to
>
> 2001:200:0:8002:203:47ff:fea5:3085 (www.kame.net)
>
> with two global addresses assigned to the ethernet card
>
> fd24:6f44:46bd:face::254
> 2002:531f:d667:face::254
>
> rule 8 does not work a
Greetings.
net/ipv6/addrconf.c:971 is
/* Rule 2: Prefer appropriate scope */
if (hiscore.rule < 2) {
hiscore.scope = __ipv6_addr_src_scope(hiscore.addr_type);
hiscore.rule++;
}
I am afraid, that it does not make any sense for I find no place where a value
is assigned to hiscore.ad
13 matches
Mail list logo
