From: Hasso Tepper <hasso@estpak.ee>
To: Patrick McHardy <kaber@trash.net>
Cc: "J. Simonetti" <jeroens@office.netland.nl>, netdev@oss.sgi.com
Subject: Re: icmp_unreachable uses wrong ip
Date: Mon, 2 May 2005 20:38:21 +0300 [thread overview]
Message-ID: <200505022038.22014.hasso@estpak.ee> (raw)
In-Reply-To: <42763E96.1070209@trash.net>
Patrick McHardy wrote:
> Hasso Tepper wrote:
> > Similar patches have been posted to the list repeatedly AFAIK with no
> > any response from developers. Can someone enlighten us why? Is there
> > something wrong with it? This is the feature people administrating
> > routers would like to have. It makes debugging complicated topologies
> > much easier and all routers I have seen behave this way.
>
> 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.
--
Hasso
next prev parent reply other threads:[~2005-05-02 17:38 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 [this message]
2005-05-02 22:04 ` Patrick McHardy
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=200505022038.22014.hasso@estpak.ee \
--to=hasso@estpak.ee \
--cc=jeroens@office.netland.nl \
--cc=kaber@trash.net \
--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).