From: George Alexandru Dragoi <waruiinu@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: bridge + nat
Date: Mon, 19 Jul 2004 21:17:55 +0300 [thread overview]
Message-ID: <3063e504071911176fbdbad4@mail.gmail.com> (raw)
In-Reply-To: <3063e5040719103222676063@mail.gmail.com>
False Alarm
There is no voip, it is just that computer with a modem for fax
stuff, the friend who asked for help just told me. Anyway,it is good
to know i can't use the bridge that way. Thank you Anthony again
On Mon, 19 Jul 2004 20:32:55 +0300, George Alexandru Dragoi
<waruiinu@gmail.com> wrote:
> Somebody told methere are situations where you can specify to voip
> software(or hardware, i have no ideea how voip works) which ip should
> expect to have for port forward situations. Well seems i have to stay
> with windows and winproxy who like to suggest to browsers to download
> index.html from google.com :), and no QoS.
>
> Thank you for clarifying
>
>
>
> On Mon, 19 Jul 2004 15:48:30 +0100, Antony Stone
> <antony@soft-solutions.co.uk> wrote:
> > On Monday 19 July 2004 3:31 pm, George Alexandru Dragoi wrote:
> >
> > > 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.
> >
> > No. With 2 NICs you can either bridge, or route, but not both.
> >
> > With 3 NICs you could bridge 2 of them together, and route between the bridged
> > pair and the 3rd NIC, however in this situation I think you would need to
> > have an IP address on the bridged pair, and you say you have only 1 public IP
> > address available?
> >
> > > 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.
> >
> > With only 1 public IP address I think you are stuck as soon as you assign that
> > address to any machine except the VoIP server.
> >
> > Why do people keep on coming up with protocols which don't work across NAT?
> >
> > NAT works at OSI layer 3. Any higher level protocols should not care about
> > it.
> >
> > Regards,
> >
> > Antony.
> >
> > --
> > There's no such thing as bad weather - only the wrong clothes.
> >
> > - Billy Connolly
> >
> >
> >
> > Please reply to the list;
> > please don't CC me.
> >
> >
>
next prev parent reply other threads:[~2004-07-19 18:17 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
2004-07-19 14:48 ` Antony Stone
2004-07-19 17:32 ` George Alexandru Dragoi
2004-07-19 18:17 ` George Alexandru Dragoi [this message]
-- 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=3063e504071911176fbdbad4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox