Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Thu Jun 30, 2022 15:31 Post subject:
To reply to the OP, I was told that the defaults are correct for anything that has more than 16MB of RAM, apparently. The default nvram variable values are "wrong".
Quote:
ah you mean lower end. ahm specify lower end. this is bullshit. the old 4096 restriction was for 16 mb ram devices. no current device (except for very old wrt54g etc.) has such low ram
@alozaros, Microsoft's logic is beyond reproach , to be fair you have to have some type of CC and they assume most ppl just plug the WAN cable to the back of the machine and back then (Windows Vista/7) they weren't far from the truth and still in many parts of the world they are close to it.
And I'm still trying to find out if DD-WRT's CC is up for all outgoing traffic or just p2p without doing much work, yep Im also lazy, deal with it.
As already mentioned several times.
the TCP congestion control is endpoint based.
When the router is the endpoint, the TCP congestion control of the router is used but not when simply forwarding data to a client.
Packet forwarding is layer 3
and congestion control is layer 7
If the client is the endpoint, then the client's congestion control is also used.
You must run a TCP application on the router itself to use the router's congestion control.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sun Jul 03, 2022 8:30 Post subject:
So this section has been fully dealt with.
The default value string (4096) was hardcoded (so are all default values on default strings help text), it was never actually pulling default values from any particular default holding file I mean NEVER did since this was added umpteen years ago, so it showed this value no matter device, this is no longer the case, now defaults are being pulled from default values holding files and populated here.
Future contributions where accurate default values are needed the implementation now exists to populate the correct default values per device, should there be one obviously, some defaults in other areas are standard on all devices.
If you notice any default values on any page that are incorrect per device, please let me know on the UI bug and discussion thread or via PM.
Defaults will be shown correctly per target, the fieldset will now read Network Stack Tuning as opposed to Ip Filter Settings (Adjust for P2P)
Maximum Ports was also wrong, this is in fact Maximum Connections and is so renamed. Lower end devices will have a lower default due to resource consumption as opposed to higher end devices which will have more connections per default.
The settings here are only a portion of Stack Tuning available in the sysctl page in any case, which should only be changed by experienced users
Settings for P2P are the TCP/UDP and maximum connections.
Congestion control will affect the router running VPN in certain circumstances/setups as well as running webserver, iperf via TCP and so on.
I was investigating the possibility that DD-WRT was doing something non standard here (i.e. modifying the LAN/WLAN clients windowing/congestion control algorithm), sometimes features are altered, but not in this case.
Not a full or complete or technical explanation needless to say.
Expect these changes on builds newer than 49413 and as such no point complaining about this old old old issue (10 year+ guesstimate) in build threads either, it is now fixed on dev builds. Other wrongly named strings have been addressed in previous commits, things have been reworded in almost every page, but I dont have all routers to look at, so its possible some strings per device that are not Broadcom will have weird/wrong wording. All in all now DD-WRT UI/UX should be a much improved overall even if not perfect at this time.
TODO is do a small write up for the in (router) page help strings and perhaps more detailed entries on the actual help page (triggered under more...) HManagement.asp
, to be fair you have to have some type of CC and they assume most ppl just plug the WAN cable to the back of the machine and back then (Windows Vista/7) they weren't far from the truth and still in many parts of the world they are close to it.