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 13:56:27 -0300	[thread overview]
Message-ID: <1075049787.1636.7.camel@pepelui.baicom> (raw)
In-Reply-To: <A9EB4907-4EF7-11D8-A7CD-000A9577164C@hotmail.com>

in this case (i understand now)
Like Antony said, the better approach is to make a linux box with
netfilter as firewall and 2 nics.

One of this nics connected to the dsl modem and the other nic as the
LAN. 

So all boxes inside de lan are connected, and you must configure nat in
the linux box in order to the LAN boxes reach internet.



On Sun, 2004-01-25 at 02:31, William Knop wrote:
> Say I want to transfera file from one computer to another in my house.
> Since they are ondifferent subnets, the data is routed out my modem to
> the gateway atmy isp, and then back in my modem and to the other
> computer in myhouse. Ideally (in any reasonable setup), the data
> should not leavethe house and flood my dsl modem with local traffic.
> 
> So, I want to grab packets destined for the gateway (via
> afirewall/iptables), check if the packet is destined for one of
> thethree local subnets, and make the packet go directly to
> it'sdestination. I'm not sure if this has to do with ethernet
> frames,tcp/ip, or arp or something like that, but I've tried lots of
> thingswith minimal success.
> 
> 
>         im not shureif 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
>         viadhcp, 
>         >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 itvery 
>         >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
>         > 
>         > 
>         > 
>         > 
> 
-- 
Alexis <alexis@attla.net.ar>



  reply	other threads:[~2004-01-25 16:56 UTC|newest]

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

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=1075049787.1636.7.camel@pepelui.baicom \
    --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.