Router firewall issue

[Muse]

I'm using a Buffalo WHR-HP-G54 wireless router with a DSL modem supplied by my ISP, Sonic.net. Generally I get around 5Mbps, sometimes more sometimes less. I have an issue wherein Cisco Webex recordings that should load (i.e. stop "buffering...") after 15-30 seconds typically don't stop buffering and start playing for 4-10 or more minutes, usually closer to 10 minutes. This is not a common problem and I've been working with the tech support at the site that furnishes the files, with Cisco Webex support and with my ISP's support (sonic.net). Webex thinks the problem is with filtering or restrictions by my ISP. My ISP declares that they don't filter, that the problem is likely with my equipment, either my router or modem and they want to send me a router/modem package to test with and if it works they want me to rent the router, which doesn't sit right with me. I don't rent anything!

Well, I am on my 2nd DSL modem over the last several months and had the same problem so I doubt very much it's a problem with the modem. Is it possible I can configure my router in such a way that the problem is resolved? Below is text of a Word file that Webex support sent me today. I'm using Tomato firmware (a Toast version). Where in the firmware could I look to implement the suggestions? I've been poking around and don't see where I can enter exceptions.

Actually, I've tried connecting my desktop directly to the modem, with the modem connected directly to a homerun from the DSL box on the side of my house. I figure this takes the router out of the equation but the times are still just as slow it seems. This is indeed confusing. I brought one of my laptops over to my sister's house yesterday and on her AT&T DSL network (connected wirelessly), the files loaded in 20 seconds on average.
- - - -

To ensure traffic to and from the WebEx domain is routed appropriately through your firewall or proxy servers, review the settings below:
Web browser exceptions
• Add an exception for the entire webex.com domain = *.webex.com.
o At the minimum, the following addresses should be added as exceptions: YOURSITENAME.webex.com and akamaicdn.webex.com.
• ActiveX and/or JavaScript will need to be allowed through the firewall and web browsers should be configured to not restrict ActiveX and/or JavaScript.
• We ask that WebEx sites are not cached (content, IP-path) on proxy servers.
Cisco WebEx Production IP Exceptions
Note: Due to dynamic IP address allocation, WebEx cannot guarantee your WebEx site will operate with a given IP at all times. Therefore, it is necessary to add the full IP address range to ensure proper connectivity to your WebEx site in all situations.
• 64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)
• 66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)
• 66.163.32.0/20 (CIDR) or 66.163.32.0 - 66.163.47.255 (net range)
• 209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)
• 208.8.81.0/24 (CIDR) or 208.8.81.0 - 208.8.81.255 (net range)
• 210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)
• 62.109.192.0/18 (CIDR) or 62.109.192.0 - 62.109.255.255 (net range)
• 173.243.0.0/20 (CIDR) or 173.243.0.0 - 173.243.15.255 (net range)
• 114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range)
Ports used by the WebEx client for communication for both inbound and outbound traffic
Port Port Number Access Type
TCP 80 Client Access
TCP 443 Client Access - Secure Traffic (SSL Sites)
TCP/UDP 1270 Client Access (Non SSL Sites)
TCP/UDP 53 Domain Name System (DNS)
TCP/UDP 5101 MMP
TCP 8554 Audio Streaming Client Access
UDP 7500 Audio Streaming
UDP 7501 Audio Streaming
UDP 9000 VoIP/Video
UDP 9001 VoIP/Video

 

[AFurryReptile]

If it is indeed something to do with a the routing or throttling by your ISP, a VPN connection should at least prevent them from seeing what you're doing. Granted, a VPN connection will in and of itself slow down the connection, but it may work for diagnostic purposes.

You can usually get a free trial from any reputable services out there. I've used both StrongVPN and TorrentPrivacy.

Have you tried a different browser? A different computer? Do all websites choke when Webex is?

 

[Muse]

If it is indeed something to do with a the routing or throttling by your ISP, a VPN connection should at least prevent them from seeing what you're doing. Granted, a VPN connection will in and of itself slow down the connection, but it may work for diagnostic purposes.

You can usually get a free trial from any reputable services out there. I've used both StrongVPN and TorrentPrivacy.

Have you tried a different browser? A different computer? Do all websites choke when Webex is?

I'm unsure what you mean by the VPN, none of the support people I've talked to have mentioned that. My ISP is sending me that DSL modem + N router combination, the support technician (one of the supervisors, and he seems pretty heads up, but I'm not sure) says it's for diagnostic purposes, implying that they are trying to learn something by supplying me with these. There's no upfront additional charge at least to start. Later, after we see what transpires we can discuss what to do. He said a rental fee can maybe be negotiated. I tried to sound him out on the uncertainty of this to get him to quote a figure and he said maybe $6.95 additional a month. I had the feeling that things may play out somehow and differently and I consented to have him send it to me, I should have it today or tomorrow, I figure.


How would I set up a VPN connection? Is that what the modem+router will enable? The ISP (sonic.net) guy said that since they know the router they would be able to walk me through the configurations that he figures might/will solve the problem. He said the fact that they don't know my router is the reason he can't help me with what I have. One of the Webex support guys (actually more than one) did a control session on my computer (yes, I know it's not smart to let other people see and control your machine but I figured I should in this instance and after all these guys are Cisco and I figure I should trust them), and had a look into my router's firmware (Tomato). I watched as he poked through the firmware configurations. I am not at all sure he knew what he was looking for.

I've tried both Firefox (my usual) and IE. I have 3 computers on the network that I use regularly, an ethernet connected desktop (that is usually connected to the router but we've also tried connected directly to the modem), and two wirelessly connected laptops, one of which is Windows 7 64 bit Ultimate, the other computers are WinXP, including another laptop that acts as my data server (on 24/7, with a USB HD).

Anyway I have to figure that since connecting my desktop directly to the modem (taking the router out of the equation) and still experiencing extremely slow connection indicates that the router is NOT the problem. I guess I should call that ISP guy again and ask him about that...

AFAIK, the only website I'm having problems with are involved with Webex. I don't seem to have issues with Youtube, for example. Also, I can stream videos from my Picasa (Google+) albums just fine, I think.
- - - -

"prevent them from seeing what you're doing."

What do you mean by this? Prevent who? Would be hackers? Prevent my ISP's throttling from having an effect? I'm not getting the paradigm/concept here. Thanks for the help.

 

[AFurryReptile]

What do you mean by this? Prevent who? Would be hackers? Prevent my ISP's throttling from having an effect? I'm not getting the paradigm/concept here. Thanks for the help.

I'm not sure a VPN would be a permanent solution, but it might tell you if your traffic is getting throttled. Or if a bad route is causing problems.

A VPN (virtual private network) is a fully encrypted connection with a remote server. All of your web traffic will be tunneled through it, and your ISP will not be able to throttle that traffic based on what it is. Your ISP won't know what it is.

That said, because you're tunneling through a remote server, you WILL see in an increase in latency and a reduction in speed. But it may not affect Webex performance enough to matter.