And, BTW, when I manually configure eth1 with the network-admin
adminstrative dialog, the connection works, and sudo ifup eth1 and sudo
ifdown eth1 do work fine:

Aug  2 13:03:10 localhost dhclient: There is already a pid file 
/var/run/dhclient.eth1.pid with pid 134812041
Aug  2 13:03:10 localhost dhclient: Internet Systems Consortium DHCP Client 
V3.0.5
Aug  2 13:03:10 localhost dhclient: Copyright 2004-2006 Internet Systems 
Consortium.
Aug  2 13:03:10 localhost dhclient: All rights reserved.
Aug  2 13:03:10 localhost dhclient: For info, please visit 
http://www.isc.org/sw/dhcp/
Aug  2 13:03:10 localhost dhclient: 
Aug  2 13:03:10 localhost dhclient: wifi0: unknown hardware address type 801
Aug  2 13:03:11 localhost avahi-daemon[4975]: Registering new address record 
for fe80::205:3cff:fe04:51e6 on eth1.*.
Aug  2 13:03:11 localhost dhclient: wifi0: unknown hardware address type 801
Aug  2 13:03:11 localhost dhclient: Listening on LPF/eth1/00:05:3c:04:51:e6
Aug  2 13:03:11 localhost dhclient: Sending on   LPF/eth1/00:05:3c:04:51:e6
Aug  2 13:03:11 localhost dhclient: Sending on   Socket/fallback
Aug  2 13:03:14 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 
port 67 interval 7
Aug  2 13:03:19 localhost kernel: [  780.632000] wifi0: LinkStatus=2 
(Disconnected)
Aug  2 13:03:19 localhost kernel: [  780.632000] wifi0: LinkStatus: 
BSSID=44:44:44:44:44:44
Aug  2 13:03:19 localhost kernel: [  780.640000] wifi0: CMD=0x0121 => res=0x7f, 
resp0=0x0004
Aug  2 13:03:19 localhost kernel: [  780.640000] wifi0: hfa384x_set_rid: 
CMDCODE_ACCESS_WRITE failed (res=127, rid=fc48, len=2)
Aug  2 13:03:19 localhost kernel: [  780.644000] wifi0: LinkStatus=2 
(Disconnected)
Aug  2 13:03:19 localhost kernel: [  780.644000] wifi0: LinkStatus: 
BSSID=44:44:44:44:44:44
Aug  2 13:03:19 localhost kernel: [  780.652000] wifi0: LinkStatus=2 
(Disconnected)
Aug  2 13:03:19 localhost kernel: [  780.652000] wifi0: LinkStatus: 
BSSID=44:44:44:44:44:44
Aug  2 13:03:19 localhost kernel: [  780.664000] eth1: Trying to join BSSID 
00:09:5b:38:87:c0
Aug  2 13:03:19 localhost kernel: [  780.680000] wifi0: LinkStatus=1 (Connected)
Aug  2 13:03:19 localhost kernel: [  780.680000] wifi0: LinkStatus: 
BSSID=00:09:5b:38:87:c0
Aug  2 13:03:20 localhost kernel: [  781.620000] eth1: no IPv6 routers present
Aug  2 13:03:21 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 
port 67 interval 15
Aug  2 13:03:21 localhost dhclient: DHCPOFFER from 192.168.2.1
Aug  2 13:03:21 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 
67
Aug  2 13:03:21 localhost dhclient: DHCPACK from 192.168.2.1
Aug  2 13:03:21 localhost avahi-daemon[4975]: Joining mDNS multicast group on 
interface eth1.IPv4 with address 192.168.2.212.
Aug  2 13:03:21 localhost avahi-daemon[4975]: New relevant interface eth1.IPv4 
for mDNS.
Aug  2 13:03:21 localhost avahi-daemon[4975]: Registering new address record 
for 192.168.2.212 on eth1.IPv4.
Aug  2 13:03:21 localhost dhclient: bound to 192.168.2.212 -- renewal in 2939 
seconds.

-- 
[prism2.5] doesn't associate for network-manager with hostap_cs
https://bugs.launchpad.net/bugs/57146
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to