Did you do a factory settings?
After that restore the settings for best result.
I installed 22SF and I have a few issues.In general, not so obligatory. I recommed this procedure mainly for R7500 in my readme (too different drivers with stock firmware).
R7800: should be compatible with stock, so not absolutely necessary for R7800.
Voxel.
I installed 22SF and I have a few issues.
When I do a reboot my 2.4 is not coming up. I have to start it from the gui.
I also did a speed test at dslreports and I am getting an F for the buffer bloat. Quality reads A+. Ping time is really good though!
Well, Buffer bloat: Specific stuff. With the same dslreports I am getting:I installed 22SF and I have a few issues.
When I do a reboot my 2.4 is not coming up. I have to start it from the gui.
I also did a speed test at dslreports and I am getting an F for the buffer bloat. Quality reads A+. Ping time is really good though!
sysctl -w net.ipv4.tcp_ecn=1
That didn't seem to work. I still got an F on the bloat test.Well, Buffer bloat: Specific stuff. With the same dslreports I am getting:
Overall: A+
BufferBloat: A
Quality: A+
The same router, the same firmware, different Internet line.
I had one feedback that man, he had BufferBloat “C” with stock FW and has got BufferBloat “B” with my build.
I’d suggest you to do some fine tuning. Check for example this hint:
https://www.bufferbloat.net/projects/cerowrt/wiki/Enable_ECN/#enabling-ecn-on-linux
i.e.
1. Enter to your router console (by SSH or if you did not set it yet by telnet, enabling telnet from http://routerlogin.net/debug.htm).
2. Run the command from console:
Code:sysctl -w net.ipv4.tcp_ecn=1
3. Test by dslreports again.
If it will be better, you can correct the file /etc/sysctl.conf changing this value.
P.S. Sometimes it is really better to do reset ;-) Maybe.
Voxel.
That didn't seem to work. I still got an F on the bloat test.
From an A to a C.What did you get with sock firmware?
Voxel.
From an A to a C.
. . .
start() {
# Socket buffers
# echo 1048576 > /proc/sys/net/core/rmem_max
# echo 1048576 > /proc/sys/net/core/wmem_max
. . .
How do I edit the file in telnet? I don't know the command to edit in LinuxIf you can, try to comment by "#" symbols the lines with "echo" commands in init script /etc/init.d/optware:
Code:. . . start() { # Socket buffers # echo 1048576 > /proc/sys/net/core/rmem_max # echo 1048576 > /proc/sys/net/core/wmem_max . . .
and reboot router after this. Then again bloat test after reboot.
Voxel.
Well... "vi" is the best editir ;-) I guess you don't know it...How do I edit the file in telnet? I don't know the command to edit in Linux
cp /etc/init.d/optware /mnt/sda1/
cp -f /mnt/sda1/optware /etc/init.d/optware
I don't have Linux for my computer.Well... "vi" is the best editir ;-) I guess you don't know it...
So the way is: copy this file to USB stick, then edit the file from stick (attached to computer). Then copy it from the stick to router. Something like:
Code:cp /etc/init.d/optware /mnt/sda1/
then edit is attaching to computer, then attach it back to router and:
Code:cp -f /mnt/sda1/optware /etc/init.d/optware
Voxel
You can edit using Notepad +++ from under the Windows.I don't have Linux for my computer.
I guess I'll have to d/l a distro and boot from the cd.
I'll try that when I get back.You can edit using Notepad +++ from under the Windows.
Hi Voxel!If you can, try to comment by "#" symbols the lines with "echo" commands in init script /etc/init.d/optware:
Code:. . . start() { # Socket buffers # echo 1048576 > /proc/sys/net/core/rmem_max # echo 1048576 > /proc/sys/net/core/wmem_max . . .
and reboot router after this. Then again bloat test after reboot.
Voxel.
sysctl -w net.ipv4.tcp_ecn=1
That sounds good. On the R7800, it runs an Ooakla speed test by default. So I'll try to set the bandwidth manually before I go through all the editing etc. I just haven't used Linux since 2000. So I forget all that stuff. I also have a very active network ie. Xbox, PS3, computers and if I mess it up I catch a lot of shxx!Bufferbloat and its effects can happen anywhere along the route between you and your remote site (in this case, the dslreports test site). The router isn't the only location. Cablemodems for instance will have their own buffers there.
The best way to get good result along most of the route (provided the ISP isn't overloaded) is to cap your bandwidth a few percents below what your ISP is giving you, ensuring that you will never fill up the buffers in your modem/router/PC.
I absolutely agree. It depends not only from your router settings, but also from concrete remote site. So if you tune your router for maximum performance with dslreports you can face problems with other sites.Bufferbloat and its effects can happen anywhere along the route between you and your remote site (in this case, the dslreports test site). The router isn't the only location. Cablemodems for instance will have their own buffers there.
The best way to get good result along most of the route (provided the ISP isn't overloaded) is to cap your bandwidth a few percents below what your ISP is giving you, ensuring that you will never fill up the buffers in your modem/router/PC.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!