D-Link Forums

The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Beta Code! => Topic started by: EddieZ on March 15, 2009, 05:06:24 AM

Title: 1.22B05: Changes to the QoS module?
Post by: EddieZ on March 15, 2009, 05:06:24 AM: Since the latest beta I've noticed that the rules set in QoS are not followed anymore. Looking into the Internet log I noticed that my IP (which has been set to priority 32 on all ports) is only been given priority 128 ...

Question is: Is my case isolated? So please let me know how your QoS configured rules reflect in the Internet log.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: lotacus on March 15, 2009, 09:30:53 AM: works fine for me. I dont use QoS but tested it out using port 80. I had some problems getting it set up and found out that I had to do the reverse to what dlink support said on their website to configure it.

(http://hpzdfa.bay.livefilestore.com/y1pmH-D9ZcnLyasLXjB6FcgNeveYzlW_ool-RovmeK_ZTzIls0BxfOcMv05Kf8l-CEdNqJ-vXqtT1LEhn4qMHLygQ/q0srules.PNG)

(http://hpzdfa.bay.livefilestore.com/y1pxSEQRnd7cAWSsVjaBTg3PHmqoDMPCuLSwtheUJhwdbn1aRwsVqo_chF7B71n7BUXsdV9SZuFwUU61W8ejgyRTA/QoS.PNG)
Title: Re: 1.22B05: Changes to the QoS module?
Post by: Lycan on March 16, 2009, 08:26:57 AM: What firmware is that guys? I'll test it myself.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: lotacus on March 16, 2009, 12:22:29 PM: lycan lycan lycan.

Quote
Topic: 1.22B05: Changes to the QoS module?
Title: Re: 1.22B05: Changes to the QoS module?
Post by: Lycan on March 16, 2009, 12:25:09 PM: LOL. Yea I realized it after I posted.
Don't fret, there's already a 1.30 in the works.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: EddieZ on March 16, 2009, 12:37:11 PM: Quote from: Lycan on March 16, 2009, 12:25:09 PM
LOL. Yea I realized it after I posted.
Don't fret, there's already a 1.30 in the works.

gimme gimme to test ;D
Title: Re: 1.22B05: Changes to the QoS module?
Post by: EddieZ on March 16, 2009, 12:42:58 PM: It seems that entering a specific port in the remote port range does work, but a remote port range does not. Is there some decision making involved when it spots overlapping ranges from IP's (if so, which)?
Title: Re: 1.22B05: Changes to the QoS module?
Post by: Lycan on March 16, 2009, 12:54:33 PM: No, thats odd, you should be able to QoS all 65,535 ports if you want.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: EddieZ on March 16, 2009, 02:19:23 PM: Quote from: Lycan on March 16, 2009, 12:54:33 PM
No, thats odd, you should be able to QoS all 65,535 ports if you want.

Ranges working/not working:
remote port 80 - 80 > priority shows in logs
remote port 0 - 65535 > no priority in logs
Title: Re: 1.22B05: Changes to the QoS module?
Post by: Lycan on March 16, 2009, 02:21:59 PM: Give me a screen shot of both the statetable and the configs?
Title: Re: 1.22B05: Changes to the QoS module?
Post by: lotacus on March 16, 2009, 06:57:30 PM: (http://hpzdfa.bay.livefilestore.com/y1pMfGXofMEDTiFS1NCUU7Xo7Pg4r_O4LvsDNmVQmxv_OvjhUgjD_zczw_NxzopRTii1Mgl6aeldB1rr4GSgmC5tw/QoS.PNG)

(http://hpzdfa.bay.livefilestore.com/y1pHC2FVPsp3BKcEYkOheyAPirr5tTSBBjF4jaqTAPxShyj3AvJZOgX4RNyitmSdARJLSNje1eYEXAazSspEu3KiA/nat.PNG)

As you can see, I started at port 1 since there is no such thing as a port 0, however I don't think it really matters.

Setting the rule for all ports works with me. I loaded up utorrent, and confirmed that all connections were using a priority of 32 just as I set.

Not sure what H/W revision your running, but mine is A2 and everything is working as expected. Perhaps you should re-confirm your IP address.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: EddieZ on March 17, 2009, 12:31:31 PM: I did a full reset, manually inputting all config data and now it does work OK. Seems my install of beta05 still wasn't perfect.... Thanks for checking.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: lotacus on March 17, 2009, 05:05:21 PM: no problem.
Title: Re: 1.22B05: Changes to the QoS module?
Post by: bluenote on March 18, 2009, 09:41:32 AM: Hey Eddie

If it makes you feel any better I've found that I had to confirm my QOS settings by checking the status of connections because the configuration seems to have some funny rules where you can exclude your own setting accidently. (ie: the router interprets certain QOS fields as "OR" and you would expect it to be "AND") I'm not sure I'm recalling this correctly, but the gist is, it didn't behave as I expected and I needed to confirm my settings by status.