QoS through switch then to router?

Posts: 3 · New Forum Member Joined: Mar 28, 2005 Posts: 3

Actually, the echo is only with certain callers (I've noticed it mainly from Verizon cell phones). The choppiness though was universal whenever there was a load on the network.

I moved the PAP2 now to be directly connected to the WRTG54V1 router. We'll see if it makes a difference. FYI, I'm running the stock Linksys 3.03.6 firmware. I've configured QoS for the port this time, and not the MAC.

Posts: 482 · Posted: Wed Mar 30, 2005 1:38 am Post subject:

That won't really do any good if the port is connected to a switch where your Vonage adapter is also sitting alongside other active PC connections, as your diagram indicates. You need to plug the Vonage adapter right into the WRT54G if you want to use QoS that way. The only way I can think of using QoS that wouldn't require changing your topology would be to set QoS based on the protocol, which would be SIP in this case. But I also don't know if that's supported in the stock firmware.

Posts: 66 · Full Forum Member Joined: Feb 07, 2005 Posts: 66

I set mine up with the MAC id, worked fine..
Also set it up with the Lan port it is on.. Works better..

It would be better if it is on the router port itself and not a switch, but if you dont have a choice, then u dont..

Alchemy or DD-Wrt #21 will work great too.. Better working with the up and down side of the bandwidth

Posts: 1 · New Forum Member Joined: Mar 24, 2005 Posts: 1

Hello all. Relative to this subject - I was hoping to get a confirmation of my equipment sequence and perhaps solicit suggestions for more efficiency.

Current sequence:

Cable Modem -> Linksys WRT54GS -> 2 PC's and RT31P2
The system has been connected about five days and incoming calls sound as good as or better than the local phone company. Outgoing, however, is hit-and-miss. The main complaint I'm hearing is a comparison to a "choppy cell phone" connection.

I've read through a majority of the relative posts here, and adjusted my WRT54GS QOS to high on the RT31P2 port and per the Voip speed test I get +/- 2700 down & +/- 360 up with a QOS of +/- 90%. This seemed to help my outgoing calls, but I'm not sure if it's the best connection I can expect.

Now here's where I reveal my novice networking capabilities. My home network is configured for a 192.168.1.xx IP range, but the RT31P2 device defaults to a 192.168.15.XX range. As a result, I can't see the RT31P2 configuration web-based utility with my current setup without directly connecting the WAN cable and main PC Ethernet cables into it. If I try to reassign the IP of the RT31P2 to a 1.XX it acknowledges the change, but then won't allow the config. utility to run. I then reset the RT31P2 and reconnect the original config and it all works as before. Is there another way of configuring my 1.XX network to see the 15.XX device? If so and it's successful, do I need to tweak any of the settings on the RT31P2 device to perhaps improve the outgoing calls? Or should I leave good enough alone and be glad that I'm saving $100 / month with Vonage?

Thanks in advance.

Posts: 482 · Posted: Sun Apr 03, 2005 1:50 am Post subject: Re: Equipment Sequence?

arkatct wrote:

Current sequence:

Cable Modem -> Linksys WRT54GS -> 2 PC's and RT31P2

Now here's where I reveal my novice networking capabilities. My home network is configured for a 192.168.1.xx IP range, but the RT31P2 device defaults to a 192.168.15.XX range. As a result, I can't see the RT31P2 configuration web-based utility with my current setup without directly connecting the WAN cable and main PC Ethernet cables into it. If I try to reassign the IP of the RT31P2 to a 1.XX it acknowledges the change, but then won't allow the config. utility to run.

You need to set the WAN side of the RT31P2 to a static 192.168.1.x address outside the DHCP scope of the WRT54GS and also turn on Remote Administration. Then you'll be able to admin the RT31P2 from your PC by going to http://192.168.1.x:8080. You need to specify port 8080 when you're coming in fron the WAN side of the RT31P2 because Remote Administration runs on port 8080.