From: Patrick McHardy <kaber@trash.net>
To: Hasso Tepper <hasso@estpak.ee>
Cc: "J. Simonetti" <jeroens@office.netland.nl>, netdev@oss.sgi.com
Subject: Re: icmp_unreachable uses wrong ip
Date: Tue, 03 May 2005 00:04:48 +0200 [thread overview]
Message-ID: <4276A400.2050306@trash.net> (raw)
In-Reply-To: <200505022038.22014.hasso@estpak.ee>
Hasso Tepper wrote:
> Patrick McHardy wrote:
>
>>Why can't you simply add the prefered source address to the route?
>
> Because I don't know what it is. Router A knows what's the best path from
> router A to router B, but he can't know (at least in cases where there are
> more than 1 path between them) what's the best path from router B to router
> A. Therefore you canät say which one is incoming interface in router A for
> traffic from router B. And even if you know it in some moment, topology
> might change in next moment (dynamic routing) etc.
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.
Regards
Patrick
next prev parent reply other threads:[~2005-05-02 22:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 13:21 icmp_unreachable uses wrong ip J. Simonetti
2005-05-02 13:59 ` Hasso Tepper
2005-05-02 14:52 ` Patrick McHardy
2005-05-02 17:38 ` Hasso Tepper
2005-05-02 22:04 ` Patrick McHardy [this message]
2005-05-03 6:44 ` Hasso Tepper
2005-05-03 18:15 ` Patrick McHardy
2005-05-03 23:35 ` Hasso Tepper
2005-05-03 23:37 ` Patrick McHardy
2005-05-04 8:29 ` Lennert Buytenhek
2005-05-04 7:03 ` Meelis Roos
2005-05-03 11:46 ` Hasso Tepper
2005-05-03 9:22 ` Lennert Buytenhek
2005-05-03 9:42 ` Pekka Savola
2005-05-03 10:38 ` Lennert Buytenhek
2005-05-03 11:00 ` Hasso Tepper
2005-05-04 1:15 ` Glen Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4276A400.2050306@trash.net \
--to=kaber@trash.net \
--cc=hasso@estpak.ee \
--cc=jeroens@office.netland.nl \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).