From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: IP Alias with iptables
Date: Wed, 21 Apr 2004 08:50:03 +0100 [thread overview]
Message-ID: <200404210850.03709.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <EMEKLOMJOPNJPAFKHEDJOEDGCDAA.rhaces_chistes@yahoo.com.mx>
On Wednesday 21 April 2004 12:39 am, Rodrigo Haces wrote:
> Thanks for this, hope this is my last post:
>
> assuming this will allow all 192.168.1.0/24 go to 192.168.0.0/24 how could
> i do if i want not all the subnet, but only 192.168.1.10, i suppose is with
> the -s option, but im not sure of how to use this.
iptables -A FORWARD -i eth0 -o eth1 -s 192.168.1.10 -j ACCEPT
Regards,
Antony
> > -----Mensaje original-----
> > De: netfilter-admin@lists.netfilter.org
> > [mailto:netfilter-admin@lists.netfilter.org]En nombre de Antony Stone
> > Enviado el: Martes, 20 de Abril de 2004 01:33 a.m.
> > Para: Netfilter
> > Asunto: Re: IP Alias with iptables
> >
> > On Tuesday 20 April 2004 4:08 am, Rodrigo Haces wrote:
> > > New Situation:
> > >
> > > eth0: 192.168.1.1 Connected to hub 1
> > > eth1: 192.168.0.1 Connected to hub 2
> > >
> > > hub 1 is for guests
> > > hub 2 is for administrative porposes, and MUST be able to use network
> > > 192.168.0.x and 192.168.1.x
> >
> > So, the firewall needs to allow 192.168.1.0/24 addresses to connect to
> > 192.168.0.0/24 but not the other way round.
> >
> > > so this is something i thought.
> > >
> > > eth0... 192.168.1.1 netmask 255.255.255.0
> > > eth1... 192.168.0.1 netmask 255.255.0.0
> >
> > Doesn't look good.
> >
> > > eth1:1. 192.168.1.101 netmask 255.255.0.0
> >
> > Looks as bad as the first idea, with only one interface.
> >
> > > my laptop is part of the administrative sector, i have
> >
> > 192.168.0.10 ip, but
> >
> > > i need to be able to use also 192.168.1.10 so i can monitor guests,
> >
> > What is wrong with yur laptop havign just one IP address (that *is*
> > conventional, after all), and the firewall allowing it to
> > "monitor" addresses
> > in the other subnet? Perhaps you should explain more about what
> > you mean by
> > "monitor"?
> >
> > > Any ideas
> >
> > Yes. Have two subnets with separate address ranges, a firewall
> > in between,
> > and allow one subnet to connect to the other, but not the other way
> > round.
> >
> > eg:
> > eth0 192.168.1.1 netmask 255.255.255.0
> > eth1 192.168.0.1 netmask 255.255.255.0
> >
> > iptables -P FORWARD DROP
> > iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> > iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT
> >
> > Regards,
> >
> > Antony.
> >
> > --
> > Success is a lousy teacher. It seduces smart people into
> > thinking they can't
> > lose.
> >
> > - William H Gates III
> >
> > Please reply
> > to the list;
> > please
> > don't CC me.
--
"It would appear we have reached the limits of what it is possible to achieve
with computer technology, although one should be careful with such
statements; they tend to sound pretty silly in five years."
- John von Neumann (1949)
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-04-21 7:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 15:41 IP Alias with iptables Rodrigo Haces
2004-04-19 14:53 ` Antony Stone
2004-04-19 16:07 ` Rodrigo Haces
2004-04-19 15:25 ` Antony Stone
2004-04-19 16:12 ` Alistair Tonner
2004-04-19 21:31 ` Antony Stone
2004-04-20 3:08 ` Rodrigo Haces
2004-04-20 7:33 ` Antony Stone
2004-04-20 23:39 ` Rodrigo Haces
2004-04-21 7:50 ` Antony Stone [this message]
2004-04-20 18:06 ` Dick St.Peters
2004-04-20 18:27 ` Antony Stone
2004-04-19 16:55 ` Rodrigo Haces
2004-04-19 15:43 ` Cedric Blancher
2004-04-19 15:22 ` Michael Gale
[not found] <006901c4261e$01f081f0$0c00a8c0@pepelui>
2004-04-19 16:20 ` Rodrigo Haces
2004-04-19 15:28 ` Alexis
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=200404210850.03709.Antony@Soft-Solutions.co.uk \
--to=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