If eth0 goes down after a reboot, rules for it will be applied to eth1.
Quoted 4 lines · Antony Stone
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...
Quoted 4 lines
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.
Quoted 6 lines · Erik Enge
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...
Ugh !!! What sort of networking setup have you got here ???
You're *supposed* to put addresses from different subnets onto each interface...
What netmasks are you using on these interfaces ?
Quoted 10 lines
Quoted 4 lines
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.
Based on the addresses you've given above, I agree with you, but that looks
like a very weird way to set up a firewall. I don't understand how you
expect your routing tables to work.
Give us more information about your overall network setup, and we'll probably either tell you that you've been very lucky with your routing table setup, or that you've got more to worry about than one of your NICs dying :-)
Antony.
Signature · 3 lines
If you want to be happy for an hour, get drunk. If you want to be happy for a year, get married. If you want to be happy for a lifetime, get a garden.
Quoted 1 line · Antony Stone
Ugh !!! What sort of networking setup have you got here ???
A fictional one. :-)
Here's what we are thinking about doing, with the actual subnets:
NIC 1, eth0, 192.168.1.0, private LAN
NIC 2, eth1, 192.168.10.0, DMZ
NIC 3, eth2, 192.168.11.0, DMZ located elsewhere NIC 4, eth3, 10.0.0.0, backup subnet
NIC 5, eth4, some-other-subnet-that-leads-to-the-internet
Quoted 4 lines
Give us more information about your overall network setup, and we'll probably either tell you that you've been very lucky with your routing table setup, or that you've got more to worry about than one of your NICs dying :-)
:-)
Ok, given the above configuration, and as we discussed before, why is it inconceivable that the interface would communicate with my router?
Thanks for your help so far,
Erik.
Note: currently, we only have one small firewall with a LAN behind it. The reason we need this quite elaborate setup (assuming we're not going to buy any switches) is that we are moving part of our infrastructure to a colocation.
Quoted 4 lines · Erik Enge
Quoted 1 line · Antony Stone
Ugh !!! What sort of networking setup have you got here ???
A fictional one. :-)
Oh good. I feel much better about things already.
Quoted 7 lines
Here's what we are thinking about doing, with the actual subnets:
NIC 1, eth0, 192.168.1.0, private LAN
NIC 2, eth1, 192.168.10.0, DMZ
NIC 3, eth2, 192.168.11.0, DMZ located elsewhere NIC 4, eth3, 10.0.0.0, backup subnet
NIC 5, eth4, some-other-subnet-that-leads-to-the-internet
Very nice. Very reasonable. This should work. I still think you have
nothing to worry about (as I said in my first reply).
Quoted 2 lines
Ok, given the above configuration, and as we discussed before, why is it inconceivable that the interface would communicate with my router?
eth1 has address 192.168.10.1 (I assume), netmask 255.255.255.0, and it's expecting to find other machines with the network address 192.168.10.0/24 connected to it.
One day eth0 dies and eth1 gets reassigned by the Bios / kernel to take over the duties of eth0 (however it's still plugged into the same equipment it used to be connected to).
So eth1 now has address 192.168.1.1, netmask 255.255.255.0, and expects to talk to machines with network address 192.168.1.0/24 connected to it.
If something with address 192.168.10.42 sends out an ARP request for its default gateway of 192.168.10.1 (ie the old eth1 which it used to be connected to), this interface which now has address 192.168.1.1 isn't going to reply, so nothing communicates at the ethernet level (Ramin, I'm not going to discuss whether this is layer 1 or layer 2 right now, okay ?)
Similarly, by the time you get up to NIC5, which used to be eth4, and is now eth3, you've got eth3 with address 10.0.0.0 (I'll assume this has a netmask of 255.0.0.0 for the time being, but it really doesn't matter whether you've picked a Class A, B or C for this) plugged into something-that-leads-to-the- Internet, but which definitely doesn't have an address starting with 10 (if
it did, it would have been plugged into NIC4 in the first place). Therefore
this interface (NIC5) won't communicate with anything either for the same reason.
Basically what happens is that NIC1 dies, all the other NICs get assigned IP addresses which are invalid on the networks they're physically connected to, and ARP (which is what links the ethernet layer and the IP layer) doesn't
work any more. Nothing will talk to anything else until you either repair
NIC1, or swap all the cables along one position on your firewall, which brings you back to the physical configuration you wanted in the first place.
Does this make it clear ?
Quoted 4 lines
Note: currently, we only have one small firewall with a LAN behind it. The reason we need this quite elaborate setup (assuming we're not going to buy any switches) is that we are moving part of our infrastructure to a colocation.
That's no problem. One day you'll join them up using FreeS/WAN, I hope :-)
Antony.
Signature · 1 line
Most people have more than the average number of legs.
Quoted 1 line · Antony Stone
Does this make it clear?
Ahh, now it all makes sense.
That's so very much for your time. :-)
Erik.