Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Rudi Starcevic <tech@wildcash.com>
To: netfilter@lists.netfilter.org
Subject: Re: Fwd: Route packets from an interface to another
Date: Mon, 12 Sep 2005 07:39:58 -0700	[thread overview]
Message-ID: <4325933E.1070902@wildcash.com> (raw)
In-Reply-To: <65aa6af90509111432525f4bd6@mail.gmail.com>

Hi,

> What is it you want to achieve? 

eth0 -> 192.168.2.0/24
eth1 -> 192.168.3.0/34

I want to achieve two seperate networks.

I want traffic from eth1 to go via eth0
which will link the two LANS and provide
Internet access.

> I don't see any firewall configuration at all....
> your route is wide open... so to speak.

Yes, I have not added any firewalling yet.
This is for my 3 machines at home.

After I am happy with my routing I intend to add
Firewalling rules, VPN and learn about bandwith shaping.

> In case you want to enable forwarding from the lan boxes to internet,
> just enable forward, masquerade output and that's it. 

It would be this simple if there was just one LAN.

> Creating two separate routing tables is not a must.

The issue here is how to route packets from one NIC to another.
Deciding on which networks to use and why is another question.

> Once the network interfaces
> come up, they set the route.... just make sure the default gateway is
> set as well.

Won't the default route for eth0 be 192.168.2.6 and won't the default
route for eth1 be 192.168.3.6 ?

I fail to see how "Once the network interfaces come up,
they set the route" will make packets from eth1 will
auto-magiclly go out eth0 as eth1 default route is not eth0 by default.

Regards,
Rudi.



  reply	other threads:[~2005-09-12 14:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:51 Route packets from an interface to another Jonathan
2005-09-09 21:36 ` /dev/rob0
2005-09-09 21:18   ` Jonathan
2005-09-10  4:45     ` /dev/rob0
2005-09-10  7:54       ` /dev/rob0
2005-09-12  7:56         ` Jonathan
2005-09-13  1:45           ` /dev/rob0
2005-09-12 13:36       ` Rudi Starcevic
     [not found]         ` <65aa6af905091114314108597e@mail.gmail.com>
2005-09-11 21:32           ` Fwd: " Edmundo Carmona
2005-09-12 14:39             ` Rudi Starcevic [this message]
     [not found]               ` <65aa6af9050911145833fa12fd@mail.gmail.com>
2005-09-11 21:58                 ` Edmundo Carmona
2005-09-12 15:06                 ` Fwd: " Rudi Starcevic
     [not found]                   ` <65aa6af9050911151962bc24a2@mail.gmail.com>
2005-09-11 22:20                     ` Edmundo Carmona
2005-09-12 15:19                     ` Rudi Starcevic
2005-09-11 21:34         ` /dev/rob0
2005-09-12 14:47           ` Rudi Starcevic
2005-09-12 14:51           ` Rudi Starcevic

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=4325933E.1070902@wildcash.com \
    --to=tech@wildcash.com \
    --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