After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589003 - applet indicates no connection while lan is active
applet indicates no connection while lan is active
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.7.x
Other Linux
: Normal minor
: ---
Assigned To: Dan Williams
Dan Williams
: 587946 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-19 09:32 UTC by bbfk
Modified: 2010-01-30 22:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description bbfk 2009-07-19 09:32:08 UTC
I have a lan here at home with a gateway to a dsl-router.

Networkmanager knows about it and shows ifupdown (eth0) as present but the applet itself indicates no connection.
Comment 1 Dan Williams 2009-08-20 03:08:45 UTC
From a terminal, could you run 'nm-tool' and paste the output into this bug?
Comment 2 bbfk 2009-08-21 18:03:29 UTC
$ nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            e100
  State:             unmanaged
  Default:           no
  HW Address:        00:00:00:00:00:00

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on
Comment 3 bbfk 2009-08-21 18:13:02 UTC
I add the ifconfig output:
ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:02:b3:cd:e1:a8  
          inet Adresse:192.168.1.200  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6-Adresse: fe80::202:b3ff:fecd:e1a8/64 Gültigkeitsbereich:Verbindung


and 

dmesg |grep e100
[    0.488076] pci 0000:00:0b.0: Firmware left e100 interrupts enabled; disabling
[    1.256207] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    1.256263] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.256379] e100 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    1.276307] e100 0000:00:0b.0: PME# disabled
[    1.277324] e100: eth0: e100_probe: addr 0xcfffc000, irq 19, MAC addr 00:02:b3:cd:e1:a8
[   33.816237] e100: eth0 NIC Link is Up 100 Mbps Full Duplex

I remember that I had some issues about not available proprietary e100 driver, however, since the lan was always available I have ignored those messages I cannot find any other error with regard to the intel e100 card in dmesg.

system: linux 2.6.30-1-686 and debian sid last updated within the last 5 days.
gnome
Comment 4 bbfk 2009-08-21 18:57:12 UTC
I add the ifconfig output:
ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:02:b3:cd:e1:a8  
          inet Adresse:192.168.1.200  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6-Adresse: fe80::202:b3ff:fecd:e1a8/64 Gültigkeitsbereich:Verbindung


and 

dmesg |grep e100
[    0.488076] pci 0000:00:0b.0: Firmware left e100 interrupts enabled; disabling
[    1.256207] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    1.256263] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.256379] e100 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    1.276307] e100 0000:00:0b.0: PME# disabled
[    1.277324] e100: eth0: e100_probe: addr 0xcfffc000, irq 19, MAC addr 00:02:b3:cd:e1:a8
[   33.816237] e100: eth0 NIC Link is Up 100 Mbps Full Duplex

I remember that I had some issues about not available proprietary e100 driver, however, since the lan was always available I have ignored those messages I cannot find any other error with regard to the intel e100 card in dmesg.

system: linux 2.6.30-1-686 and debian sid last updated within the last 5 days.
gnome
Comment 5 Dan Williams 2010-01-30 22:44:25 UTC
Ok, so NetworkManager reports eth0 as being "unmanaged".  On Debian/Ubuntu for backwards compatibility, NM is set to ignore any devices you have specified in /etc/network/interfaces, and since they are ignroed of course NM doesn't know anything about them or what their state is.  If you want NM to manage those devices, you can remove any entry in /etc/network/interfaces relating to eth0 and NM should magically find the device and manage it.
Comment 6 Dan Williams 2010-01-30 22:46:11 UTC
*** Bug 587946 has been marked as a duplicate of this bug. ***