All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexis" <alexis@attla.net.ar>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: iptables routing help
Date: Sun, 25 Jan 2004 01:27:11 -0300	[thread overview]
Message-ID: <001601c3e2fb$80507110$0200000a@heretic> (raw)
In-Reply-To: CD650C0C-4EB3-11D8-8BD0-000A9577164C@hotmail.com

im not shure if i can understand the schema, could be more specific?

thanks


----- Original Message ----- 
From: "William Knop" <w_knop@hotmail.com>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, January 24, 2004 6:25 PM
Subject: iptables routing help


> 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.
> 
> Thanks much,
> William
> 
> 
> 
> 



  reply	other threads:[~2004-01-25  4:27 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 [this message]
2004-01-25  8:57 ` Antony Stone
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='001601c3e2fb$80507110$0200000a@heretic' \
    --to=alexis@attla.net.ar \
    --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.