I can't stream music/movies to my 360 since we got Vonage...
Since getting Vonage I can't stream anything to my xbox because instead of the ethernet cable from my PC going into my modem/gateway it HAS to go into the Vonage module, thing; or else I cant connect to the internet or make phone calls...I've tried using an old router as a switch. I plug an ethernet cable from my PC to this switch, then from the router a cable to the vonage module thing, and one to my modem/gateway, but to no avail.Please..does anyone have a suggestion ? It'd be greatly apperciated. Thanks in advance
what i have to do to connect to internet/make phone calls:
Wall Jack to Modem, Modem To Vonage, PC to Vonage
(this is where i have problems, in order to stream over LAN i need a connection from my pc to my modem, and this doesn't allow me to do so...>_< )
what i was thinking of doing:
PC to Switch, Switch to Vonage, Switch to Modem, Modem to Vonage (for internet connectivity)
There are several ways to solve this problem, each w/ increasing complexity, but w/ significantly increasing advantages.
The simplest solution is to just connect the VDV21-VD to the WRT54GS, LAN to WAN, respectively. You're just creating another local network behind those already defined by VDV21-VD and 2701. In order for this to work properly, you have to make sure the 2107, VDV21-VD, and WRT54GS are using different subnets (e.g., 192.168.1.x, 192.168.2.x, 192.168.3.x).
[2701 (192.168.1.x)](lan)<-- wire -->(wan)[vdv21-vd (192.168.2.x)](lan)<-- wire -->(wan)[wrt54gs (192.168.3.x)]
As simple as that is, it also means you have three (3) NAT routers and firewalls between the Internet and your wired and wireless clients on the WRT54GS, which significantly complicates firewall management (e.g., port forwarding). So we’d prefer to eliminate those extraneous firewalls.
You were on the right track to removing one of those firewalls by trying to use the WRT54GS as a switch. The mistake was not disabling its DHCP server. You also need to give the WRT54GS a static IP address in the same subnet as the VDV21-VD, and finally connect them LAN to LAN.
[2701 (192.168.1.1)](lan)<-- wire -->(wan)[vdv21-vd (192.168.2.1)](lan)<-- wire -->(lan)[wrt54gs (dhcp disabled, 192.168.2.2)]
Now we only have two firewalls (2701 and VDV21-VD).
But we can do better. If we place the 2701 in bridge mode, that will demote the 2701 to just a modem (no routing, no local network). So now the only router and firewall in the chain is the VDV21-VD.
[2701)](lan)<-- wire -->(wan)[vdv21-vd (192.168.1.1)](lan)<-- wire -->(lan)[wrt54gs (dhcp disabled, 192.168.1.2)]
But we can do even better. I’m willing to bet you’d rather have your own router (WRT54GS) in control rather than the VDV21-VD (esp. when the VDV21-VD has been forced on you for the sake of VOIP). To do that, re-enable DHCP on the WRT54GS and connect the VDV21-VD to the WRT54GS, LAN to WAN, respectively. Give the WRT54GS’s WAN port a static IP in the same subnet as the VDV21-VD. Finally, place that IP address in the DMZ of the VDV21-VD. Now any inbound traffic otherwise not intercepted by the VDV21-VD on behalf of VOIP is just passed to the WRT54GS! For all intents and purposes, the VDV21-VD is just acting as a filter.
(lan)<-- wire -->(wan)[vdv21-vd (192.168.1.x)](lan)<-- wire -->(wan)[wrt54gs (192.168.2.x)]
This is the ideal configuration, imo. The 2701 is now just a modem. The VDV21-VD just filters out VOIP traffic. Everything else just works its way down to the WRT54GS as normal. The WRT54GS is the only router/firewall you ever need to manage. If it’s too overwhelming, just start w/ the simplest configuration, then move to the next. While the simplest configuration will always work, any progress made towards the more sophisticated configurations will be worth it, imo.