From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Howto route through
Date: Tue, 02 Nov 2004 20:04:01 +0000 [thread overview]
Message-ID: <200411022104.01526.stef.coene@docum.org> (raw)
In-Reply-To: <41850B0D.9000409@draxinusom.ch>
On Monday 01 November 2004 15:44, Rene Gallati wrote:
> Hm that is a solution, however how do I "attract" the traffic for the
> PCs in the LAN? I can either assign all IPs as aliases which looks a bit
> crude or use proxyArp or bridging to convey the traffic over from one
> side to the other.
The isp should route all traffic for your 1.2.3.0/28 range to 1.2.3.1.
From your example: Range is 1.2.3.0/28 (1.2.3.0 - 1.2.3.15)
eth0: 1.2.3.1 eth1: 1.2.3.1
---- Internet ------- FW Box ------ LAN (1.2.3.0/28)
default gw lan machines: 1.2.3.1
default gw firewall: assigned gw from your isp (in 1.2.3.0/28)
ip route add default via 1.2.3.X dev eth0
routes on your firewall: for each lan, going out on eth1:
ip route add 1.2.3.1 dev eth0
(don't know if this works, but it's to make sure packets for the lan
host 1.2.3.1 are leaving out on eth1)
> At the moment, transparent bridge filter looks like the best idea to me,
> however the lan nic is a gigE card so I don't know if running it in
> promiscous all the time would be a good idea.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-11-02 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 15:55 [LARTC] Howto route through Rene Gallati
2004-10-31 17:32 ` Stef Coene
2004-10-31 17:32 ` Chris Bennett
2004-11-01 2:47 ` gypsy
2004-11-01 14:44 ` Rene Gallati
2004-11-01 14:56 ` Rene Gallati
2004-11-01 15:11 ` Rene Gallati
2004-11-02 20:04 ` Stef Coene [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=200411022104.01526.stef.coene@docum.org \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.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.