From: George Alexandru Dragoi <waruiinu@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: bridge + nat
Date: Mon, 19 Jul 2004 16:31:20 +0200 [thread overview]
Message-ID: <3063e504071907313a194279@mail.gmail.com> (raw)
In-Reply-To: <200407191025.44076.Antony@Soft-Solutions.co.uk>
That is what i wanted to do, with 2 NICs to make a bridge between
internet and the LAN, assign the public ip to one of the LAN machine,
and prite ips to the rest of machines, and to hope it will work, seems
not, i hoped i could do this. If the voip hardware/software wont work
in nat with port forward, i wont change there with linux.
Maybe there is a suggestion for that voip, or if i can do this with 3
NICs, and 1 single public IP.
Thanks in advance
On Mon, 19 Jul 2004 10:25:44 +0100, Antony Stone
<antony@soft-solutions.co.uk> wrote:
> On Monday 19 July 2004 6:46 am, George Alexandru Dragoi wrote:
>
> > Hello, i am trying to make a linux machine as both router and bridge.
>
> How many NICs do you have in the machine?
>
> So long as you are bridging between some group of NICs, and then routing
> between the bridge group and the other NICs, then you should be able to
> simply set up routing, netfilter etc using device name br0 for the bridge.
>
> You cannot do bridging and routing on the same group of NICs.
>
> Hope this helps,
>
> Regards,
>
> Antony.
>
> --
> Software development can be quick, high quality, or low cost.
>
> The customer gets to pick any two out of three.
>
> Please reply to the list;
> please don't CC me.
>
>
next prev parent reply other threads:[~2004-07-19 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 5:46 bridge + nat George Alexandru Dragoi
2004-07-19 9:25 ` Antony Stone
2004-07-19 14:31 ` George Alexandru Dragoi [this message]
2004-07-19 14:48 ` Antony Stone
2004-07-19 17:32 ` George Alexandru Dragoi
2004-07-19 18:17 ` George Alexandru Dragoi
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 17:44 bridge+nat Mikael Nehlsen
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=3063e504071907313a194279@mail.gmail.com \
--to=waruiinu@gmail.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 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.