Cannot activate network interface in kubuntu after switching to manual configuration

Bug #212365 reported by Christopher Yee Mon
4
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Confirmed
Undecided
Luka Renko

Bug Description

Binary package hint: knetworkmanager

Summary: Applied manual configuration in kubuntu in order to switch from dhcp to static addresses for one machine. It wouldn't enable the interface after that.

Steps
1. Install Ubuntu
2. Install kubuntu-desktop on top of that
3. Verify that the machine is using the automatic configuration in KNetworkManager
4. Right-click the network icon in the system tray and choose Manual configuration
5. Select the interface and select Configure Interface, select the option for Manual address and check the box for 'Activate when the computer starts ', select OK, OK
6. Verify if the network is enabled by single clicking the network icon on KNetworkManager in the system tray
7. Attempt to ping other machines in the network or ping yahoo.com
8. Restart the machine and attempt steps 6 and 7 again
9. Logout and login to Gnome and re try step 6 and 7

Expected Results: Once setting the manual configuration in step 5, if the ip address that was set was a free valid one in that network subnet, the interface that was changed should be displayed as active in step 6 when checking the connection status. In addition to this, the pings of the network and yahoo.com should be successful in step 7. The retries in step 8 and 9 should also be successful.

Actual Results: Once the configuration is changed to manual in step 5, the connection status in step 6 reveals that no network device is active. the attempts at accessing other machines on the network in step 7 is not successful.

The retry after restarting in step 8 also fails.

Once logging into Gnome however, the equivalent Network Manager status dialog in gnome shows that the network is set to the address that was set in kubuntu manual configuration, network manager also shows that the configuration is set to manual. The pings are also successful in gnome in this manual configuration.

If Manual configuration is also accessed, and Roaming mode enabled so that Network Manager manages the connection as dhcp, when logging back into kde, the network interface works again.

The network interface should remain active if setting it to manual from kubuntu knetworkmanager

Revision history for this message
Luka Renko (lure) wrote :

Can you attach your /etc/network/interfaces file after switching to manual?
Can you provide output of "ifconfig" command when using manual config?
Do you use ping from command line? what is the exact message you get on ping?

Changed in knetworkmanager:
assignee: nobody → lure
status: New → Incomplete
Revision history for this message
Christopher Yee Mon (christopher-yeemon) wrote :
Download full text (5.9 KiB)

Here is cat /etc/network/interfaces, ifconfig and the ping of the lan and yahoo before turning on manual configuration:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

eth0 Link encap:Ethernet HWaddr 00:1A:92:B3:70:CC
          inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21a:92ff:feb3:70cc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1336386 errors:0 dropped:0 overruns:0 frame:0
          TX packets:798237 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1788255530 (1.6 GB) TX bytes:96982579 (92.4 MB)
          Interrupt:18

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1073 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1073 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:35283 (34.4 KB) TX bytes:35283 (34.4 KB)

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.952 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.781 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.742 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.10 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.08 ms

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4014ms
rtt min/avg/max/mdev = 0.742/0.932/1.105/0.154 ms

PING yahoo.com (216.109.112.135) 56(84) bytes of data.
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=1 ttl=54 time=18.2 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=2 ttl=54 time=14.8 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=3 ttl=54 time=19.7 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=4 ttl=54 time=14.4 ms
64 bytes from w2.rc.vip.dcn.yahoo.com (216.109.112.135): icmp_seq=5 ttl=54 time=14.5 ms

--- yahoo.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4008ms
rtt min/avg/max/mdev = 14.485/16.376/19.773/2.204 ms

Here is cat /etc/network/interfaces, ifconfig and the ping of the lan and yahoo after turning on manual configuration:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth0 inet static
address 192.168.1.103
netmask 255.255.255.0
gateway 192.168.1.1

eth0 Link encap:Ethernet HWaddr 00:1A:92:B3:70:CC
          inet6 addr: fe80::21a:92ff:feb3:70cc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:23880 (23.3 KB) TX bytes:492 (492.0 b)
          Interrupt:18

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:1073 errors:0 dropped:0 overruns:...

Read more...

Changed in knetworkmanager:
status: Incomplete → New
Revision history for this message
Jason Straight (jason-jeetkunedomaster) wrote :

Same here, dhcp works, however setting static networking does nothing when selecting a configuration, also disabled wireless just to make sure, still nothing.

Changed in knetworkmanager:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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