Wired not available in NetworkManager after wireless is used (Gutsy)

[Mackenzie Morgan]

1. Connect to wireless network
2. Plug in ethernet cable
3. Click on NetworkManager with intent to switch to wired network
4. Wired network option is greyed out.

Right-clicking and disabling wireless also doesn't work. I'm guessing maybe that's the underlying bug, and that the wired connection won't connect because wireless isn't releasing.

[Alexander Sack (asac)]

plesae post your /etc/network/interfaces and tell us which interface is the wired one. Further attach your /var/log/syslog as well.

[Alexander Sack (asac)]

for now this looks more like a plain network-manager bug, than an applet one.

[Mackenzie Morgan (maco.m)]

Sorry this took a while. I replied to the bug through email and attached the info, but it appears not to have made it here.

$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

Which likely doesn't help :P This might be useful:

$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:E0:B8:AB:C7:6C
          inet addr:161.253.8.116 Bcast:161.253.11.255 Mask:255.255.252.0
          inet6 addr: fe80::2e0:b8ff:feab:c76c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:236640 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16196 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:57640590 (54.9 MB) TX bytes:2750729 (2.6 MB)
          Interrupt:17

eth1 Link encap:Ethernet HWaddr 00:13:02:4C:BC:CC
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:5615 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:16 Base address:0x2000 Memory:d6000000-d6000fff

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:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1693 (1.6 KB) TX bytes:1693 (1.6

/var/log/syslog is attached. I just reproduced the bug to get the right
info into the syslog. This time, the "wired network" option didn't stay
greyed out, but it was still unusable. Clicking on it didn't activate
the radio button.

[Francis Bond (bond)]

I am also getting this behavior on an X60 with the atheros wireless card (self compiled).

If I change the wired connection to be manuall configured, DHCP, then ifup eth0, it works fine.

[Mackenzie Morgan (maco.m)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems to work for me now, though it's rather slow at it. It takes
about a minute before it sees and tries to connect to the wired connection.

Francis Bond wrote:
> I am also getting this behavior on an X60 with the atheros wireless card
> (self compiled).
>
> If I change the wired connection to be manuall configured, DHCP, then
> ifup eth0, it works fine.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHFjOdojm3DbyNMmkRAhagAJ9gR16OAmgHL0EC986YTGTyWlNodACgs0tM
ro9mT8fvLrkXQDxJ/dzpx/E=
=1He8
-----END PGP SIGNATURE-----

[Alexander Sack (asac)]

please test if the test-package provided at https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/145683/comments/15 helps for you as well.

Thanks,
 - Alexander

[Xvani (fredrile+launchpad)]

I also have this problem..

Which of the packages should I be using?

[GregR1 (bluepowder7)]

Alexander - i was forwarded this bug report and hoped to find a solution to my own bug which i also reported. To date, i have no solution, and if i try to run a package from your link, my installer says "Error: a more recent version is already installed" or words to that effect. I grabbed this file:

network-manager_0.6.5-0ubuntu16~ppa3_i386.deb 11-Oct-2007 16:40 267K

has there been any more recent work on this?
here's my bug report, in case you want to look into it:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/160394

[ke1g (ke1g-nh)]

I haven't tried wired, but I may have another manifestation of this, or I may have something unrelated,
so I ask, are you able to switch locations when they use different access points?

When I use network-manager to select and apply another location, for the purpose of connecting the
the AP that I'm now near (roaming never worked for me in feisty), I get the song and dance, but no IP
address on the interface (ath0, atheros in a Toshiba). If I then reboot, the interface comes up fine
with the newly selected AP.

If you're experience doesn't match, I'll perhaps open a fresh bug. But it strikes me that the problems
might be related.

[GregR1 (bluepowder7)]

around here, there's 3 wireless networks available (mine, plus two
neighbours broadcasting their SSID). my network manager automatically
connects me to my router (likely tied to the keyring), but if i try to
change it to access one of the other two signals, it doesn't change
over at all. so, it may be related to what you are experiencing. the
other signals aren't wimpy - one is at least 50% full, the other (when
it shows up) is around 20%.

it seems that at least 95% of the time, one boot session gets me one
interface. wanna change interface? gotta reboot. *groan*

On Nov 28, 2007 3:09 PM, ke1g <email address hidden> wrote:
> I haven't tried wired, but I may have another manifestation of this, or I may have something unrelated,
> so I ask, are you able to switch locations when they use different access points?
>
> When I use network-manager to select and apply another location, for the purpose of connecting the
> the AP that I'm now near (roaming never worked for me in feisty), I get the song and dance, but no IP
> address on the interface (ath0, atheros in a Toshiba). If I then reboot, the interface comes up fine
> with the newly selected AP.
>
> If you're experience doesn't match, I'll perhaps open a fresh bug. But it strikes me that the problems
> might be related.
>
>
> --
> Wired not available in NetworkManager after wireless is used (Gutsy)
> https://bugs.launchpad.net/bugs/148630
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Greg R.

[ke1g (ke1g-nh)]

I found the long cat-5 cable and plugged in. Maybe I wasn't patient enough, but the interface
didn't come up on its own. It was suitably checked, and DHCP was selected. I can bring it
up with sudo ifconfig eth0 down followed by ...up , but I also have to bring the wireless down
with ifconfig before the routing gets changed to use the wired (I have a slide switch to shut off
WiFi, again, maybe I didn't wait long enough). I'm not sure what to try in order to confirm what.
I can cycle things in various ways if it helps in the search (though this will be my last playing
for about 18 hours). Just make a detailed suggestion.

[Basilio Kublik (sourcercito)]

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

[Mackenzie Morgan (maco.m)]

Works on Hardy

[Basilio Kublik (sourcercito)]

Hi there
Thanks for your time and feedback, I'm closing this report due your last comment about being fixed in the soon to be stable release of Ubuntu.