Re: bridge + nat

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxx> 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.
> 
>


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux