[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 04057) Re: ping6 is sent out from wrong interface
- To: <usagi-users@xxxxxxxxxxxxxxxxx>, YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
- Subject: (usagi-users 04057) Re: ping6 is sent out from wrong interface
- From: "Fey Marcus" <Fey@xxxxxxx>
- Date: Wed, 25 Jun 2008 09:51:05 +0200
- Cc: <netdev@xxxxxxxxxxxxxxx>, <usagi-users@xxxxxxxxxxxxxx>
- Importance: normal
- In-reply-to: <4861ED72.6080100@xxxxxxxxxxxxxxxx>
- Priority: normal
- References: <4861ED72.6080100@xxxxxxxxxxxxxxxx>
- Reply-to: usagi-users@xxxxxxxxxxxxxxxxx
- Thread-index: AcjWlvv9w4WMZsm1Qdix1Z00CUaXegAALa/w
- Thread-topic: (usagi-users 04056) Re: ping6 is sent out from wrong interface
Hi Naohiro,
>I'm not convinced yet.
>I don't think it's correct that kernel or ping6 arbitrarily
>decides outgoing interface.
>
>Is this really an expected behaviour?
>Could you explain to me the reason of it, too?
>
>I think the behavior should be similar to IPv4.
It's due to routing.
Your routing table shows this:
---
# route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:2c0:418:1::/64 * U 256 0 0 eth0
2001:2c0:418:2::/64 * U 256 0 0 eth1
fe80::/64 * U 256 0 0 eth0
fe80::/64 * U 256 0 0 eth1
::::::
2001:2c0:418:1::1/128 * U 0 8 1 lo
2001:2c0:418:2::2/128 * U 0 5 1 lo
::::::
ff00::/8 * U 256 0 0 eth0
ff00::/8 * U 256 0 0 eth1
#
---
...with eth0 being preferred over eth1 for multicast packets.
You could add a dedicated route for ff02::/16 to make the kernel output the packet via eth1.
Bye,
Marcus
-----------------------------------------
IABG mbH
Sitz der Gesellschaft: Ottobrunn, Registergericht: Amtsgericht Muenchen, HRB 5499
Geschaeftsfuehrung: Prof. Dr.-Ing. Rudolf F. Schwarz
Vorsitzender des Aufsichtsrats: General a. D. Wolfgang Altenburg