network-manager - active connection information (network) is wrong

[Jeroen Maris]

Binary package hint: network-manager

My new Ubuntu 7.10 Tribe 3 with all updates shows an icon for my networkcard (Intel Pro1000PT PCI-e). When I right-click on it and select "Connection Information", only the IP-address and the Hardware Address are filled in, the broadcast address, subnet mask, default route, primary dns and secondary dns are all set to "0.0.0.0". Although everything related to network connectivity is OK, these fields should be filled, but are not. In Ubuntu 7.04 these fields were filled with the actual information.

ProblemType: Bug
Architecture: i386
Date: Mon Jul 23 21:40:59 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-panel
NonfreeKernelModules: nvidia
Package: gnome-panel 1:2.19.5-0ubuntu3
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/jeroen
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux Nemo 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux

[Jeroen Maris (jealma)]

This screenshot shows the connection information dialog. Note that most fields are set to 0.0.0.0

[Jeroen Maris (jealma)]

This is the output of "ifconfig eth0". Note that a broadcast address is present, as well as a network mask.

[Jeroen Maris (jealma)]

This is the content of the resolv.conf file, showing that a primary DNS is present, but it does not show up in the connection information dialog.

[Johan Van Hellemont (johan-van-hellemont)]

I can confirm this with updated tribe 3.
network-manager 0.6.5-0ubuntu7
network-manager-gnome 0.6.5-0ubuntu6
here is the output of ifconfig

eth0 Link encap:Ethernet HWaddr 00:16:41:55:AB:F0
          inet addr:213.118.242.201 Bcast:213.118.247.255 Mask:255.255.248.0
          inet6 addr: fe80::216:41ff:fe55:abf0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:750 errors:0 dropped:0 overruns:0 frame:0
          TX packets:482 errors:0 dropped:0 overruns:0 carrier:0
          collisions:127 txqueuelen:1000
          RX bytes:446846 (436.3 KB) TX bytes:64702 (63.1 KB)
          Interrupt:16

[Johan Van Hellemont (johan-van-hellemont)]

When I right-click on the nm-applet and uncheck ''Enable Networking'' and check again the connection information is now visible.

[Alexander Sack (asac)]

Hi,

does this only happen for devices that are configure as auto in /etc/network/interfaces ?

 - Alexander

[Achim (ach1m)]

Yes,

If I configured the NIC with "network-admin" manually, I doesn't get any information from nm-applet.

p.s. I can confirm what "johan Van Hellemont" wrote.
My NIC is a Intel Gigabit Lan (module e1000).

I hope this helps to solve the problem.

best wishes
Achim

[Johan Van Hellemont (johan-van-hellemont)]

Problem fixed with Tribe 5 for me.

[Jeroen Maris (jealma)]

Not for me. I've installed a fresh Kubuntu 7.10 tribe5 and installed every update, but still the same problem here also. And if I remember correctly, ubuntu 7.10 tribe5 also still has this problem.

[Johan Van Hellemont (johan-van-hellemont)]

Problem is back again after today's updates,maybe the update of dhcp3?
Devices are configured as auto.

johan@thinkpad:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

[Johan Van Hellemont (johan-van-hellemont)]

fixed for me in network-manager 0.6.5-0ubuntu12.
Thanks!

[Alexander Sack (asac)]

Jeroen, can you please test the latest network-manager in gutsy? (0.6.5-0ubuntu14)

[Alexander Sack (asac)]

well ... latest is current 0.6.5-0ubuntu13 ... but ubuntu14 should be available soon as well. Shouldn't matter much for your case

[Jeroen Maris (jealma)]

Sorry for the late response, but the problem was fixed since about two days ago. An update of NetworkManager fixed the problem. The version that I currently use is 0.6.5-0ubuntu13.

[Alexander Sack (asac)]

fixed in 0.6.5-0ubuntu13 ... as expected.

Thanks for confirming,

 - Alexander