Ok, going back to the beginning... if you only have one public IP, you will use nat. w2k3 RRAS is probably configured with rules to handle the extra issues with the VoIP protocols... you never said which one, SIP, IAX2, H.323, MGCP... Linux comes blank, no iptables rules, you have to add extra iptables rules to deal with VoIP. It's probably easier than your bridge setup. even a $50 d-link router can do this easily. If you are using SIP ip_nat_sip kernel module can help add the abillity. This is more of a VoIP problem than a linux-net problem, try this: http://www.voip-info.org/wiki/view/Linux+Router and for the actual port forwarding: http://www.voip-info.org/wiki/view/port+forwarding You should also consider using a STUN server outside your network for your voip devices to figure out the type of NAT. On Wed, 2007-11-21 at 16:40 +0000, Mateus Interciso wrote: > On Wed, 21 Nov 2007 10:28:00 -0600, Matt Zagrabelny wrote: > > > On Wed, 2007-11-21 at 16:11 +0000, Mateus Interciso wrote: > >> On Wed, 21 Nov 2007 13:04:40 +0000, Mateus Interciso wrote: > > > > [...] > > > >> Maybe, if I explain a little more about the fisical network we have, it > >> may be easier to understand(or find the problem) > > -- Jeremy Jackson Coplanar Networks (519)489-4903 - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
