(E-Mail Removed) (Mark T.B. Carroll) wrote in
news:(E-Mail Removed):
> I used to have Vonage with a Road Runner cable modem and back then the
> VoIP worked just fine sat behind my Linux box that provided DHCP and NAT
> for it. Lingo and BroadVoice have also worked fine with this type of
> arrangement. (Now I have an irrelevantly-weird ISP, but still.)
Yes, that is what I wanted to do too.
> What network traffic do you see on your home Linux gateway when you
> watch with tcpdump or wireshark or whatever? Can you look for the Vonage
> box getting its DHCP IP address, can you see its attempt at an outbound
> connection, both reaching the gateway from the LAN, and being passed
> onto the WAN by the gateway? The problem, or at least where it is, might
> become clear if you watch what's happening.
Too late. As much as I want to make this work with my linux box providing
the NATs, I really need the phone, like NOW, so I took the Linksys PAP2
back and exchanged it for a Linksys WRT54GP2. It has a router in it. I plug
the Linksys into the cable modem, the telephones into the Linksys, and the
three computers into the Linksys, and it all works.
This looks like a pretty good router so I will stick the Linux box into the
DMZ so that the servers will work again. It does work with DynDNS but I use
Zoneedit and so I will just go back to the old way with scripts in my dchp
exit hooks file.
> (Note that IME normal netstat doesn't report things NAT'ed through the
> machine, but http://tweegy.demon.nl/projects/netstat-nat/ can do it.)
>
> HTH,
>
> Mark.
I really, really wanted to make it work but the PAP2 was having none of it.
Perhaps a different adapter would have accepted my Linux router, all the
computers do, but not that PAP2.
--
~Ohmster
theohmster at comcast dot net
Put "messageforohmster" in message body
to pass my spam filter.