From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: William Knop <w_knop@hotmail.com>
Cc: bmcdowell@coxhealthplans.com, netfilter@lists.netfilter.org
Subject: Re: iptables routing help
Date: Tue, 27 Jan 2004 06:46:55 -0500 [thread overview]
Message-ID: <1075204015.1891.0.camel@jasiiitosh.nexusmgmt.com> (raw)
In-Reply-To: <915A2E91-5082-11D8-A7CD-000A9577164C@hotmail.com>
That's understandable - inserting a second interface is quite
intrusive. However, creating a logical interface does not require
inserting a second NIC - merely binding a second IP address to the
existing NIC - two networks running on the same NIC - John
On Mon, 2004-01-26 at 23:37, William Knop wrote:
> Unfortunately, using two interfaces isn't an option, either. A friend
> of mine suggested vpn, however there has to be a cleaner route.
>
> I thought I could drop packets from the prerouting table and it would
> fall into the default routing table or something like that. Surely
> there has to be a way.
>
>
> On Jan 26, 2004, at 11:29 AM, <bmcdowell@coxhealthplans.com> wrote:
>
> >
> > I was about to suggest the exact same thing.
> >
> >
> > Bob
> >
> > -----Original Message-----
> > From: netfilter-admin@lists.netfilter.org
> > [mailto:netfilter-admin@lists.netfilter.org]On Behalf Of John A.
> > Sullivan III
> > Sent: Monday, January 26, 2004 6:06 AM
> > To: William Knop
> > Cc: netfilter@lists.netfilter.org
> > Subject: Re: iptables routing help
> >
> >
> > On Sun, 2004-01-25 at 13:53, William Knop wrote:
> >> Okay, the problem is that we don't want to do nat (as I said in my
> >> original plee for help). We need external ips on all of the machines.
> >> Additionally, The ISP's DHCP server specifies it's own gateway, so I
> >> can't do normal routing, without spoofing the gateway's address and
> >> doing all sorts of ugly stuff (please correct me if I'm wrong).
> >>
> >>
> >> I was under the impression one could have iptables drop a packet from
> >> the prerouting or brouting table and it would go through the machine's
> >> routing table, without being specified on all the lan machines as the
> >> gateway.
> >>
> >>
> >> The physical layout we have are a bunch of boxes connected to a
> >> switch, and the dsl modem connected to the switch's uplink port. I
> >> could have the modem jack into a firewall box, or something, however
> >> the linux ethernet bridge seems to do very odd things to arps, and
> >> also iptables. Would bridging be necessary?
> >>
> >>
> >>
> > <snip>
> > This may not be as bad as it sounds and it my be a netfilter issue.
> > Looking at the topology, I would assume that there are several devices
> > on the same public subnet connect through the switch to the DSL modem
> > in
> > which case they should talk to each other directly on that subnet
> > without sending the data across the DSL modem. But am I correct to
> > understand that even though these devices share the same switch and the
> > same DSL modem that they are allocated public addresses out of
> > different
> > IP subnets?
> >
> > If that is the case, the best solution is to install a second NIC into
> > each device and create a separate private network as already suggested.
> > Barring that, you can create a second, logical network on the same
> > media. Use iproute2 to bind a second address to each of the public
> > interfaces. These will all come from the same subnet and should be
> > able
> > to communicate with each other. Just be sure to use the secondary
> > address when sending data between those devices.
> >
> > ip address add dev0 192.168.1.4/24
> > ip address add dev0 192.168.1.5/24
> > ip address add dev0 192.168.1.6/24 . . . etc.
> >
> > This is a bit dangerous as these devices are still publicly exposed and
> > the ISP may allow traffic on RFC1918 addresses on their internal
> > networks so you may want to tightly secure the devices even for traffic
> > from these "private" addresses using iptables.
> >
> > This is the sort of set up that we use on our internal routers to
> > participate in the worldwide VPN project (http://www.worldwidevpn.com).
> > Good luck - John
> > --
> > John A. Sullivan III
> > Chief Technology Officer
> > Nexus Management
> > +1 207-985-7880
> > john.sullivan@nexusmgmt.com
> > ---
> > If you are interested in helping to develop a GPL enterprise class
> > VPN/Firewall/Security device management console, please visit
> > http://iscs.sourceforge.net
> >
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
next prev parent reply other threads:[~2004-01-27 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 16:29 iptables routing help bmcdowell
2004-01-27 4:37 ` William Knop
2004-01-27 11:46 ` John A. Sullivan III [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-25 18:53 William Knop
2004-01-26 12:06 ` John A. Sullivan III
2004-01-25 5:31 William Knop
2004-01-25 16:56 ` Alexis
2004-01-25 17:09 ` Unknown, Alistair Tonner
2004-01-24 21:25 William Knop
2004-01-25 4:27 ` Alexis
2004-01-25 8:57 ` Antony Stone
2004-01-25 9:18 ` Antony Stone
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=1075204015.1891.0.camel@jasiiitosh.nexusmgmt.com \
--to=john.sullivan@nexusmgmt.com \
--cc=bmcdowell@coxhealthplans.com \
--cc=netfilter@lists.netfilter.org \
--cc=w_knop@hotmail.com \
/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