From: Thomas Graf <tgraf@suug.ch>
To: Tim Newsham <newsham@lava.net>
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: source routing - bug?
Date: Wed, 15 Jun 2005 03:05:48 +0200 [thread overview]
Message-ID: <20050615010548.GE22463@postel.suug.ch> (raw)
In-Reply-To: <Pine.BSI.4.61.0506061455340.11929@malasada.lava.net>
* Tim Newsham <Pine.BSI.4.61.0506061455340.11929@malasada.lava.net> 2005-06-06 15:02
> Using the netcat utility I run tests from machine A:
>
> $ nc -g B C 3333
> I see packets forwarded to B then on to C and the connection
> completes successfully.
>
> $ nc -g A -g B C 3333
> I see packets forwarded over lo to A, and no further packets
> are sent over lo or eth0. Machines B and C receive no packets.
A 127.0.0.1 source address is considered martian by the source
validation code as proposed by rfc1812. You should see warnings
in the console if you have martian logging enabled.
> $ nc -g B A 3333
> I see packets forwarded out over eth0 to B and then back to A
> but machine A never seems to accept the packets or reply with
> a SYN or RST.
A will do a route lookup of [src=A dst=A] which results in your
local route being returned. Again this violates rfc1812 because
that route will not be a unicast route but a local one. A martian
source warning should be logged if enabled.
next parent reply other threads:[~2005-06-15 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSI.4.61.0506061455340.11929@malasada.lava.net>
2005-06-15 1:05 ` Thomas Graf [this message]
2005-06-15 1:15 ` source routing - bug? Tim Newsham
2005-06-15 1:24 ` Thomas Graf
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=20050615010548.GE22463@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=newsham@lava.net \
/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).