From: Robert Sander <r.sander@heinlein-support.de>
To: netfilter@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Configure ICMP error source address
Date: Mon, 15 Feb 2016 10:13:15 +0100 [thread overview]
Message-ID: <56C196AB.5080403@heinlein-support.de> (raw)
In-Reply-To: <568F8207.9040305@heinlein-support.de>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 08.01.2016 10:31, Robert Sander wrote:
> We have the situation that our routers use RFC1918 addresses on their
> transfer networks (which should be quite common nowadays to save on
> public IPv4 addresses). ICMP errors are generated with RFC1918 source
> addresses and therefor never reach the original sender.
A follow-up to this request:
It is much easier to accomplish when settings routes with a source
address that is a public IP like this:
ip route add default via 10.10.10.1 src 192.0.2.24
ICMP errors will then use 192.0.2.24 as the source address.
No need for a kernel patch. Thanks for all the input.
Regards
--
Robert Sander
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG:
HRB 93818 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -- Sitz: Berlin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2016-02-15 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 9:31 Configure ICMP error source address Robert Sander
2016-01-08 15:24 ` prmarino1
2016-01-08 16:11 ` Hannes Frederic Sowa
2016-01-09 3:57 ` prmarino1
2016-01-09 9:57 ` Hannes Frederic Sowa
2016-01-09 16:41 ` Robert Sander
2016-01-09 22:55 ` Pascal Hambourg
2016-01-09 23:01 ` Hannes Frederic Sowa
2016-01-10 19:12 ` Robert Sander
2016-01-08 16:21 ` Hannes Frederic Sowa
2016-02-15 9:13 ` Robert Sander [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=56C196AB.5080403@heinlein-support.de \
--to=r.sander@heinlein-support.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter@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 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).