doesn't attach to wifi network at boot/login

[Jos Dehaes]

In addition to ubuntu #40125, now even at boot there is no network. I have to manually select my accesspoint in the list before the network comes online. This is a severe regression.

[Jos Dehaes (jos-dehaes)]

setting severity to major, since the primary purpose of networkmanager is to not have to worry about these things.

[Scott James Remnant (Canonical) (canonical-scott)]

Please provide more information.

What wireless card do you have? What other network cards are present? Do any of the wired cards have a cable attached?

Attach your /etc/network/interfaces file, along with /etc/iftab and output of "ifconfig -a"

[Jos Dehaes (jos-dehaes)]

I have a wired network card (not connected):
0000:02:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

The wifi card is:
0000:07:00.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)

jos@hamerkeuh:~$ 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

#iface eth2 inet dhcp
#wireless-essid dehaes
#auto eth2

jos@hamerkeuh:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0C:6E:35:97:7C
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 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:11 Base address:0xc000

eth2 Link encap:Ethernet HWaddr 00:04:E2:B3:62:F4
          inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::204:e2ff:feb3:62f4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:359 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:409852 (400.2 KiB) TX bytes:39308 (38.3 KiB)
          Interrupt:11

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:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:572 (572.0 b) TX bytes:572 (572.0 b)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

jos@hamerkeuh:~$ cat /etc/iftab
# This file assigns persistent names to network interfaces.
# See iftab(5) for syntax.

eth0 mac 00:0c:6e:35:97:7c arp 1
eth1 mac 00:04:e2:b3:62:f4 arp 1

[Scott James Remnant (Canonical) (canonical-scott)]

There is a known bug in NetworkManager where the wireless interface gets renamed.

Try commenting out the eth1 line in /etc/iftab

[Scott James Remnant (Canonical) (canonical-scott)]

possible dup of bug 42861 if that fixes it for you

[Jos Dehaes (jos-dehaes)]

commenting eth1 in /etc/iftab fixes this.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]