Home_greyopenFATE - openSUSE feature tracking > #306646
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Add option in yast to disable tcp window scaling

Feature state

Rejected Information
Rejected Information


I live in Guatemala and like most people in countries like mine I don't have a broadband connection, so everytime I install openSUSE I see myself opening a terminal to disable tcp window scalingĀ  and opening kate with root permisions to edit /etc/sysctl.conf to make the change permanent. Though is not complicated to do, it has become an expensive operation to perform. So it would be nice for me and for those of us who need to disable this feature to have an option to disable it in yast. It would be nice to see it in the same tab in which one can disable ipv6.


icons/user_comment.png J. E. wrote: (9 years ago)

So what does the deactivation of TCP Window Scaling have to do with wireless?

icons/user_comment.png J. R. wrote: (9 years ago)

It enables some of us to browse the internet. Take a

icons/user_comment.png J. E. wrote: (9 years ago)

Broken TCP endpoints are nothing that's caused solely by wireless. It affects all types of transport.

FWIW, the option should not be next to ipv6, but it should be in the sysctl editor (whatever yast module that edits /etc/sysconfig/sysctl)

icons/user_comment.png J. R. wrote: (9 years ago)

I don't really care about where it should be. I wouldn't mind to see this feature in another module as long as there's a simple and easy way to do it and having this option in yast makes a lot of sense to me.

icons/user_comment.png M. L. wrote: (9 years ago)

If that eases the download for people in areas with bandwith issues we should make it easy to change in YaST.

icons/user_comment.png R. D. wrote: (8 years ago)

Looking at some tech discussion of this issue from couple years back :



It seems something that YaST Installer could try automatically, when it has a net connection, but downloaders are failing to complete. It's not simply "scaling" good/bad, but something possibly improved by option values.

Putting this in the UI as an option, will lead to complaints about confusing and quirky-ness, and attempting to fallback automagically to better network parameters, is likely easier to program, and YaST could simply report the attempt succeeded or failed; and something like refreshing the repo's could set the option post-installation. That's much better and more informative than posing a boggling option which 99.9% of end users will never need, or will think they need when they in fact don't.

Last change: 8 years ago
Loading tags...
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint