[x-l-tracker] [ xcast-linux-Bugs-1673794 ] incompatibility with policy routing (2.6.19-)

[SourceForge.net <no...@so...>]

Bugs item #1673794, was opened at 2007-03-05 14:39
Message generated for change (Comment added) made by tkuro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=415584&aid=1673794&group_id=35822

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: kernel-patch
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Takahiro Kurosawa (tkuro)
Assigned to: Takahiro Kurosawa (tkuro)
Summary: incompatibility with policy routing (2.6.19-)

Initial Comment:
XCAST6 patch does not seem to work correctly when CONFIG_IPV6_MULTIPLE_TABLES is set to yes.
If CONFIG_IPV6_MULTIPLE_TABLES is set to yes, the host can not send XCAST6 packets.  It's not confirmed whether or not the host works as a receiver or a router.

----------------------------------------------------------------------

>Comment By: Takahiro Kurosawa (tkuro)
Date: 2007-03-10 18:19

Message:
Logged In: YES 
user_id=255155
Originator: YES

Committed the fix (net/ipv6/addrconf.c rev. 1.11).

----------------------------------------------------------------------

Comment By: Takahiro Kurosawa (tkuro)
Date: 2007-03-10 18:12

Message:
Logged In: YES 
user_id=255155
Originator: YES

File Added: fix.diff

----------------------------------------------------------------------

Comment By: Takahiro Kurosawa (tkuro)
Date: 2007-03-10 18:06

Message:
Logged In: YES 
user_id=255155
Originator: YES

The problem is caused by the rule table priority.  If policy routing is
active, the "local" rule table and the "main" rule table is created on
boot.  The "local" table is used for special purpose like local routes and
ff00::/8, while the route command adds routing entries in the "main" table.
 The problem is that the "local" table has priority over the "main" table; 
the "ff05::10/128" entry added by the route command is never used but the
ff00::/8 entry in the "local" table is always used.

Adding the "ff05::10/128" routing entry in the "local" table should fix
the problem.  I've confirmed this by adding it with the ip command (from
iproute2).  Probably we should add the ff05::10/128 entry inside the kernel
as it is also a special routing entry.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=415584&aid=1673794&group_id=35822