Trying to limit bandwidth on other wireless devices - Netgear interface

Toggle sidebar Toggle sidebar
K

Kaiokhen

Honorable
Mar 28, 2013
17
0
10,510
Hello. I am new to the forum and i would like to learn how to properly set the bandwidth limit of each wireless devices.

Currently i have a streaming device which is very similar to AppleTV. Its wireless and is constantly streaming which hogs the bandwidth quite greedily. I did my research regarding QoS and my router has the feature the router that i have is NetGear Router R6300v2(http://www.amazon.com/Netgear-Router-AC1750-Gigabit-R6300v2/dp/B00EM5UFP4/ref=sr_1_1?ie=UTF8&qid=1386203986&sr=8-1&keywords=R6300v2)

As i encounter with the QoS interface, i have set the priority for each device. However, there is no input of bandwidth limit. It just gives me a priority option.
Question. Is Uplink bandwidth Maximum equivalent to upload speed? Because i set it to roughly 400Kbs and it affected the upload speed across the network. So i am guess this is the upload speed and not the cap for download speed correct?

Here are the images below of the NetGear interface. As you can see, other devices are set low priority. However, it doesnt seem to work and they continuously hog the bandwidth. I would really appreciate for your help and maybe a lesson or tips that i am missing out

SATIshu.png


sof1NaH.png


Thank you for your time and your help
 
Solution
B
The concept that you can somehow control incoming traffic by dropping outbound packets is flawed. Sure if you drop 100% you can stop the requests but anything less than 100% is going to have very random results.

A somewhat fake example to keep things simple but it does represent how this works.

I send a 20 byte message to netflicks "play video videoname".
Netflicks then starting the data for some high def video at 5m/sec
Once every minute it asks are you still receiving/wanting the data
I then send a 3 byte "yes" message.

So you can get 5m/sec by sending 20 bytes of data and keep the feed running by sending 3bytes every minute. So how could you restrict this so netflicks would only send 2m/sec of data.


Like this fake example...
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,326
2,756
125,640
As you found QoS is mostly a worthless feature.

Yes you can really only control the UPLOAD traffic. In most cases your upload stream is not the one that is overloaded it is your download. The problem with the download is that when the ISP detects the connection is full it randomly throws away traffic. Not much your router can do the traffic is gone way before it even gets close to your house.

Now some routers have the ability to put hard limits on bandwidth both up and down. Which is really nice if you actually have a problem with your upload bandwidth and need to limit some traffic. The download limitation on its face seems stupid. My link is overloaded so the ISP is dropping random data...so I get mad and drop even more of the youtube traffic that ISP does not drop. That does not magically undrop the traffic the ISP dropped. The only reason this appears to work is some application like youtube are smart enough to detect the traffic loss and slow down. Because they are now transmitting less data to try to avoid the dropping the total utilization should less and the ISP can stop dropping traffic.

The only flaw with this concept is the application must be able to detect the traffic loss and take action to reduce it bandwidth. If the application is designed to send 2m/sec no matter what you do then QoS inbound limits will not solve the issue.
 
Upvote 0 Downvote
allennnn

allennnn

Honorable
Nov 25, 2012
306
0
10,860
From reading about QoS on wiki the router queues and drops the outgoing requests for packets so if no request is made then the site/isp won't be answering and sending packets back down the line, now if it's set up poorly or the line is very low maybe to many requests get answered still and it has little effect.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,326
2,756
125,640
The concept that you can somehow control incoming traffic by dropping outbound packets is flawed. Sure if you drop 100% you can stop the requests but anything less than 100% is going to have very random results.

A somewhat fake example to keep things simple but it does represent how this works.

I send a 20 byte message to netflicks "play video videoname".
Netflicks then starting the data for some high def video at 5m/sec
Once every minute it asks are you still receiving/wanting the data
I then send a 3 byte "yes" message.

So you can get 5m/sec by sending 20 bytes of data and keep the feed running by sending 3bytes every minute. So how could you restrict this so netflicks would only send 2m/sec of data.


Like this fake example in real traffic the requests for data and the acknowledgement packets (if they are even used) are very tiny compared to data being received.

 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom