Re: link status and association

2006-04-16 Thread David Woodhouse
On Fri, 2006-04-14 at 11:06 +0200, Yves-Alexis Perez wrote:
 iirc you -always- had to mount the interface *before* associating. When
 you modprobe the module the radio is turned off, mounting the interface
 does enable the radio. dmesg outputs are pretty clear on it:

Yes, that's a bug. I fixed this in the Fedora Core 5 kernel -- I'm
fairly sure I also sent the patch here.

-- 
dwmw2

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: link status and association

2006-04-14 Thread Yves-Alexis Perez
On Thu, 2006-04-13 at 19:52 -0600, Hans Fugal wrote:
 This is what I am observing:
 
 modprobe bcm43xx
 iwconfig eth1 essid foo
 ip link set up eth1

iirc you -always- had to mount the interface *before* associating. When
you modprobe the module the radio is turned off, mounting the interface
does enable the radio. dmesg outputs are pretty clear on it:


Apr 14 11:04:57 hidalgo sudo:   corsac : TTY=pts/2 ; PWD=/home/corsac ;
USER=root ; COMMAND=/sbin/modprobe bcm43xx
Apr 14 11:04:57 hidalgo kernel: bcm43xx driver
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Chip ID 0x4306, rev 0x3
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Number of cores: 5
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Core 0: ID 0x800, rev 0x4,
vendor 0x4243, enabled
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Core 1: ID 0x812, rev 0x5,
vendor 0x4243, disabled
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Core 2: ID 0x80d, rev 0x2,
vendor 0x4243, enabled
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Core 3: ID 0x807, rev 0x2,
vendor 0x4243, disabled
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Core 4: ID 0x804, rev 0x9,
vendor 0x4243, enabled
Apr 14 11:04:57 hidalgo kernel: bcm43xx: PHY connected
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Detected PHY: Version: 2, Type
2, Revision 2
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Detected Radio: ID: 2205017f
(Manuf: 17f Ver: 2050 Rev: 2)
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Radio turned off
Apr 14 11:04:57 hidalgo kernel: bcm43xx: Radio turned off


Then:

Apr 14 11:05:26 hidalgo sudo:   corsac : TTY=pts/2 ; PWD=/home/corsac ;
USER=root ; COMMAND=/sbin/ip link set up eth1
Apr 14 11:05:26 hidalgo kernel: bcm43xx: PHY connected
Apr 14 11:05:27 hidalgo kernel: bcm43xx: Radio turned on
Apr 14 11:05:27 hidalgo kernel: bcm43xx: Chip initialized
Apr 14 11:05:27 hidalgo kernel: bcm43xx: DMA initialized
Apr 14 11:05:27 hidalgo kernel: bcm43xx: 80211 cores initialized
Apr 14 11:05:27 hidalgo kernel: bcm43xx: Keys cleared
Apr 14 11:05:27 hidalgo kernel: ADDRCONF(NETDEV_UP): eth1: link is not
ready
Apr 14 11:05:27 hidalgo ifd[3367]: executing:
'/usr/share/laptop-net/link-change eth1 unmanaged unknown
up,running,disconnected'


Then:

Apr 14 11:05:42 hidalgo sudo:   corsac : TTY=pts/2 ; PWD=/home/corsac ;
USER=root ; COMMAND=/sbin/iwconfig eth1 essid droledequartier
Apr 14 11:05:49 hidalgo kernel: printk: 179 messages suppressed.
Apr 14 11:05:49 hidalgo kernel: SoftMAC: Open Authentication completed
with 00:14:bf:3c:98:df
Apr 14 11:05:49 hidalgo kernel: ADDRCONF(NETDEV_CHANGE): eth1: link
becomes ready
Apr 14 11:05:50 hidalgo ifd[3367]: executing:
'/usr/share/laptop-net/link-change eth1 unmanaged
up,running,disconnected up,running,connected'

Then:

Apr 14 11:06:13 hidalgo sudo:   corsac : TTY=pts/2 ; PWD=/home/corsac ;
USER=root ; COMMAND=/sbin/ifup eth1
Apr 14 11:06:13 hidalgo dhclient: Internet Systems Consortium DHCP
Client V3.0.3
Apr 14 11:06:13 hidalgo dhclient: Copyright 2004-2005 Internet Systems
Consortium.
Apr 14 11:06:13 hidalgo dhclient: All rights reserved.
Apr 14 11:06:13 hidalgo dhclient: For info, please visit
http://www.isc.org/products/DHCP
Apr 14 11:06:13 hidalgo dhclient:
Apr 14 11:06:14 hidalgo dhclient: Listening on
LPF/eth1/00:11:24:96:be:70
Apr 14 11:06:14 hidalgo dhclient: Sending on
LPF/eth1/00:11:24:96:be:70
Apr 14 11:06:14 hidalgo dhclient: Sending on   Socket/fallback
Apr 14 11:06:16 hidalgo dhclient: DHCPREQUEST on eth1 to 255.255.255.255
port 67
Apr 14 11:06:16 hidalgo dhclient: DHCPACK from 192.168.0.1
Apr 14 11:06:16 hidalgo avahi-daemon[2392]: New relevant interface
eth1.IPv4 for mDNS.
Apr 14 11:06:16 hidalgo avahi-daemon[2392]: Joining mDNS multicast group
on interface eth1.IPv4 with address 192.168.0.21.
Apr 14 11:06:16 hidalgo avahi-daemon[2392]: Registering new address
record for 192.168.0.21 on eth1.
Apr 14 11:06:16 hidalgo dhclient: bound to 192.168.0.21 -- renewal in
34620 seconds.

I've always seen this behavior and iirc it's intended.

Regards,

-- 
Yves-Alexis Perez

___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev


Re: link status and association

2006-04-14 Thread Hans Fugal
On Fri, 14 Apr 2006 at 11:06 +0200, Yves-Alexis Perez wrote:
 On Thu, 2006-04-13 at 19:52 -0600, Hans Fugal wrote:
  This is what I am observing:
  
  modprobe bcm43xx
  iwconfig eth1 essid foo
  ip link set up eth1
 
 iirc you -always- had to mount the interface *before* associating. When
 you modprobe the module the radio is turned off, mounting the interface
 does enable the radio. dmesg outputs are pretty clear on it:

Yes, this has been the case since I began using the driver. 

 I've always seen this behavior and iirc it's intended.

Is it really? This is not how other drivers work. I have a usb
zd1201-based wireless device, and I can set the essid and key before
bringing the link up, and it just works when I do bring the link up.
It continues to work if I bring the link down briefly and then back up.

From a user's perspective I would argue that it makes no sense that you
can set the essid and key without error, and run iwconfig and see the
values you set, and yet it doesn't work unless you set it _again_, after
bringing the link up. If you look at the archives you'll see quite a few
people have tripped up on this in the past. 

It also makes logical sense to prepare level 2 before initiating level
3. If you were to change the mac address on an ethernet driver, you
would not expect to only be able to do this after bringing the link up.

Just my humble opinion - I'm no driver developer, just a user with an
opinion. :)

-- 
Hans Fugal ; http://hans.fugal.net
 
There's nothing remarkable about it. All one has to do is hit the 
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach


signature.asc
Description: Digital signature