Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: iptables routing help
Date: Sun, 25 Jan 2004 08:57:37 +0000	[thread overview]
Message-ID: <200401250857.37939.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <CD650C0C-4EB3-11D8-8BD0-000A9577164C@hotmail.com>

On Saturday 24 January 2004 9:25 pm, William Knop wrote:

> Hello,
> My dsl provider has my house on several subnets (ips obtained via dhcp,
> along with a netmask of 255.255.255.0), so I have had to screw around
> with each machine to make sure local traffic doesn't flood the dsl
> modem. To remedy this, I've been trying to set up a firewall box to
> basically reroute those three subnets as local, but I'm finding it very
> difficult. It seems like every doc out there only addresses nat, which
> is definitely not what we want. I'd greatly appreciate some help
> accomplishing this.

This is not a netfilter question - in fact quite the opposite - it is an IP 
routing question, which netfilter will only help to interfere with.

All netfilter would do for you in a case like this is help to drop packets 
which would otherwise be routed.   Netfilter doesn't route packets - that's 
the job of the normal routing table.

Many times on this list a question is answered with "get your basic routing 
working first, then start implementing netfilter rules to drop things you 
don't want."   In your case the correct routing table entries will solve your 
problem - there's almost certainly no need for netfilter to be involved 
except as the perimeter firewall just before your networks hit the DSL.

I suggest you start with something like 
http://www.linux.org/docs/ldp/howto/Networking-Overview-HOWTO.html or 
http://www.linux.org/docs/ldp/howto/IP-Subnetworking.html - alternatively a 
standard IP book such as O'Reilly's "TCP/IP Network Administration" by Craig 
Hunt will tell you what you need.

The main thing is to make sure you don't have netfilter rules blocking what 
your routing table would otherwise allow between your local subnets.

Hope this helps,

Antony.

-- 
Most people are aware that the Universe is big.

 - Paul Davies, Professor of Theoretical Physics

                                                     Please reply to the list;
                                                           please don't CC me.



  parent reply	other threads:[~2004-01-25  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24 21:25 iptables routing help William Knop
2004-01-25  4:27 ` Alexis
2004-01-25  8:57 ` Antony Stone [this message]
2004-01-25  9:18 ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-01-25  5:31 William Knop
2004-01-25 16:56 ` Alexis
2004-01-25 17:09 ` Unknown, Alistair Tonner
2004-01-25 18:53 William Knop
2004-01-26 12:06 ` John A. Sullivan III
2004-01-26 16:29 bmcdowell
2004-01-27  4:37 ` William Knop
2004-01-27 11:46   ` John A. Sullivan III

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=200401250857.37939.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