Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1169663
| From | Markus Stenberg <markus.stenberg@iki.fi> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] ipv6: Fixed source specific default route handling. |
| Date | 2015-06-22 01:20 +0200 |
| Message-ID | <pDWGR-2NM-1@gated-at.bofh.it> (permalink) |
| References | <pmIAi-jO-25@gated-at.bofh.it> <pDR4t-34v-1@gated-at.bofh.it> <pDVKN-1tA-1@gated-at.bofh.it> <pDW4a-1PP-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
You have /128 dst. To override it you need dst/128 AND src/>0 route. ( or just /128 dst and higher metric). Sorry if I am bit unclear - can explain better given real keyboard but that is avail only week from now. -Markus (on the road, via iPhone) 21.6.2015 23.35、Matthias Schiffer <mschiffer@universe-factory.net> のメッセージ: >> On 06/22/2015 12:05 AM, Markus Stenberg wrote: >> Prefsrc is essentially historic non IPv6 construct. IPv6 SAS is based on dst, src, metric ordered lookup just like the routing is too ( lookup rfc, some src specific routing drafts for details ). >> >> Therefore I do not see a problem. If you want specific SA, add same route with higher metric and/or (more) specific src match. >> >> There might be bugs there tho, but that is how it should work. As SAS is supposed to happen before routing ( see rfc ) the prefsrc is .. Cough. >> >> -Markus > > Could you explain in detail what you mean with "If you want specific SA, > add same route with higher metric and/or (more) specific src match."? > Routes aren't bound to specific addresses except via the "src" attribute > (which is called prefsrc in the kernel), which is exactly what it not > working. I can't control the chosen source address at all when > source-specific routes are involved. > > Also, metric-based route selection is broken when source-specific routes > are involved. The commands mentioned in my first mail will create the > following configuration: > > # ip a > 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state > UNKNOWN group default qlen 500 > link/ether 22:46:f4:9c:9e:3a brd ff:ff:ff:ff:ff:ff > inet6 fd00::20/64 scope global > valid_lft forever preferred_lft forever > inet6 fe80::2046:f4ff:fe9c:9e3a/64 scope link > valid_lft forever preferred_lft forever > 4: test@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UNKNOWN group default > link/ether ae:2b:02:16:23:0f brd ff:ff:ff:ff:ff:ff > inet6 fd00::1/128 scope global > valid_lft forever preferred_lft forever > inet6 fe80::ac2b:2ff:fe16:230f/64 scope link > valid_lft forever preferred_lft forever > > # ip -6 r > fd00::/64 from fd00::/64 dev eth0 metric 1024 > fd00::1 dev test proto kernel metric 256 > fd00::/64 dev eth0 proto kernel metric 256 > > The only route I have added manually is the source-specific one, the > other two have been created by address assignment. Adding a "src" > address to the source-specific route has no effect. > > Even though the source-specific route has a higher metric than the > generic one, the source-specific one shadows the generic route. > > Thanks for your reply, > Matthias > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] ipv6: Fixed source specific default route handling. Matthias Schiffer <mschiffer@universe-factory.net> - 2015-06-21 19:20 +0200
Re: [PATCH] ipv6: Fixed source specific default route handling. Markus Stenberg <markus.stenberg@iki.fi> - 2015-06-22 01:20 +0200
Re: [PATCH] ipv6: Fixed source specific default route handling. Steven Barth <steven@midlink.org> - 2015-06-22 08:30 +0200
Re: [PATCH] ipv6: Fixed source specific default route handling. YOSHIFUJI Hideaki/吉藤英明 <hideaki.yoshifuji@miraclelinux.com> - 2015-06-23 04:00 +0200
csiph-web