• July 04, 2020, 06:11:48 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 2 3 [4] 5 6 7

Author Topic: Firmware 1.04 QoS Mod - Finally!  (Read 66316 times)

shm0

  • Level 2 Member
  • **
  • Posts: 51
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #45 on: March 26, 2014, 11:15:56 AM »

I think the upload measurement maybe only works accurate for Upload Speeds below < 2 Mbits.

So Yes set the Upload Speed to the advertised speed of your isp plan. (Maybe verify with some speed test site that you can get the speeds. Disable QoS before testing and stop all other traffic.)

In my case my isp advertises 5Mbit Upload. I verified that with speedtest.net.

So i enter 5120 as my upload speed. (5 * 1024).

Do some heavy uploading and check your pings. If you are satisfied with the results leave it like that.
If not try enter some lower value. start with 95 % of your upload rate.
For this example it would be 4864. (5120 * 0.95).
Test again.
If the results are still not good enough lower again by 5 %.
e.g. 4608 (5120 * 0.9).
Repeat this steps until you are satisfied with the results.

hope this helps somewhat.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #46 on: March 26, 2014, 11:25:19 AM »

Ya sounds good and thanks for the info.

I was on a 2Mb line until they gave me 3Mb recently so I was right on the fence.

I'm checking some old threads dating back a while to see if any one still has there 8 series routers and see if maybe we can get some more beta testing in with results besides my testing.

Once we at least get all the FWs modded and some initial testing done, and once I hear back from D-Link's official stance on this, will see if we can go public here with it or else where since this I presume this wouldn't be supported by D-Link officially. However I believe these routers in this program are headed to EOL, if not already by now so this may open up a bit more freedom in regards to mod'g the FW. Will see what happens.  ::)

Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #47 on: March 26, 2014, 03:50:47 PM »

Ok testing with:
Manual Uplink Speed :   3072 kbps    
   
   
   Diff Server:
   
   
Speeds hung around 2.90-3.00 and no higher.

   C:\>ping cableone.net -n 1000

Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=76ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=136ms TTL=249
Reply from 24.116.1.80: bytes=32 time=157ms TTL=249
Reply from 24.116.1.80: bytes=32 time=146ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=147ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=140ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=143ms TTL=249
Reply from 24.116.1.80: bytes=32 time=147ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=154ms TTL=249
Reply from 24.116.1.80: bytes=32 time=173ms TTL=249
Reply from 24.116.1.80: bytes=32 time=151ms TTL=249
Reply from 24.116.1.80: bytes=32 time=78ms TTL=249
Reply from 24.116.1.80: bytes=32 time=115ms TTL=249
Reply from 24.116.1.80: bytes=32 time=137ms TTL=249
Reply from 24.116.1.80: bytes=32 time=160ms TTL=249
Reply from 24.116.1.80: bytes=32 time=177ms TTL=249
Reply from 24.116.1.80: bytes=32 time=192ms TTL=249
Reply from 24.116.1.80: bytes=32 time=213ms TTL=249
Reply from 24.116.1.80: bytes=32 time=225ms TTL=249
Reply from 24.116.1.80: bytes=32 time=247ms TTL=249
Reply from 24.116.1.80: bytes=32 time=171ms TTL=249
Reply from 24.116.1.80: bytes=32 time=246ms TTL=249
Reply from 24.116.1.80: bytes=32 time=297ms TTL=249
Reply from 24.116.1.80: bytes=32 time=296ms TTL=249
Reply from 24.116.1.80: bytes=32 time=304ms TTL=249
Reply from 24.116.1.80: bytes=32 time=199ms TTL=249
Reply from 24.116.1.80: bytes=32 time=282ms TTL=249
Reply from 24.116.1.80: bytes=32 time=345ms TTL=249
Reply from 24.116.1.80: bytes=32 time=353ms TTL=249
Reply from 24.116.1.80: bytes=32 time=365ms TTL=249
Reply from 24.116.1.80: bytes=32 time=219ms TTL=249
Reply from 24.116.1.80: bytes=32 time=312ms TTL=249
Reply from 24.116.1.80: bytes=32 time=429ms TTL=249
Reply from 24.116.1.80: bytes=32 time=399ms TTL=249
Reply from 24.116.1.80: bytes=32 time=211ms TTL=249
Reply from 24.116.1.80: bytes=32 time=279ms TTL=249
Reply from 24.116.1.80: bytes=32 time=391ms TTL=249
Reply from 24.116.1.80: bytes=32 time=471ms TTL=249
Reply from 24.116.1.80: bytes=32 time=164ms TTL=249
Reply from 24.116.1.80: bytes=32 time=80ms TTL=249
Reply from 24.116.1.80: bytes=32 time=66ms TTL=249
Reply from 24.116.1.80: bytes=32 time=66ms TTL=249
Reply from 24.116.1.80: bytes=32 time=101ms TTL=249
Reply from 24.116.1.80: bytes=32 time=121ms TTL=249
Reply from 24.116.1.80: bytes=32 time=115ms TTL=249
Reply from 24.116.1.80: bytes=32 time=97ms TTL=249
Reply from 24.116.1.80: bytes=32 time=165ms TTL=249
Reply from 24.116.1.80: bytes=32 time=120ms TTL=249
Reply from 24.116.1.80: bytes=32 time=153ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=166ms TTL=249
Reply from 24.116.1.80: bytes=32 time=147ms TTL=249
Reply from 24.116.1.80: bytes=32 time=193ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=134ms TTL=249
Reply from 24.116.1.80: bytes=32 time=115ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=100ms TTL=249
Reply from 24.116.1.80: bytes=32 time=95ms TTL=249
Reply from 24.116.1.80: bytes=32 time=172ms TTL=249
Reply from 24.116.1.80: bytes=32 time=134ms TTL=249
Reply from 24.116.1.80: bytes=32 time=164ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=165ms TTL=249
Reply from 24.116.1.80: bytes=32 time=114ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 77, Received = 77, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 471ms, Average = 172ms
   
   2nd Run:
C:\>ping cableone.net -n 1000

Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=66ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=129ms TTL=249
Reply from 24.116.1.80: bytes=32 time=136ms TTL=249
Reply from 24.116.1.80: bytes=32 time=142ms TTL=249
Reply from 24.116.1.80: bytes=32 time=159ms TTL=249
Reply from 24.116.1.80: bytes=32 time=149ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=142ms TTL=249
Reply from 24.116.1.80: bytes=32 time=167ms TTL=249
Reply from 24.116.1.80: bytes=32 time=137ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=149ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=138ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=142ms TTL=249
Reply from 24.116.1.80: bytes=32 time=155ms TTL=249
Reply from 24.116.1.80: bytes=32 time=150ms TTL=249
Reply from 24.116.1.80: bytes=32 time=143ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=143ms TTL=249
Reply from 24.116.1.80: bytes=32 time=140ms TTL=249
Reply from 24.116.1.80: bytes=32 time=140ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=147ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=159ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=144ms TTL=249
Reply from 24.116.1.80: bytes=32 time=140ms TTL=249
Reply from 24.116.1.80: bytes=32 time=138ms TTL=249
Reply from 24.116.1.80: bytes=32 time=139ms TTL=249
Reply from 24.116.1.80: bytes=32 time=140ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=156ms TTL=249
Reply from 24.116.1.80: bytes=32 time=148ms TTL=249
Reply from 24.116.1.80: bytes=32 time=141ms TTL=249
Reply from 24.116.1.80: bytes=32 time=143ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=80ms TTL=249
Reply from 24.116.1.80: bytes=32 time=64ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 67, Received = 67, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 167ms, Average = 111ms

Time seem a bit higher than yesterday at same time frame of day.

Thoughts?  ???
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

shm0

  • Level 2 Member
  • **
  • Posts: 51
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #48 on: March 27, 2014, 04:41:43 AM »

That doesnt look good.
Did you use Automatic Classification?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #49 on: March 27, 2014, 07:28:21 AM »

Yes...only thing thats not enabled is Dynamic De fragmentation. Connection Type set to manual CABLE...

I thought maybe time frame of day here could have an impact with the ISP since it was heading into early evening and more people are getting home...not sure.

I did remove the main LAN switch from the router so it was only the one wired PC connected..some wireless devices however they weren't doing anything...
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

shm0

  • Level 2 Member
  • **
  • Posts: 51
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #50 on: March 27, 2014, 07:58:19 AM »

Yes could be possibly that your isp is overloaded at the rush hours. Could you try with some even lower value like 2560 ?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #51 on: March 27, 2014, 08:00:33 AM »

I will do that...today after work.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #52 on: March 27, 2014, 04:57:16 PM »

Looks even worse:
Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=60ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=173ms TTL=249
Reply from 24.116.1.80: bytes=32 time=184ms TTL=249
Reply from 24.116.1.80: bytes=32 time=187ms TTL=249
Reply from 24.116.1.80: bytes=32 time=184ms TTL=249
Reply from 24.116.1.80: bytes=32 time=179ms TTL=249
Reply from 24.116.1.80: bytes=32 time=176ms TTL=249
Reply from 24.116.1.80: bytes=32 time=185ms TTL=249
Reply from 24.116.1.80: bytes=32 time=177ms TTL=249
Reply from 24.116.1.80: bytes=32 time=177ms TTL=249
Reply from 24.116.1.80: bytes=32 time=182ms TTL=249
Reply from 24.116.1.80: bytes=32 time=178ms TTL=249
Reply from 24.116.1.80: bytes=32 time=178ms TTL=249
Reply from 24.116.1.80: bytes=32 time=186ms TTL=249
Reply from 24.116.1.80: bytes=32 time=175ms TTL=249
Reply from 24.116.1.80: bytes=32 time=193ms TTL=249
Reply from 24.116.1.80: bytes=32 time=183ms TTL=249
Reply from 24.116.1.80: bytes=32 time=202ms TTL=249
Reply from 24.116.1.80: bytes=32 time=178ms TTL=249
Reply from 24.116.1.80: bytes=32 time=171ms TTL=249
Reply from 24.116.1.80: bytes=32 time=170ms TTL=249
Reply from 24.116.1.80: bytes=32 time=188ms TTL=249
Reply from 24.116.1.80: bytes=32 time=196ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 202ms, Average = 154ms

I'll try again late night...
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #53 on: March 29, 2014, 11:17:19 AM »

So I forgot my prior 827 results were with a test PC in a QoS rule so I presume this was th reason of the higher ping times.

Manual Measured Uplink Speed :   2560 kbps
15Mb file sent via web email.

QoS enabled with PC in a QoS rule with 128 Priority set:
Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=76ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=60ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=185ms TTL=249
Reply from 24.116.1.80: bytes=32 time=181ms TTL=249
Reply from 24.116.1.80: bytes=32 time=175ms TTL=249
Reply from 24.116.1.80: bytes=32 time=176ms TTL=249
Reply from 24.116.1.80: bytes=32 time=175ms TTL=249
Reply from 24.116.1.80: bytes=32 time=182ms TTL=249
Reply from 24.116.1.80: bytes=32 time=183ms TTL=249
Reply from 24.116.1.80: bytes=32 time=90ms TTL=249
Reply from 24.116.1.80: bytes=32 time=126ms TTL=249
Reply from 24.116.1.80: bytes=32 time=150ms TTL=249
Reply from 24.116.1.80: bytes=32 time=177ms TTL=249
Reply from 24.116.1.80: bytes=32 time=197ms TTL=249
Reply from 24.116.1.80: bytes=32 time=217ms TTL=249
Reply from 24.116.1.80: bytes=32 time=236ms TTL=249
Reply from 24.116.1.80: bytes=32 time=253ms TTL=249
Reply from 24.116.1.80: bytes=32 time=279ms TTL=249
Reply from 24.116.1.80: bytes=32 time=261ms TTL=249
Reply from 24.116.1.80: bytes=32 time=293ms TTL=249
Reply from 24.116.1.80: bytes=32 time=308ms TTL=249
Reply from 24.116.1.80: bytes=32 time=279ms TTL=249
Reply from 24.116.1.80: bytes=32 time=326ms TTL=249
Reply from 24.116.1.80: bytes=32 time=350ms TTL=249
Reply from 24.116.1.80: bytes=32 time=308ms TTL=249
Reply from 24.116.1.80: bytes=32 time=373ms TTL=249
Reply from 24.116.1.80: bytes=32 time=388ms TTL=249
Reply from 24.116.1.80: bytes=32 time=341ms TTL=249
Reply from 24.116.1.80: bytes=32 time=194ms TTL=249
Reply from 24.116.1.80: bytes=32 time=418ms TTL=249
Reply from 24.116.1.80: bytes=32 time=351ms TTL=249
Reply from 24.116.1.80: bytes=32 time=206ms TTL=249
Reply from 24.116.1.80: bytes=32 time=475ms TTL=249
Reply from 24.116.1.80: bytes=32 time=364ms TTL=249
Reply from 24.116.1.80: bytes=32 time=224ms TTL=249
Reply from 24.116.1.80: bytes=32 time=477ms TTL=249
Reply from 24.116.1.80: bytes=32 time=377ms TTL=249
Reply from 24.116.1.80: bytes=32 time=248ms TTL=249
Reply from 24.116.1.80: bytes=32 time=494ms TTL=249
Reply from 24.116.1.80: bytes=32 time=397ms TTL=249
Reply from 24.116.1.80: bytes=32 time=247ms TTL=249
Reply from 24.116.1.80: bytes=32 time=520ms TTL=249
Reply from 24.116.1.80: bytes=32 time=399ms TTL=249
Reply from 24.116.1.80: bytes=32 time=255ms TTL=249
Reply from 24.116.1.80: bytes=32 time=558ms TTL=249
Reply from 24.116.1.80: bytes=32 time=411ms TTL=249
Reply from 24.116.1.80: bytes=32 time=273ms TTL=249
Reply from 24.116.1.80: bytes=32 time=562ms TTL=249
Reply from 24.116.1.80: bytes=32 time=427ms TTL=249
Reply from 24.116.1.80: bytes=32 time=290ms TTL=249
Reply from 24.116.1.80: bytes=32 time=582ms TTL=249
Reply from 24.116.1.80: bytes=32 time=445ms TTL=249
Reply from 24.116.1.80: bytes=32 time=300ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 72, Received = 72, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 582ms, Average = 233ms

PC not in a QoS rule and QoS still enabled:
Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=58ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=58ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=58ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=64ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=59ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=60ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 80, Received = 80, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 64ms, Average = 52ms

PC not in a QoS rule, QoS enabled and 3072kbps set:

Pinging cableone.net [24.116.1.80] with 32 bytes of data:
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=59ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=60ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=73ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=61ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=63ms TTL=249
Reply from 24.116.1.80: bytes=32 time=62ms TTL=249
Reply from 24.116.1.80: bytes=32 time=68ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=68ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=53ms TTL=249
Reply from 24.116.1.80: bytes=32 time=56ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=52ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249
Reply from 24.116.1.80: bytes=32 time=48ms TTL=249
Reply from 24.116.1.80: bytes=32 time=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=49ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 71, Received = 71, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 73ms, Average = 53ms

I believe my earlier tests on the 857 were with a PC not set in a QoS rule, just QoS enabled with the TS settings. I presume QoS rules will effect ping times based on settings and priority values.

Thoughts?
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

shm0

  • Level 2 Member
  • **
  • Posts: 51
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #54 on: March 30, 2014, 10:14:52 AM »

As i explained to you before if you put a qos rule for one device. Lets say 128. Every Service thats running over the internet gets the priority 128. Thats bad. You do want your games get lower priority value and your file sharing, heavy uploading a higher value ? Dont you? ;) (Lower Value = Higher Priority)

So my recommendation is just use the automatic classification and dont mess with priority rules.
If you want to use priority rules. use rules on service basis not device basis. You can use device rules for example for voip phones.

So the last two test are without priority rule for pc and automatic classification on? They look quite fine.
« Last Edit: March 30, 2014, 10:16:26 AM by shm0 »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #55 on: March 30, 2014, 12:16:50 PM »

Yes Auto Class. is enabled.

As for rules, all my non critical devices are set in a rule to give normal or close to normal QoS priority with 128..My 2 game consoles are set for 1 or 50, mostly 50 to give the best priority for gaming...

So I think were good on the 827 Mod FW?
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

shm0

  • Level 2 Member
  • **
  • Posts: 51
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #56 on: March 30, 2014, 03:09:54 PM »

Yes i think its fine. ;D
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #57 on: March 31, 2014, 07:33:46 AM »

Ok, let me know about the 655 FW. I'll get the 657 downloaded. I'm not sure if they are going to do another release of FW on the 657 or not. Didn't get much love in it's life and I think it may have already gone into EOL.  :-\
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

Syaoran

  • Level 3 Member
  • ***
  • Posts: 192
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #58 on: July 27, 2014, 02:18:51 PM »

Where is the download link to try this out? 
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 48926
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #59 on: July 28, 2014, 10:46:59 AM »

PM me your email address and I'll send you it. I did have it up on my FTP, however since I change routers every so often, keeping the FTP going is a pain so it's just easier to email it.

Where is the download link to try this out? 
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!
Pages: 1 2 3 [4] 5 6 7