From: Mark Watts <m.watts@eris.qinetiq.com>
To: linux-kernel@vger.kernel.org
Cc: Adam Popik <popik@moon.tuniv.szczecin.pl>
Subject: Re: stupied userspace programs or kernel bug ?
Date: Wed, 7 Jul 2004 15:15:10 +0100 [thread overview]
Message-ID: <200407071515.10625.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407071421180.23555-100000@moon.tuniv.szczecin.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Hello ;
> That is a problem:
> linux#ifconfig eth0 192.168.1.1
Because you didn't specify a netmask, it defaulted to 255.255.255.0
> linux#ifconfig lo:1 192.168.1.100 netmask 255.255.255.255 up
Although you specified a tighter netmask here, the routing table is such that
192.168.1.0/24 is routed out eth0, overriding the fact that 1.100 is on lo:1
I'll bet the kernel responds to the ICMP echo request because it knows it
holds the IP for 1.100 so it should respond, yet its outbound routing tells
it to respond via eth0. (somone connect me if I'm wrong)
This is probably a side effect of having two interfaces on the same subnet,
and having the /24 subnet higher up the routing rable than the /32 host.
I believe the behaviour you are seeing is 'by design' although the merits of
this have been discussed to death in the past (IIRC)
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA7AVuBn4EFUVUIO0RAlXpAJ9I1FBUhqDDgV3Tvs53NjSM9BQq9QCeIVeu
f4Jzs0L/LlvjOsm8CcMNoJs=
=/jLZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-07 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 12:28 Adam Popik
2004-07-07 14:15 ` Mark Watts [this message]
2004-07-07 14:54 ` Adam Popik
2004-07-07 19:47 ` Dub Spencer
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=200407071515.10625.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=popik@moon.tuniv.szczecin.pl \
/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
all inboxes | Powered by JetHome®