From: Erik Enge <eenge@prium.net>
To: Antony Stone <Antony@soft-solutions.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: If eth0 goes down after a reboot, rules for it will be applied to eth1.
Date: 11 Sep 2002 14:25:56 -0400 [thread overview]
Message-ID: <873csg4c3v.fsf@prium.net> (raw)
In-Reply-To: <20020911174425.URMD287.mta02-svc.ntlworld.com@there>
Antony Stone <Antony@Soft-Solutions.co.uk> writes:
> 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
> 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.
next prev parent reply other threads:[~2002-09-11 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 16:14 If eth0 goes down after a reboot, rules for it will be applied to eth1 Erik Enge
2002-09-11 17:44 ` Antony Stone
2002-09-11 18:25 ` Erik Enge [this message]
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=873csg4c3v.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