Web Browsing Performance affected adversely with a single PC uploading
-
The issue was that they expected my PC to have exclusive access to the router for the duration of the ticket.
That is normally about 20 to 30 mins.
That means my whole family is offline for potentially days, and this is unacceptable.
DAYS!? What? It should not take days.
You got to skip level 1 and talk to someone higher up.
-
After tests are run on my end, I submit data and wait for a response. That in itself can take hours. Then some time to investigate the problem on their end etc etc and time slips away. It's not like I've got any SLA guarantees to leverage. I'll get to it eventually but it's not really a pressing concern for me at the moment. We're getting the extra downstream bandwidth I paid for, and I couldn't really care about upstream.
-
I had a similar issue that occurred with either an upload or a download by one machine locking out other machines. This started when I installed pfSense ( 2.2.2) in place of a Cisco ASA.
DSL Supports first move was to have me remove pfSense and of course the problem was solved as far as they were concerned since the problem only existed with pfSense inline.
After much research and packet sniffing I disabled Queue management or Q0S on the DSL router. (F@ST 1704N) That did the trick. It was on by default. Every few months they reset me and I have to turn it off again and re-enter the virtual servers.
What got my eye here is your reference to RRT time increasing. Was the same here.
-
So instead of telling you you had double NAT and two routers they blamed pfSense. Nice, but typical. ISPs can't be expected to support every device under the sun (no matter what their customers might think). Only the ones they provide and even then marginally so.
ISPs responsibility where customer-provided gear is concerned is pretty much to provision the circuit correctly and provide correct configuration specifications.
-
So instead of telling you you had double NAT and two routers they blamed pfSense. Nice, but typical. ISPs can't be expected to support every device under the sun (no matter what their customers might think). Only the ones they provide and even then marginally so.
ISPs responsibility where customer-provided gear is concerned is pretty much to provision the circuit correctly and provide correct configuration specifications.
I could put the Cisco or Linksys back in as they worked fine without the issue described above … NOT ::)
Double NAT is fine as long as you know the limitations ( IPSEC, VPN, UPnP, ect) ;D
The ISP here seems to frown on Bridge Mode. -
They can frown all they want.
-
Still confused, just tell them YEAH only my computer is connected.. The most they can see is the mac of the device connected to their modem.. WTF does what connected behind your router have to do with their network not giving you the speed you paid for??
Just at a complete loss.. The person tell you to do that is some level 1 reading off a script.. So answer his script question with an answer that lets him move to the next question.
-
WTF does what connected behind your router have to do with their network not giving you the speed you paid for??
The implication being that my own router is causing the problem, so get it out of series and test directly between PC and cablemodem.
The person tell you to do that is some level 1 reading off a script.
And that's exactly what I expect when dealing with a consumer service.
