Matthias Schiffer wrote:
> On 06/22/2015 07:58 AM, Steven Barth wrote:
>> On 22.06.2015 00:35, Matthias Schiffer wrote:
>>> 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 s
On 06/22/2015 07:58 AM, Steven Barth wrote:
> On 22.06.2015 00:35, Matthias Schiffer wrote:
>> 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 th
On 22.06.2015 00:35, Matthias Schiffer wrote:
> 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 t
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 のメッセージ:
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 w
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/o
On 05/05/2015 12:36 PM, Markus Stenberg wrote:
> If there are only IPv6 source specific default routes present, the
> host gets -ENETUNREACH on e.g. connect() because ip6_dst_lookup_tail
> calls ip6_route_output first, and given source address any, it fails,
> and ip6_route_get_saddr is never calle
From: Markus Stenberg
Date: Tue, 5 May 2015 13:36:59 +0300
> If there are only IPv6 source specific default routes present, the
> host gets -ENETUNREACH on e.g. connect() because ip6_dst_lookup_tail
> calls ip6_route_output first, and given source address any, it fails,
> and ip6_route_get_saddr
If there are only IPv6 source specific default routes present, the
host gets -ENETUNREACH on e.g. connect() because ip6_dst_lookup_tail
calls ip6_route_output first, and given source address any, it fails,
and ip6_route_get_saddr is never called.
The change is to use the ip6_route_get_saddr, even
9 matches
Mail list logo
