Print

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

[dan1son]

I've been running wireless routers with QOS for years (mostly DD-WRT) and recently bought myself the DIR-825 for its dual band and gigabit abilities.  I'm not quite ready to put DD-WRT on it due to instability and speed problems reported, but I NEED the QOS features to work for my uses in D-Links setup. 

I host a lot of stuff on my home server; web, e-mail, subsonic (music streaming), torrents, ssh tunnels, etc.  and have a very specific priority level for each so I can do what I need personally while others or torrents get the rest of the upload bandwidth.  The problem is I can't seem to nail this thing down to work at all.  Automatic classification does, fairly obviously, not fit the bill for me.  I run mostly non-standard ports and services a home router probably doesn't know about.  I understand I'm not the normal customer   I also realize QOS on this router only effects upload, and I'm cool with that.

My main concern is with "conflicting rules."  Does the router tell me they're conflicting if they are?  If not... how would I prioritize outgoing web traffic different from incoming web traffic? 

For example, do these conflict?  If so how do I remedy the situation...
Local IP Range  10.1.1.40 - 10.1.1.40  Local Port Range  80 - 80
Remote IP Range ALL  Remote Port Range  ALL

Local IP Range  ALL  Local Port Range  ALL
Remote IP Range  ALL  Remote Port Range  80 - 80


I'm currently using 9 of the 10 rules.  I left bit torrent off the list so it gets bottom priority.  However, if those two above conflict I'm afraid they all do and are being removed. 

I appreciate the help.  This setup was very possible in DD-WRT, I'd like it to be here as well. 

[dan1son]

Well I messed around with it some more last night and ended up removing all of the outgoing rules and replacing them with a rule for my DHCP addresses that gives them a proper priority.  So the Web rule with remote port 80-80 in the last post is gone, and any others like it.  Definitely no conflicts now

That seems to "work".  But I'm very dissapointed with the QOS engine on these routers.  The response time for QOS to give priority is slow (takes several seconds for a transfer to get up to speed if a lower priority stream is already consuming the pipe).

The lack of "conflicting rules," as they call it, especially since they don't seem to tell you they're conflicting, makes forming a proper priority rule list difficult.  It's normal in the computer field to have "conflicting rules."  Look at permissions on any computer.  If you're a member o***roup with higher permissions to a file than your own direct permissions you get the higher of the two (actually the join of the two sets).  This should be the case here as well.  If I give every computer on my DHCP list priority 8 but give one of those priority 7 that should work fine. 

The lack of a "default" priority.  The inability to set something lower than the default priority is a huge disadvantage.  It should be possible to set a few things higher, and a few things lower, without having to plop everything else in the rule list.  This with the lack of "conflicting rules" makes it impossible to build the rule structure I want. 

Again, I know I'm not the average user, but manual QOS setup isn't for the average user.  It's not even documented in the manual, and barely documented in the help.  A power user function needs full functionality.  I've managed to get about 75% of the functionality I want, which will do for now. 

[dan1son]

To continue the discussion with myself...

I gave up on dlinks QOS.  It was horrible at handling multiple connections from the same machine matching a QOS rule.  Basically if I ssh'd into the machine more than once from another machine, the connection would slow down regardless of the current bandwidth use. 

DD-WRT is now installed and running.