Bug 118043

Version:           0 (using KDE Continue)
Installed from:    2.3.1
Compiler:          kppp/general
OS:                X.............

I tried to set up a dialup connection from an isolated location a while ago. I followed the advice in the manual:
"Choose from the list of connection speeds supported by your serial port. Note that the serial port supports much higher speeds than your modem in most cases. You should probably start with the highest number available, and only reduce it if you have connection problems."
I set the speed to the highest value, 460800 and the modem connected at 9600. It was a working connection but with a severe performance deficiency. It was quite difficult to find a workaround, because there are so many things to consider (modem, serial port configuration, kernel configuration, pppd, kppp). When I was there again 8 months later i tried again. This time I got the very unintuitive idea to reduce the connection speed to increase the connection speed. I tried 230400 without success. Still only 9600. But i did not give up there, after having checked the kernel configuration carefully several times, I was determined to try through the whole list of values. Then I was finally lucky with 115200. It made the actual speed rise to around 44000 (with some small variation). So I found the workaround, but it is a serious usability problem that the user should have to use trial and error. Most users would probably not even pay attention to the connection speed (9600) and just think that "Internet access in Linux is dog slow and sucks". And if they do, they have no idea that lowering the connection speed could fix the problem with a too slow connection speed. And even if they try it, they might give up when lowering to 230400 does not help.

Why is there such an unintuitive mapping between configured connection speed and actual connection speed? Why does the software do such a stupid thing as connecting at 9600 and pretend that everything is all right?