All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Colverson <netfilter@vcxz.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: conf scenario.
Date: Mon, 03 May 2004 23:01:01 +0100	[thread overview]
Message-ID: <4096C11D.5000709@vcxz.co.uk> (raw)
In-Reply-To: <200405032156.34614.Antony@Soft-Solutions.co.uk>

Antony Stone wrote:
> On Monday 03 May 2004 9:42 pm, Krystian wrote:
>>i need some help on how to configure this scenario in iptables:
>>
>>[adsl modem/router]-----[eth1-linux box-eth0]-----[network]
>>
>>question: how to configure "linux box's" iptables to forward and
>>masquarade traffic from most users and bridge traffic for couple
>>"public" users.

I don't believe that any iptables configuration is necessary for the 
machines with public IPs. The Linux box will need a public IP on the 
same subnet as them and will need to have IP forwarding turned on (echo 
1 > /proc/sys/net/ipv4/ip_forward). The boxes with public IPs will need 
to have the Linux box as their default gateway and it should all just work.

If you can't spare a public IP for the Linux box, can you just connect 
the ADSL modem/router, the Linux box, and the clients all to the same 
Ethernet? This is the setup I use. In that case the clients with public 
IPs would be able to see the ADSL modem/router directly (and would 
simply use that as their default gateway).

> Add a third interface card eth2, bridge eth1 and eth2 as br0, and then route 
> between br0 and eth0.
> 
> If you have hosts on your network which need public IPs then they have to be 
> on a separate subnet from your normal clients anyway.

I don't think this is necessary. The public IP clients are obviously on 
a different IP subnet, but they can happily share the Ethernet with the 
NATed clients.

-- 
Jon



  reply	other threads:[~2004-05-03 22:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 20:42 conf scenario Krystian
2004-05-03 20:56 ` Antony Stone
2004-05-03 22:01   ` Jon Colverson [this message]
2004-05-03 22:28     ` Antony Stone
2004-05-04 19:58       ` Krystian

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=4096C11D.5000709@vcxz.co.uk \
    --to=netfilter@vcxz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.