If it's not done on the router then it will have to be done at a network level but by the time the packets in the network it's already used the upstream bandwidth, You could drop it in the network and hope the sending application backs off (Which is basically what happens with downstream QOS on a lot of routers) but if it doesn't then all you're actually doing is causing more usage due to the retranmissions.

I think he's suggesting the QOS rules are applied to the router by Plusnet using TR069.

I guessed as much but does it work normally? from what I can tell it does as many routers chose this way of doing it ?

batboy is correct with TR069 or could be by firmware update.

Edited by deleted (Sun 03-Nov-13 21:11:54)

In reply to a post by BatBoy:

I think he's suggesting the QOS rules are applied to the router by Plusnet using TR069.

It would depend if the TR-69 Data model contains the parameters for QOS or not, either as part of the standard IGD tree or as a vendor specific extension.

I should have said remote admin really.

In reply to a post by BatBoy:

I should have said remote admin really.

TR-69 would be the best way to change settings on lots of devices providing the QOS is controllable via it, The problem then becomes finding the right balance of QOS settings and it also depends on how good the QOS is on the router.

Then there's the problem of knowing the customers upstream sync speed so that the system can apply the correct settings.

It's probably doable just a bit of a minefield.

The PlusNet router does not need the customer to enter their upload speed to do QOS as the router already QOS's ICMP traffic out of the box and does it well with good latency.

Edited by deleted (Sun 03-Nov-13 21:13:18)

http://community.plus.net/forum/?topic=116556.msg100...
In that thread above (The one I posted earlier) the method was to blacklist traffic that could harm games like HTTP file uploads or NNTP traffic. This lead to a few problems like unable to detect some traffic such as bit torrent upstream from harming game/VOIP traffic. So using telnet I had a go to QOS gaming traffic itself and came up with this rule list (You can copy and paste these in to the router to save time typing them in manually)

expr add name=P2P type serv proto udp dstport 27000
expr add name=P2P type serv proto udp dstport 27001
expr add name=P2P type serv proto udp dstport 27002
expr add name=P2P type serv proto udp dstport 27003
expr add name=P2P type serv proto udp dstport 27004
expr add name=P2P type serv proto udp dstport 27005
expr add name=P2P type serv proto udp dstport 27006
expr add name=P2P type serv proto udp dstport 27007
expr add name=P2P type serv proto udp dstport 27008
expr add name=P2P type serv proto udp dstport 27009
expr add name=P2P type serv proto udp dstport 27010
expr add name=P2P type serv proto udp dstport 27011
expr add name=P2P type serv proto udp dstport 27012
expr add name=P2P type serv proto udp dstport 27013
expr add name=P2P type serv proto udp dstport 27014
expr add name=P2P type serv proto udp dstport 27015
expr add name=P2P type serv proto udp dstport 88
expr add name=P2P type serv proto udp dstport 3074
expr add name=P2P type serv proto udp dstport 3075
expr add name=P2P type serv proto udp dstport 1863
expr add name=P2P type serv proto udp dstport 3478
expr add name=P2P type serv proto udp dstport 3479
expr add name=P2P type serv proto udp dstport 3480
expr add name=P2P type serv proto udp dstport 3658
expr add name=P2P type serv proto udp dstport 10070
label rule add chain=qos_user_labels index=1 name=P2P serv=P2P label=Management
saveall

These rules detect most Peer to peer games (75%) and some dedicated server (50%) games on PC while also detecting most games on PlayStation and Xbox Consoles (around 90% for both).So these QOS rules should work well with consoles.
Using these rules no matter what traffic is being uploaded at the same time as playing the game it should not cause lag problems (fixing the problem they had in that thread with bit torrent upstream) These QOS rules could also be used with the QOS rules within that thread to reduce lag in any of the games that are not supported with my rules.

Edit: maybe PlusNet could use QOS rules like these?
Edit 2: removed port 53 as not gaming rule

Edited by deleted (Sun 24-Nov-13 12:56:29)

I wouldn't include UDP port 53 in your rule set - that's the port for DNS. You want name lookups, which use very little bandwidth, to be handled quickly, not prioritized downwards with P2P traffic.