knetworkconf doesn't save gateway

Bug #16177 reported by Sergio Cambra
30
Affects Status Importance Assigned to Milestone
kdeadmin (Ubuntu)
Fix Released
High
Jonathan Riddell

Bug Description

Although I setup a gateway, knetworkconf doesn't save it in /etc/network/interfaces

Revision history for this message
Matthew Carpenter (matt-eisgr) wrote :

Application of Domain Name seems to require clicking "Apply", while "Ok" doesn't
seem to make the changes.

Revision history for this message
Jonathan Riddell (jr) wrote :
Revision history for this message
Chris (cprise) wrote :

Control Center does not apply/retain the manually-entered Default Gateway. This
is not a non-DHCP LAN.

When I try to add a Default Gateway it behaves as if the setting is accepted.
But it isn't and when I exit and return to the network settings, the gateway
field is blank! I had to manually execute a 'route' command in the shell to get
networking operational.

Please test basic use-cases!

Revision history for this message
Andre le Roux (andreler) wrote :

Network setting problem in kubuntu breezy using static adresses
If you set up the network settings properly on installation you will not notice,
but if you try to change network settings from Network Settings on the KDE
desktop, you find the window too big or cut off at the bottom and you cannot get
to the “administrator” button to make admin access. Sometimes you can get the
bottom edge of it, but when entering the password it will accept without giving
you access. If you run sudo kcontrol you can get in as administrator, but then
if you try to change anything you will find that you can enter the gateway ip,
but it will disappear once you go out of the window. It can only then be set
with console command sudo route add default gw 192.168.0.1 This then has to be
done everytime you reboot. To overcome this go to /etc/network/interfaces and
edit by adding the line gateway 192.168.0.1 under the address, netmask, network
and broadcast ip list. It seems as if this problem is not understood or not seen
as a problem as it was present in hoary as well and there are quite a few
threads on this. This is a serious problem and needs to be logged as a bug again.

Revision history for this message
Nigel Ridley (nigel-rmk) wrote :

(In reply to comment #4)
> Network setting problem in kubuntu breezy using static adresses
> If you set up the network settings properly on installation you will not notice,
> but if you try to change network settings from Network Settings on the KDE
> desktop, you find the window too big or cut off at the bottom and you cannot get
> to the “administrator” button to make admin access. Sometimes you can get the
> bottom edge of it, but when entering the password it will accept without giving
> you access. If you run sudo kcontrol you can get in as administrator, but then
> if you try to change anything you will find that you can enter the gateway ip,
> but it will disappear once you go out of the window. It can only then be set
> with console command sudo route add default gw 192.168.0.1 This then has to be
> done everytime you reboot. To overcome this go to /etc/network/interfaces and
> edit by adding the line gateway 192.168.0.1 under the address, netmask, network
> and broadcast ip list. It seems as if this problem is not understood or not seen
> as a problem as it was present in hoary as well and there are quite a few
> threads on this. This is a serious problem and needs to be logged as a bug again.

I searched for this bug on bugzilla but didn't find it so logged it as a
[duplicate] bug (#18637) today.

BTW. You can always hold the Alt key and move a window by dragging the mouse (to
get to an inacessable part of the gui window.

Revision history for this message
Matthew Carpenter (matt-eisgr) wrote :

"BTW. You can always hold the Alt key and move a window by dragging the mouse (to
get to an inacessable part of the gui window."

Nope. Not in this case.

Revision history for this message
Andre le Roux (andreler) wrote :

(In reply to comment #0)
> Although I setup a gateway, knetworkconf doesn't save it in
/etc/network/interfaces

Jonathan,
          The bug is still present. I have updated with all the latest updates
from the repos and have also installed your kde-base-bin file and so far I have
been able to use administrator mode, but in the network settings window the
window still opens larger than the screen and the administrator mode button is
thus off the screen. The static gateway IP still dispappears if you make any
change, such as having 192.168.0.1, change it and change back, click add and you
can go to /etc/network/interfaces and the gateway entry is gone. Enter manually
in the file and it stays put untill you type another gateway ip or make a change
and it disappears again. The line "gateway 192.168.0.1" is cleared every time
the file is rewritten after a changes were made from the kconsole gui. If
someone configures their network properly on installation and make not changes
then it will not show up and thus may be why some have never had a problem here.
Hope this helps as I see a lot of threads around this issue still continually
cropping up. Please let us know if this is receiving attention.
Regards

Revision history for this message
Simon St James (ssj195) wrote :

*** Bug 26197 has been marked as a duplicate of this bug. ***

Revision history for this message
Christopher O'Brien (cmobrienforums) wrote :

I'm getting the same thing here.

The KDE networking config screen accepts my gateway and it says that it writes
all the settings. But when I look at the /etc/network/interfaces file, there is
no gateway in the eth0 configuration. I need to add the gateway with a text
editor for it the setting to take properly.

Also, I'm getting that problem where I need to resize the window on the bottom
so I can click on the "administrator" button. With a resolution below 1024x768,
I was unable to resize the window to get to that button.

Revision history for this message
Jonathan Riddell (jr) wrote :

fixed in dapper

Revision history for this message
Jonathan Riddell (jr) wrote :

*** Bug 24765 has been marked as a duplicate of this bug. ***

Revision history for this message
Dominik Tritscher (dominik-tritscher) wrote :

I get the same error when trying to add an additional nameserver under feisty fawn.
The new nameserver entry is used in the current session, but is not present after a reboot.
What is also strange about that: The "apply"-button is not greyed out after restarting the networking. In all other kcontrol-modules the apply-button is disabled, when there is nothing to apply.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.