So the critical buffering happens in front of the slowest link, the bottleneck (changes from fast to slow generally are critical). SQM's trick is on download to restrict the speed even further than the real bottleneck link, which effectively creates a _new_ bottleneck link under SQM's control. Since SQM is smarter in how is administrates the resulting queue latency under load stays much saner than with the usual FIFO buffers on DSLAMs/CTMSs. But to create the artificial bottleneck you need to sacrifice some bandwidth (and if artificial and real bottleneck are too similar in bandwidth, fast incoming traffic will fill both bottlenecks' queues so bufferbloat is not well controlled. So with SQM there is a tradeoff between latency under load and bandwidth, whether your specific setting are sane or not really depends. Maybe you could post the output of
cat /etc/config/sqm
tc -d qdisc
tc -s qdisc
to this thread so we can try to figure out whether you are as good as it gets already or not... Plrease also try to look up your ADSL modem's synchronization bandwidth for upload and download (these typically determine the bottleneck bandwidths).

Best Regards
        M.

moeller0 wrote:

So the critical buffering happens in front of the slowest link, the bottleneck (changes from fast to slow generally are critical). SQM's trick is on download to restrict the speed even further than the real bottleneck link, which effectively creates a _new_ bottleneck link under SQM's control. Since SQM is smarter in how is administrates the resulting queue latency under load stays much saner than with the usual FIFO buffers on DSLAMs/CTMSs. But to create the artificial bottleneck you need to sacrifice some bandwidth (and if artificial and real bottleneck are too similar in bandwidth, fast incoming traffic will fill both bottlenecks' queues so bufferbloat is not well controlled. So with SQM there is a tradeoff between latency under load and bandwidth, whether your specific setting are sane or not really depends. Maybe you could post the output of
cat /etc/config/sqm
tc -d qdisc
tc -s qdisc
to this thread so we can try to figure out whether you are as good as it gets already or not... Plrease also try to look up your ADSL modem's synchronization bandwidth for upload and download (these typically determine the bottleneck bandwidths).

Best Regards
        M.

How do i find the output of those files? I am a newbe to this

@bauj - You can use either wired or wireless during SQM setup. (You will probably be doing the SQM setup when no one else is using the wireless (or the network at all...), so the measurements should be good. Even your wireless set up will be faster than the 5M/800K DSL link.) Follow the steps in https://wiki.openwrt.org/doc/howto/sqm - start with speed settings at 85%, then run a bufferbloat test, increase the speed setting a bit, test again, etc. until latency gets too high, then back off. Do this for download first, then do the upload speeds.

@moeller0 - I am starting to recommend Cmder as a replacement for putty on Windows. http://cmder.net/ - see http://richb-hanover.com/cmder-for-wind … -to-putty/

bauj wrote:

moeller0 wrote:

So the critical buffering happens in front of the slowest link, the bottleneck (changes from fast to slow generally are critical). SQM's trick is on download to restrict the speed even further than the real bottleneck link, which effectively creates a _new_ bottleneck link under SQM's control. Since SQM is smarter in how is administrates the resulting queue latency under load stays much saner than with the usual FIFO buffers on DSLAMs/CTMSs. But to create the artificial bottleneck you need to sacrifice some bandwidth (and if artificial and real bottleneck are too similar in bandwidth, fast incoming traffic will fill both bottlenecks' queues so bufferbloat is not well controlled. So with SQM there is a tradeoff between latency under load and bandwidth, whether your specific setting are sane or not really depends. Maybe you could post the output of
cat /etc/config/sqm
tc -d qdisc
tc -s qdisc
to this thread so we can try to figure out whether you are as good as it gets already or not... Plrease also try to look up your ADSL modem's synchronization bandwidth for upload and download (these typically determine the bottleneck bandwidths).

Best Regards
        M.

How do i find the output of those files? I am a newbe to this

Hi bauj,

you need to use a terminal to connect to your router (see https://wiki.openwrt.org/doc/howto/firstlogin for some description). But in a nutshell, install, e.g. putty (http://www.chiark.greenend.org.uk/~sgta … nload.html) on your computer, open a terminal window there and type:

putty root@192.168.1.1

(basically the same procedure you did for your first boot).

That gives you a "sell" (command line interpreter" on the router, and on that shell you issue the following commands:

cat /etc/config/sqm

tc -d qdisc

tc -s qdisc

and ten copy the output from the shell window into your posting.

Best Regards
        M.

tried to use putty and it returned  connection refused. I suspect I need to input password but where?

bauj wrote:

tried to use putty and it returned  connection refused. I suspect I need to input password but where?

Hi bauj,

what was the exact command line you used?

Did you follow the instructions  from https://wiki.openwrt.org/doc/howto/firstlogin ?
Depending on your openwrt version you might first need to log in via telnet and set the root password (simply type "passwd" on the telnet shell) before you can log-in via ssh, it might also be possible to set the root password via the GUI.

Can you reach your router via a web browser using https://192.168.1.1 ?

Best Regards
        M.

Back to this finally.
When I do tests for actual speed should this be via a wired connection or wireless?

moeller0 wrote:

bauj wrote:

tried to use putty and it returned  connection refused. I suspect I need to input password but where?

Hi bauj,

what was the exact command line you used?

Did you follow the instructions  from https://wiki.openwrt.org/doc/howto/firstlogin ?
Depending on your openwrt version you might first need to log in via telnet and set the root password (simply type "passwd" on the telnet shell) before you can log-in via ssh, it might also be possible to set the root password via the GUI.

Can you reach your router via a web browser using https://192.168.1.1 ?

Best Regards
        M.

I can reach the router with a web browser. Back when I first installed open wrt i don't recall my first login but I have been using the luci gui to work with open wrt

bauj wrote:

moeller0 wrote:

Hi bauj,

what was the exact command line you used?

Did you follow the instructions  from https://wiki.openwrt.org/doc/howto/firstlogin ?
Depending on your openwrt version you might first need to log in via telnet and set the root password (simply type "passwd" on the telnet shell) before you can log-in via ssh, it might also be possible to set the root password via the GUI.

Can you reach your router via a web browser using https://192.168.1.1 ?

Best Regards
        M.

I can reach the router with a web browser. Back when I first installed open wrt i don't recall my first login but I have been using the luci gui to work with open wrt

Okay, which URL do you use via the browser?

Best Regards
        M.

moeller0 wrote:

bauj wrote:

I can reach the router with a web browser. Back when I first installed open wrt i don't recall my first login but I have been using the luci gui to work with open wrt

Okay, which URL do you use via the browser?

Best Regards
        M.

192.168.1.1

bauj wrote:

moeller0 wrote:

Okay, which URL do you use via the browser?

Best Regards
        M.

192.168.1.1

Ah great, what operating system are you using, windows?

Best Regards
        M.

moeller0 wrote:

bauj wrote:

192.168.1.1

Ah great, what operating system are you using, windows?

Best Regards
        M.

windows 10

Hi bauj,

I was away over the weekend, hence no response.

When you log in via the GUI do you need to enter a password at all?

Best Regards
        M.

moeller0 wrote:

Hi bauj,

I was away over the weekend, hence no response.

When you log in via the GUI do you need to enter a password at all?

Best Regards
        M.

Yes

bauj wrote:

moeller0 wrote:

Hi bauj,

I was away over the weekend, hence no response.

When you log in via the GUI do you need to enter a password at all?

Best Regards
        M.

Yes

Interesting, when I install putty on a windows 10 host, open a command line (cmd.exe) the following happens:

C:\Users\user>putty root@191.168.1.1

it opens a putty window with the following content:
Using username "root".
root@192.168.1.1's password:

and then I can enter the password. Could you please reboot your router and wait for 10 minutes before trying it again? And could you also post your exact command line and the output of said commands, please?

Best Regards
        M.

moeller0 wrote:

bauj wrote:

Yes

Interesting, when I install putty on a windows 10 host, open a command line (cmd.exe) the following happens:

C:\Users\user>putty root@191.168.1.1

it opens a putty window with the following content:
Using username "root".
root@192.168.1.1's password:

and then I can enter the password. Could you please reboot your router and wait for 10 minutes before trying it again? And could you also post your exact command line and the output of said commands, please?

Best Regards
        M.

When I open putty and enter putty root@192.168.1.1 it opens a command prompt  asking for for root@192.168.1.1 's password but the cursor is green and doesn't register and characters I enter

bauj wrote:

moeller0 wrote:

Interesting, when I install putty on a windows 10 host, open a command line (cmd.exe) the following happens:

C:\Users\user>putty root@191.168.1.1

it opens a putty window with the following content:
Using username "root".
root@192.168.1.1's password:

and then I can enter the password. Could you please reboot your router and wait for 10 minutes before trying it again? And could you also post your exact command line and the output of said commands, please?

Best Regards
        M.

When I open putty and enter putty root@192.168.1.1 it opens a command prompt  asking for for root@192.168.1.1 's password but the cursor is green and doesn't register and characters I enter

That's normal: passwords are not shown to avoid eavesdropping; just type it and press INTRO.