VOIP passthrough

Discussion in 'DD-WRT Firmware' started by RcNorth, Jan 27, 2006.

  1. RcNorth

    RcNorth Network Guru Member

    I've done a few searches and have found some responses, but nothing that appears to be what I'm looking for.

    I have cable internet with two DHCP IP addresses available. I would like to use one for all my internal machines, and the other for my VOIP connection.

    I was wondering if I could plug my VOIP router into one of the 4 ports and configure the port to be in the DMZ and thus get it's IP from the ISP.

    I could accomplish this by having a hub that my cable modem goes into and then the wrt54g and the VOIP router plugged into the hub. But I would like to avoid having another device if possible.

    Any ideas?

  2. RcNorth

    RcNorth Network Guru Member

    Well, I partially accomplished what I wanted to. I was looking for a way to keep the VOIP off my network so that it isn't affected by local traffic.

    I was able to connect the VOIP router (d-link DVG-1120M) to the cable modem, which will get an IP from the ISP. I then connected the WAN port of my WRT54G to the port on the Vd-link. This allows the Linksys to have a static IP on the lan, a DHCP IP to the d-link, and all my internal machines to get a DHCP address from the Linksys.

    The problem I think I'm going to have to accessing my local network from outside, for such things as VNC, remote desktop etc. I'm guessing that the d-link is not going to forward the traffic to the Linksys properly. I'm going to do some research to see how to configure NAT for the d-link.

    If anyone knows how I can hook up everything differently and still have inbound traffic, please let me know. I've never messed with iptables and know very little about Linux yet, so please keep this in mind.


  3. RcNorth

    RcNorth Network Guru Member

    ok, I know that these messages are in quick succession, but I thought that others might want to know what I found.

    I was able to configure the dlink to allow the ethernet port to pass through everything by turning off NAT on the dlink and turning on bridging. It would have been easier had the dlink had a DMZ, but I wasn't that lucky.

    With DHCP enabled on the dlink, the linksys is now able to get an IP address from the ISP. It took a while to figure this one out as I thought that if the dlink has DHCP turned on, that it would try to assign the Linksys an IP from it's own pool, but it appears to just be allowing the DHCP to pass through as well.

    So this means that both the dlink and Linksys are both receiving IPs from the ISP. I'm lucky enough to have an ISP that includes two IPs.

    So now for the last thing to figure out. How can I gain access to the dlink's web interface without having to attach the PC directly to it. Currently the LAN are all in an 192.168.15 range, with the dlink being assigned But because of the bridging, the pc isn't seeing the dlink.

    Does anyone know of a way that I can tell the linkSys that it needs to pass destined traffic to the WAN port so that it makes it to the dlink?
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice