| To: | Hasso Tepper <hasso@xxxxxxxxx> |
|---|---|
| Subject: | Re: icmp_unreachable uses wrong ip |
| From: | Patrick McHardy <kaber@xxxxxxxxx> |
| Date: | Tue, 03 May 2005 20:15:02 +0200 |
| Cc: | "J. Simonetti" <jeroens@xxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <200505030944.49175.hasso@xxxxxxxxx> |
| References: | <1115040079.5620.11.camel@xxxxxxxxxxxxxxxxxxxxxxxxx> <200505022038.22014.hasso@xxxxxxxxx> <4276A400.2050306@xxxxxxxxx> <200505030944.49175.hasso@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.7) Gecko/20050420 Debian/1.7.7-2 |
Hasso Tepper wrote: > Patrick McHardy wrote: >> >>Your patch can't guarantee that the address used is the same that was >>used as nexthop by the previous hop in the path when multiple addresses >>are configured on the incoming interface. So I don't think it achieves >>much of your goal of making debugging complicated topologies easier. > > At first I don't care what was used as nexthop. I want to know which > physical link was used. Having multiple addresses in the same link is more > corner case in core network anyway. But when multiple addresses are used the result can be even more confusing. I don't like inconsistent behaviour, and this patch works sometimes and sometimes it doesn't. > And can you explain what theoretical possibilities router has to obtain info > what address was used as nexthop by neighbour? I can think of none. Regards Patrick |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: [PATCH] s2io: replace readq() with mmiowb() in s2io_xmit(), Ramkrishna Vepa |
|---|---|
| Next by Date: | Re: IPsec performance, Dave Dillow |
| Previous by Thread: | Re: icmp_unreachable uses wrong ip, Hasso Tepper |
| Next by Thread: | Re: icmp_unreachable uses wrong ip, Hasso Tepper |
| Indexes: | [Date] [Thread] [Top] [All Lists] |