From: Alexander Hoogerhuis <alexh@boxed.no>
To: Patrick McHardy <kaber@trash.net>
Cc: Chris Wright <chrisw@sous-sol.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: A patch you wrote some time ago (aka: "[patch 41/54] ICMP: Fix icmp_errors_use_inbound_ifaddr sysctl")
Date: Wed, 20 Apr 2011 10:38:51 +0200 [thread overview]
Message-ID: <4DAE9B9B.90509@boxed.no> (raw)
In-Reply-To: <4DAE9824.10802@trash.net>
On 20.04.2011 10:24, Patrick McHardy wrote:
>
> That might be a possibility to fix this for your case. But I'm
> wondering why you're turning this on at all and not have routing
> decide the correct source address?
Not a whole lot of tuning, but trying to figure why this would not work
as any other VRRP implementation would work on other routers/OSes.
My case seems to be a general problem for ICMP errors, as the IP stack
tends to want to listen more to advice coming back with the source IP of
the gateway, not a third party.
If you have two machines (A and B) run VRRP and share an IP (C), then
any ICMP redirect should have the VRRP IP as source (C), and the way it
works today (with or without sysctl_icmp_errors_use_inbound_ifaddr) is
that it will have the source set to the primary IP of the source interface.
I suspect this holds for any other ICMP message sent back to hosts in
the connected network as well, such as PMTU-related issues, etc.
In my case nodes in the connected subnet would get ICMP redirects from
the primary IPs, and thus not listen to them as they are arriving from
nodes not listen in the list of known gateways.
It would make more sense when returning ICMP messages the source IP
would be the actual IP it is recveied on, not the primary IP of the
interface.
mvh,
A
--
Alexander Hoogerhuis | http://no.linkedin.com/in/alexh
Boxed Solutions AS | +47 908 21 485 - alexh@boxed.no
"Given enough eyeballs, all bugs are shallow." -Eric S. Raymond
next prev parent reply other threads:[~2011-04-20 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 16:43 A patch you wrote some time ago (aka: "[patch 41/54] ICMP: Fix icmp_errors_use_inbound_ifaddr sysctl") Alexander Hoogerhuis
2011-04-19 16:54 ` Chris Wright
2011-04-20 8:24 ` Patrick McHardy
2011-04-20 8:38 ` Alexander Hoogerhuis [this message]
2011-04-20 9:11 ` Alexander Hoogerhuis
2011-04-22 14:46 ` Jan Ceuleers
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=4DAE9B9B.90509@boxed.no \
--to=alexh@boxed.no \
--cc=chrisw@sous-sol.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.