Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[samssf]

Hello,

I'm trying to figure out why my internet connection (web page fetches, connections to IM servers, anything) ceases to function when I'm doing something like uploading a file, uploading photos to Flickr, etc. I'm not torrenting or doing any P2P type stuff.

I never had this problem with my Time Capsule (similar to all the other issues with this router).

1) Does everyone else have this problem? Is it just something I'm supposed to deal with or work around?
2) If not, how do I fix it?

I've tried with QoS on and off without a noticeable difference.

[alien]

Try to use QOS on the avanced menu in the router

[zim2dive]

yeah.. if my AEXn had supported QOS, I'd have never left... but alas here I am fighting this f/w.

for web traffic, try seeing if the WISH setting make any difference.

[ironic77]

More importantly, if you are using QOS, make sure the upload bandwidth is set properly.  Sometimes mine will detect a bit faster than I know is stable, so I just set it a touch lower, which also has the added benefit of faster boot times.

I'm hoping for the day when my ISP doesn't limit to 380kbps.  I mean, they offer 12Mbps down.  How in the world do they justify such a small upload?  I'm not trying to share out files -- simply would be nice to be able to upload some pictures to flickr, etc. at a reasponable speed.

[EddieZ]

Hello,

I'm trying to figure out why my internet connection (web page fetches, connections to IM servers, anything) ceases to function when I'm doing something like uploading a file, uploading photos to Flickr, etc. I'm not torrenting or doing any P2P type stuff.

I never had this problem with my Time Capsule (similar to all the other issues with this router).

1) Does everyone else have this problem? Is it just something I'm supposed to deal with or work around?
2) If not, how do I fix it?

I've tried with QoS on and off without a noticeable difference.

Tech specs about this:
Normally, your ISP upload bandwidth is much smaller than your download bandwidth.
TCP/IP needs to communicatie two-ways, so if your upload is crammed your PC will not be able to respond quickly since the response needs to wait until other packets are sent (uploaded).

That's where QoS comes in: you can give a 'priority stamp' with QoS to packets sent.
Can you give us a pirint of your QoS config? If you set something wrong QoS won't work...

[samssf]

Yeah, it appears this was a result of the QoS improperly detecting my uplink bandwidth. I'm not quite sure why the problem would occur with QoS is disabled, though. My Time Capsule didn't have QoS and didn't exhibit this issue. Perhaps it's the quality of my line, time of day, or other things.

I'm paying for 384Kbps or so from AT&T, but I'm measured it at 182Kbps using Speakeasy a few times. The router had measured it at 220.

So this time it's a big F U to AT&T. I already have an install date for Comcast for the 25th which includes a 3Mbps uplink.

[samssf]

Tech specs about this:
Normally, your ISP upload bandwidth is much smaller than your download bandwidth.
TCP/IP needs to communicatie two-ways, so if your upload is crammed your PC will not be able to respond quickly since the response needs to wait until other packets are sent (uploaded).

That's where QoS comes in: you can give a 'priority stamp' with QoS to packets sent.
Can you give us a pirint of your QoS config? If you set something wrong QoS won't work...

QoS only ever operates on packets sent. So it allows you to configure which types of sent packets receive priority (HTTP, FTP, etc) by specifying remote port, local port, IP addresses, etc.

Everything becomes unusable because my machine has to sent packets out to retrieve a web page, and those packets never reach the destination, or take a long time to do so.

[EddieZ]

QoS only ever operates on packets sent.

That's what I said...

Everything becomes unusable because my machine has to sent packets out to retrieve a web page, and those packets never reach the destination, or take a long time to do so.

That's why you use QoS....like I said

[tentimes]

I had this exact problem and posted about it around a year ago. It was due to the uplink speed not being measured correctly and then QoS kicked in and strangled the downlink when it thought the uplink was saturated. The solution was to manualy set the uplink speed in QoS settings. I can't remember where that was in the menu but if you seek you shall find! Don't turn QoS off though as it works well when it knows your uplink/downlink.

[EddieZ]

I support tentimes, you can easily set the uplink speed manually. Saves you some reboot time too and QoS will work anyway.