From: Erik Enge <eenge@prium.net>
To: netfilter@lists.netfilter.org
Cc: Antony@soft-solutions.co.uk
Subject: Re: If eth0 goes down after a reboot, rules for it will be applied to eth1.
Date: 11 Sep 2002 12:14:06 -0400 [thread overview]
Message-ID: <87ofb44i7l.fsf@prium.net> (raw)
On Wed, 11 Sep 2002 15:05:54 +0100, Antony Stone wrote:
> The IP address which was supposed to be on the 'real' eth0, which has
> just died, gets applied to what you think is eth1 (even though your
> computer has just decided to rename it eth0 as the first working
> ethernet card it found).
Correct:
Before death of NIC 1:
NIC 1, eth0, 192.168.1.1
NIC 2, eth1, 192.168.1.2
NIC 3, eth2, 192.168.1.3
and so on...
After death of NIC 2:
NIC 1 - dead
NIC 2, eth0, 192.168.1.2
NIC 3, eth1, 192.168.1.3
and so on...
> It is almost inconceivable that the interface connecting you to the
> outside world will deign to communicate with your router (or whatever
> else is the next hop upstream of you) because the IP address, network
> address, default gateway, netmask etc don't match.
I don't follow you. Let's suppose that the external interface now has
very laid-back rules and still has the same IP address, network address,
default gateway and netmask (because the 'ifconfig' statement wouldn't
have changed). Why is it inconceivable that that interface wolud
communicate with my router? I can't see why it wouldn't.
Thanks for your reply,
Erik Enge.
next reply other threads:[~2002-09-11 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 16:14 Erik Enge [this message]
2002-09-11 17:44 ` If eth0 goes down after a reboot, rules for it will be applied to eth1 Antony Stone
2002-09-11 18:25 ` Erik Enge
2002-09-11 18:47 ` Antony Stone
2002-09-11 20:21 ` Erik Enge
-- strict thread matches above, loose matches on Subject: below --
2002-09-11 13:42 Erik Enge
2002-09-11 14:05 ` Antony Stone
2002-09-11 17:19 ` Michael H.Collins
2002-09-11 18:19 ` Lists
2002-09-11 18:32 ` Antony Stone
2002-09-12 4:11 ` Lists
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=87ofb44i7l.fsf@prium.net \
--to=eenge@prium.net \
--cc=Antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.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