• April 20, 2019, 02:23:10 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 ... 7

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

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #30 on: February 17, 2014, 12:53:47 PM »

Ok...I'll give that a try. Hoping this will all work out so you can maybe do a mod for the 827 and 657.
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: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #31 on: February 17, 2014, 03:25:00 PM »

Ok set the following and rebooted:
Wired only 1 PC to the router...
Enable Traffic Shaping :     Checked
Automatic Uplink Speed :  Un-Check   
Measured Uplink Speed :   3072 kbps 
Manual Uplink Speed :     3072 kbps  <<   Select Transmission Rate 128 kbps 256 kbps 384 kbps 512 kbps 1024 kbps 2048 kbps 
Connection Type :     Auto-detect xDSL Or Other Frame Relay Network Cable Or Other Broadband Network 
Detected xDSL Or Other Frame Relay Network :   Cable Or Other Broadband Network 

C:\Users\Robear>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=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=81ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=64ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=59ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=63ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=80ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=62ms TTL=247
Reply from 24.116.1.80: bytes=32 time=69ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=61ms TTL=247
Reply from 24.116.1.80: bytes=32 time=60ms TTL=247
Reply from 24.116.1.80: bytes=32 time=59ms TTL=247

Ping statistics for 24.116.1.80:
    Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 81ms, Average = 61ms

Sending 15Mb file to my email account to my self.  ::)



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 #32 on: February 18, 2014, 12:44:04 PM »

thanks mate.
looks better i think. ;D
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #33 on: February 18, 2014, 12:47:14 PM »

So how would we set this up for detailed instruction? I presume that if the mod is in place, and to get good ping times, we need to set a manual uplink speed? Just want to get this iron out so we can put this into a detailed sticky post...
« Last Edit: February 18, 2014, 12:49:31 PM by FurryNutz »
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 #34 on: February 19, 2014, 09:12:51 AM »

For most people automatic classification will be enough i think.
For the uplink speed i would suggest to set it to isp advertised speed.
1 MBit/s = 1024 kbit/s

For example you have 3Mbit Upload. 3 x 1024 = 3072
so you enter 3072 in the box.
for 5 Mbit: 5120

and so on.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #35 on: February 19, 2014, 09:55:15 AM »

Ok sounds good. I think I'll make this a sticky.

Care to do the mod for the 655 next? I can test that out. I've got another guy testing his 857 out now.

If you do build the others, lets keep this thread going here regarding it.
« Last Edit: March 12, 2014, 01:22:37 PM by FurryNutz »
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 #36 on: February 20, 2014, 10:51:12 PM »

Sorry for the late reply. Im quite busy at work atm and for the next week also. i will do this by next week weeks end.

Should be quite easy to do i think. Because they both use the ubicom distro.

Sure you could test it. but there is always a chance to brick the device.
I think there was a emergency recovery, but i have to check that.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #37 on: February 21, 2014, 07:26:54 AM »

No rush on this.

As long as you compile the FW using the same process, bricking should be null.

Emergency Recovery Mode
« Last Edit: December 04, 2014, 01:25:54 PM by FurryNutz »
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!

kargo27

  • Level 5 Member
  • *****
  • Posts: 685
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #38 on: February 27, 2014, 07:09:17 AM »



Mine is working fine as well.  I had to keep Short GI enabled but I had to do that with the other FW, too, or else experience dropped wifi signals requiring a router reboot.

Ping results:

Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 47 milliseconds. TTL = 53
Response from google.com received in 47 milliseconds. TTL = 53
Response from google.com received in 47 milliseconds. TTL = 53
Response from google.com received in 51 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 56 milliseconds. TTL = 53
Response from google.com received in 44 milliseconds. TTL = 53
Response from google.com received in 45 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 48 milliseconds. TTL = 53
Response from google.com received in 47 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 45 milliseconds. TTL = 53
Response from google.com received in 51 milliseconds. TTL = 53
Response from google.com received in 52 milliseconds. TTL = 53
Response from google.com received in 55 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 44 milliseconds. TTL = 53
Response from google.com received in 52 milliseconds. TTL = 53
Response from google.com received in 54 milliseconds. TTL = 53
Response from google.com received in 49 milliseconds. TTL = 53
Response from google.com received in 44 milliseconds. TTL = 53
Response from google.com received in 48 milliseconds. TTL = 53
Response from google.com received in 60 milliseconds. TTL = 53
Response from google.com received in 49 milliseconds. TTL = 53
Response from google.com received in 45 milliseconds. TTL = 53
Response from google.com received in 44 milliseconds. TTL = 53
Response from google.com received in 49 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 48 milliseconds. TTL = 53
Response from google.com received in 50 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 45 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 50 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
Response from google.com received in 52 milliseconds. TTL = 53
Response from google.com received in 52 milliseconds. TTL = 53
Response from google.com received in 52 milliseconds. TTL = 53
Response from google.com received in 44 milliseconds. TTL = 53
Response from google.com received in 100 milliseconds. TTL = 53
Response from google.com received in 122 milliseconds. TTL = 53
Response from google.com received in 83 milliseconds. TTL = 53
Response from google.com received in 46 milliseconds. TTL = 53
User stopped
Pings sent: 47
Pings received: 47
Pings lost: 0 (0% loss)
Shortest ping time (in milliseconds): 44
Longest ping time (in milliseconds): 122
Average ping time (in milliseconds): 51
« Last Edit: February 27, 2014, 07:13:55 AM by kargo27 »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #39 on: February 27, 2014, 07:32:44 AM »

Awesome Kargo, Looks good...

And to confirm, as you were pinging, you sent something via email or to some place while the pinging was going on?


I think this is a stable mod.

Your Short GI issue maybe surrounding WiFi congestion in your area. I've been leaving GI enabled on my routers now, however disabling HT20/40Mhz C0-Existence now if using single mode N only.  ;D
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: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #40 on: March 25, 2014, 05:31:27 PM »

DIR-827 Results:

Auto TS Uplink and QoS enabled-
Initial Measured Uplink Speed :   2886 kbps  (May have been my interference by opening my browser at the time of testing.)

ISP Test: 50Mb Down and 3Mb ISP Service
Time time was during peak hours.
Last Result:
Download Speed: 52763 kbps (6595.4 KB/sec transfer rate)
Upload Speed: 1880 kbps (235 KB/sec transfer rate) Gets up towards 2.5 then kicks down towards the end of the test.
3/25/2014 5:43:54PM

Speedtest.net


Diff. Server:


Manual TS Uplink and QoS Enabled-
Manual Uplink Speed : 4096 kbps

ISP Download Speed: 52603 kbps (6575.4 KB/sec transfer rate)
Upload Speed: 2909 kbps (363.6 KB/sec transfer rate) No kick downs seen.
3/25/2014 5:50:28PM
Last Result:
ISP Download Speed: 52576 kbps (6572 KB/sec transfer rate)
Upload Speed: 3131 kbps (391.4 KB/sec transfer rate)
3/25/2014 5:50:56 PM

Speedtest.net


Diff. Server:



Ping Tests-
With Auto Uplink:
Enable Traffic Shaping :     
Automatic Uplink Speed :     
Measured Uplink Speed :   3359 kbps
Emailing 15Mb file attachment via web mail.
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=70ms TTL=249
Reply from 24.116.1.80: bytes=32 time=59ms 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=59ms 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=65ms TTL=249
Reply from 24.116.1.80: bytes=32 time=66ms TTL=249
Reply from 24.116.1.80: bytes=32 time=83ms TTL=249
Reply from 24.116.1.80: bytes=32 time=82ms TTL=249
Reply from 24.116.1.80: bytes=32 time=100ms TTL=249
Reply from 24.116.1.80: bytes=32 time=103ms TTL=249
Reply from 24.116.1.80: bytes=32 time=126ms TTL=249
Reply from 24.116.1.80: bytes=32 time=116ms TTL=249
Reply from 24.116.1.80: bytes=32 time=114ms TTL=249
Reply from 24.116.1.80: bytes=32 time=124ms 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=119ms TTL=249
Reply from 24.116.1.80: bytes=32 time=127ms TTL=249
Reply from 24.116.1.80: bytes=32 time=138ms TTL=249
Reply from 24.116.1.80: bytes=32 time=125ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=132ms TTL=249
Reply from 24.116.1.80: bytes=32 time=119ms TTL=249
Reply from 24.116.1.80: bytes=32 time=114ms TTL=249
Reply from 24.116.1.80: bytes=32 time=122ms TTL=249
Reply from 24.116.1.80: bytes=32 time=119ms TTL=249
Reply from 24.116.1.80: bytes=32 time=117ms TTL=249
Reply from 24.116.1.80: bytes=32 time=116ms TTL=249
Reply from 24.116.1.80: bytes=32 time=129ms TTL=249
Reply from 24.116.1.80: bytes=32 time=121ms TTL=249
Reply from 24.116.1.80: bytes=32 time=131ms TTL=249
Reply from 24.116.1.80: bytes=32 time=129ms TTL=249
Reply from 24.116.1.80: bytes=32 time=124ms TTL=249
Reply from 24.116.1.80: bytes=32 time=120ms TTL=249
Reply from 24.116.1.80: bytes=32 time=117ms TTL=249
Reply from 24.116.1.80: bytes=32 time=117ms TTL=249
Reply from 24.116.1.80: bytes=32 time=138ms TTL=249
Reply from 24.116.1.80: bytes=32 time=133ms TTL=249
Reply from 24.116.1.80: bytes=32 time=119ms TTL=249
Reply from 24.116.1.80: bytes=32 time=131ms TTL=249
Reply from 24.116.1.80: bytes=32 time=151ms TTL=249
Reply from 24.116.1.80: bytes=32 time=151ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=71ms TTL=249
Reply from 24.116.1.80: bytes=32 time=71ms 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=97ms 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=55ms TTL=249
Reply from 24.116.1.80: bytes=32 time=57ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms 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=67ms TTL=249
Reply from 24.116.1.80: bytes=32 time=72ms 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=53ms 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=58ms TTL=249
Reply from 24.116.1.80: bytes=32 time=69ms TTL=249
Reply from 24.116.1.80: bytes=32 time=55ms TTL=249

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

Manual Uplink: 4096 kbps
C:\>ping cableone.net -n 1000
Emailing 15Mb file attachment via web mail.

Pinging cableone.net [24.116.1.80] with 32 bytes of data:
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=63ms 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=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=121ms TTL=249
Reply from 24.116.1.80: bytes=32 time=116ms TTL=249
Reply from 24.116.1.80: bytes=32 time=119ms TTL=249
Reply from 24.116.1.80: bytes=32 time=120ms TTL=249
Reply from 24.116.1.80: bytes=32 time=113ms TTL=249
Reply from 24.116.1.80: bytes=32 time=121ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=127ms TTL=249
Reply from 24.116.1.80: bytes=32 time=127ms TTL=249
Reply from 24.116.1.80: bytes=32 time=122ms TTL=249
Reply from 24.116.1.80: bytes=32 time=54ms TTL=249
Reply from 24.116.1.80: bytes=32 time=85ms TTL=249
Reply from 24.116.1.80: bytes=32 time=114ms TTL=249
Reply from 24.116.1.80: bytes=32 time=126ms TTL=249
Reply from 24.116.1.80: bytes=32 time=120ms TTL=249
Reply from 24.116.1.80: bytes=32 time=138ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=123ms TTL=249
Reply from 24.116.1.80: bytes=32 time=122ms TTL=249
Reply from 24.116.1.80: bytes=32 time=130ms TTL=249
Reply from 24.116.1.80: bytes=32 time=124ms TTL=249
Reply from 24.116.1.80: bytes=32 time=126ms TTL=249
Reply from 24.116.1.80: bytes=32 time=123ms TTL=249
Reply from 24.116.1.80: bytes=32 time=123ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=125ms TTL=249
Reply from 24.116.1.80: bytes=32 time=127ms TTL=249
Reply from 24.116.1.80: bytes=32 time=149ms TTL=249
Reply from 24.116.1.80: bytes=32 time=133ms TTL=249
Reply from 24.116.1.80: bytes=32 time=125ms TTL=249
Reply from 24.116.1.80: bytes=32 time=131ms TTL=249
Reply from 24.116.1.80: bytes=32 time=121ms TTL=249
Reply from 24.116.1.80: bytes=32 time=129ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=122ms TTL=249
Reply from 24.116.1.80: bytes=32 time=120ms TTL=249
Reply from 24.116.1.80: bytes=32 time=122ms TTL=249
Reply from 24.116.1.80: bytes=32 time=128ms TTL=249
Reply from 24.116.1.80: bytes=32 time=61ms 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=51ms 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=48ms 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=50ms TTL=249
Reply from 24.116.1.80: bytes=32 time=51ms 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=55ms 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=53ms TTL=249

Ping statistics for 24.116.1.80:
    Packets: Sent = 63, Received = 63, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 149ms, Average = 95ms
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 #41 on: March 26, 2014, 10:28:12 AM »

I think the Measured Uplink is too high. Because of that there is no headroom and ping spikes over 100ms. Try with 3072 again pls.
« Last Edit: March 26, 2014, 10:35:40 AM by shm0 »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #42 on: March 26, 2014, 10:30:32 AM »

Will do. Thanks for the corrective Uplink value.  ;)
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 #43 on: March 26, 2014, 10:36:36 AM »

Thanks :D

Maybe there are ways to tweak this so it gets even better. Will check on weekend when i have more time.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47208
  • D-Link Global Forum Moderator
    • New DIR-890L Router with SmartConnect™ Technology
Re: Firmware 1.04 QoS Mod - Finally!
« Reply #44 on: March 26, 2014, 10:40:01 AM »

Sounds good.

We'll need to get this iron out so I can give details on how to use the setting. I presume fore now that manually setting the Uplink value should be at or near what users are paying for on there ISP uplink speeds? Not higher then that?  ???
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 ... 7