1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

wrt54gp2-na and voip, behind another firewall

Discussion in 'Other Linksys Equipment' started by raxhonp, Dec 12, 2005.

  1. raxhonp

    raxhonp Network Guru Member

    I have my wrt54gp2-na behind another firewall (smoothwall) and have set it up to act as a simple router: no use of the wan, fixed IP, plugged in my network using the local interface 1. I have 2 other computers connected to it and a laptop using the wireless connection working just fine, using the DHCP on my smoothwall box.

    I tried everything I could do have the voip working with such a setup but can't have a connection to the sip server. I think the integrated ATA uses by default the wan interface. Am I correct?

    Any way I could route the sip calls to my existing lan?

    Another option would then be to setup the linksys to act as a transparent gateway, using the wan interface to connect to my existing lan. Any idea how to achieve this?
     
  2. NateHoy

    NateHoy Network Guru Member

    As far as I know, the WRTP54G needs to have an Internet connection plugged into its WAN port to get the Vonage line running.

    To make it as transparent as possible, you can try just turning off the firewall, DHCP servers, and everything else you can find. I haven't tried it, but it should then act as a transparent gateway. I don't know how well it would work for file sharing, etc, but it's worth a shot...

    There is no routing feature built into the unit that would allow it to turn one of its LAN ports into a "client" port, and serve the Vonage from the "LAN" side. At least none that I know of.

    A cheap switch would solve your problem, though it means $. Buy a switch, and plug the Vonage router and your other computers into it.

    One person on the Vonage forum ( www.vonage-forum.com ) claimed to be able to get it running by (get this!) running a patch cable from one of the LAN ports on the WRTP54G to the WAN port of the SAME WRTP54G. To me, this = network loop = REALLY, REALLY bad idea.
     
  3. bluerhinoceros

    bluerhinoceros LI Guru Member

    WRT54GP2 Behind Another Router

    I just plugged the WRT54GP2's WAN port into one of my my existing router's LAN ports, and it worked fine for (separate) LAN on each of them, 802.11x on each, and VOIP on the LinkSys. The caveat was that the LinkSys is a bit braindead (firmware 1.30.01) when I accepted the default of DHCP on the WAN side. In this case, it seemed to insist that its address was the network address (x.x.x.0), not the DHCP-assigned address. My router then saw any attempt to communicate between the two LANs as a smurf attack. I wanted the two LANS to be able to talk, so I tried a static address on the LinkSys' WAN port. My original router isn't sophisticated enough to have a programmable route table. Works fine now.

    Hope this helps.

    Cheers.

     
  4. bluerhinoceros

    bluerhinoceros LI Guru Member

    WRT54GP2 Behind Another Router

    I just plugged the WRT54GP2's WAN port into one of my my existing router's LAN ports, and it worked fine for (separate) LAN on each of them, 802.11x on each, and VOIP on the LinkSys. The caveat was that the LinkSys is a bit braindead (firmware 1.30.01) when I accepted the default of DHCP on the WAN side. In this case, it seemed to insist that its address was the network address (x.x.x.0), not the DHCP-assigned address. My router then saw any attempt to communicate between the two LANs as a smurf attack. I wanted the two LANS to be able to talk, so I tried a static address on the LinkSys' WAN port. My original router isn't sophisticated enough to have a programmable route table. Works fine now.

    Hope this helps.

    Cheers.

     

Share This Page