All of lore.kernel.org
 help / color / mirror / Atom feed
From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Firewall.routing configuration problems
Date: Thu, 20 Oct 2005 14:17:13 -0500	[thread overview]
Message-ID: <200510201417.13180.rob0@gmx.co.uk> (raw)
In-Reply-To: <003c01c5d595$00853360$e7544381@SANNPJLTABLET>

On Thursday 2005-October-20 11:40, Paul Lewis wrote:
> iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE -o
> eth3

Are you thinking that the "-o eth3" will modify the behaviour of the 
MASQUERADE target? It will not. It merely modifies which packets match 
the rule. The above matches packets with source address 192.168.0.0/24 
which are routed out device eth3.

See also SNAT, which is more appropriate with static IP addresses. 
MASQUERADE is for home users and dynamic IP addresses.

IIUC your issue, which I might not because I didn't spend much time on 
it, it's routing. You need to have routes for your conference guests. 
Furthermore as has been suggested here to me (and I concur) you should 
start unlearning route(8) and ifconfig(8) and start learning ip(8) from 
iproute2, which is far more powerful and capable.
-- 
    mail to this address is discarded unless "/dev/rob0"
    or "not-spam" is in Subject: header


      parent reply	other threads:[~2005-10-20 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 16:40 [LARTC] Firewall.routing configuration problems Paul Lewis
2005-10-20 16:40 ` Paul Lewis
2005-10-20 17:03 ` [LARTC] " Peter Surda
2005-10-20 19:17 ` /dev/rob0 [this message]

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=200510201417.13180.rob0@gmx.co.uk \
    --to=rob0@gmx.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.