Version: (using KDE KDE 3.4.2) Installed from: Mandriva RPMs These days, the common use for a modem is when the ADSL fails. So, usually, eth0 exists for the outgoing connection. Therefore, it's desirable to have kppp do `ifdown eth0` before dialing, and `ifup eth0` after disconnect. A GUI option for this would be nice. (Obviously, it would have to ask which ethernet interface to disconnect) As a workaround, I have the following commands in Account->Execute: BEFORE connect: sudo ifdown eth0; sudo mv /etc/resolv.conf /etc/resolv.conf.kpppsave ; sudo touch /etc/resolv.conf UPON disconnect: sudo ifup eth0 There is an additional bug here. If the connection is terminated (eg by pressing Cancel), then the "Upon disconnect" command is not run.
This seems like a bad idea because it would lock out the system from the local area network, wouldn't it? The user would then be unable to access local file servers and printers. It would be better to just close the route to the internet than to shut down the whole interface, right?
Agreed, most of the time. But often there is no local network - all there is an eth0 interface which happens to be up, but which isn't plugged in. (eg a laptop which has been moved away from home). It should be sufficient to have: "Disable existing DNS servers during connection" and "Assign default route to this gateway" BUT, although I have both of these options specified, neither of them is actually taking effect. The output of `route` is unchanged. /etc/resolv.conf does have some new entries added by kppp, but the existing ones are not removed.
I think you can mark this as a dup of the more serious bug 116984
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!