From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Howto route through
Date: Sun, 31 Oct 2004 17:32:30 +0000 [thread overview]
Message-ID: <200410311832.30566.stef.coene@docum.org> (raw)
In-Reply-To: <41850B0D.9000409@draxinusom.ch>
On Sunday 31 October 2004 16:55, Rene Gallati wrote:
> Hello list,
>
> I'm having a little trouble imagining a setup I'll soon have.
>
> I am in the process of getting a routed /28 to my homeLAN. What I want
> to do is to put a linux box in front of the lan to filter some of the
> unneeded and potential dangerous ports. Now the box has 2 nics, one for
> the inside one for the outside.
>
> How should I go on to setup those NICs when
> a) the PCs in the net should have their official IP address from the /28
> net and
> b) the filtering linux box should at the same time have one IP address
> from the same range for some services it provides
>
> The dilemma I see (maybe it is none but I just don't know)
> if I put it this way that I have the IP of the /28er range on one nic
> and nothing to put on the other ?
You can give the nics the same ip address. Just be carefull with the routing,
you need the specify the nic when you add a route so the packets are going
out on the interface they have too.
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/
next prev parent reply other threads:[~2004-10-31 17:32 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 [this message]
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
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=200410311832.30566.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.