Netdev List
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 1/1] sysctl configurable icmperror sourceaddress
Date: Thu, 9 Jun 2005 01:40:29 +0200	[thread overview]
Message-ID: <20050608234029.GJ28207@xi.wantstofly.org> (raw)
In-Reply-To: <20050608.144941.26530856.davem@davemloft.net>

On Wed, Jun 08, 2005 at 02:49:41PM -0700, David S. Miller wrote:

> > Can this patch go in, pretty please?
> > 
> > Here's the patch again for reference:
> 
> We have a similar sysctl for ARP handling, why don't
> we make use of it?

Which one do you mean, the arp_{filter,announce,ignore} ones?  IMHO
this is a very different issue, this patch just selects which source
address we use when we reply to a packet with an ICMP.

In the case below, if all routers are linux routers, a traceroute
from source to dest will show something like this:
	1 10.0.0.254 x.xxx ms x.xxx ms x.xxx ms
	2 12.0.0.100 x.xxx ms x.xxx ms x.xxx ms
	3 12.0.0.1 x.xxx ms x.xxx ms x.xxx ms

Whereas we'd prefer seeing this, partly because it makes more sense,
partly because a very large fraction of networking hardware does it
this way too:
	1 10.0.0.254 x.xxx ms x.xxx ms x.xxx ms
	2 11.0.0.100 x.xxx ms x.xxx ms x.xxx ms   <===
	3 12.0.0.1 x.xxx ms x.xxx ms x.xxx ms

I used to work at an ISP and there are a number of practical cases
where the linux behavior is rather confusing.


cheers,
Lennert


	+------------+
	|   source   |
	|  10.0.0.1  |
	+-----+------+
	      |
	      V
	      |
	      |
	+-----+------+
	| 10.0.0.254 |
	|            |
	|   router1  +---------------------+
	|            |                     |
	| 11.0.0.254 |                     |
	+-----+------+                     |
	      |                            |
	      V                            ^ asymmetric route
	      |                            |  back to source
	      |                            |
	+-----+------+               +-----+------+
	| 11.0.0.100 |               | 13.0.0.13  |
	|            |               |            |
	|   router2  |               |   router3  |
	|            |               |            |
	| 12.0.0.100 |               | 12.0.0.101 |
	+-----+------+               +-----+------+
	      |                            |
	      +------------->--------------+
	      V
	      |
	+-----+------+
	|    dest    |
	|  12.0.0.1  |
	+------------+

      reply	other threads:[~2005-06-08 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07  9:26 [PATCH 1/1] sysctl configurable icmperror sourceaddress J. Simonetti
2005-06-07  9:40 ` J. Simonetti
2005-06-08 21:45 ` Lennert Buytenhek
2005-06-08 21:49   ` David S. Miller
2005-06-08 23:40     ` Lennert Buytenhek [this message]

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=20050608234029.GJ28207@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=davem@davemloft.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