Nope, since it turns out that your bcm43xx driver isn't advertising itself as a wireless device. At least, it certainly doesn't have any /sys/class/net/eth1/wireless directory. Which it should. So something with the driver seems broken.
Ok, well it's already been established that the bcm43xx driver is pretty dodgy. I suppose I should be looking more in that direction then.
If you "cat /sys/class/net/eth1/type", what do you get?
It outputs: 1
Are there any bcm43xx messages in the output of 'dmesg'?
running "dmesg | grep bcm43xx" gives me: bcm43xx driver bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243, enabled bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243, disabled bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243, enabled bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243, disabled bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off bcm43xx: set security called bcm43xx: .level = 0 bcm43xx: .enabled = 0 bcm43xx: .encrypt = 0 bcm43xx: PHY connected bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: 80211 cores initialized bcm43xx: Keys cleared bcm43xx: Radio turned off bcm43xx: DMA 0x0200 (RX) max used slots: 1/64 bcm43xx: DMA 0x0260 (TX) max used slots: 0/512 bcm43xx: DMA 0x0240 (TX) max used slots: 0/512 bcm43xx: DMA 0x0220 (TX) max used slots: 2/512 bcm43xx: DMA 0x0200 (TX) max used slots: 0/512 bcm43xx: PHY connected bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: 80211 cores initialized bcm43xx: Keys cleared Just to make sure I don't get caught not including the right information again, I've included the full output of dmesg as an attachment. The card itself is working. Like I said, if I turn all encryption on the network off, it connects just fine. So I guess in that sense, NetworkManager is working fine. It's being told it's a wired card and if it doesn't have to deal with anything specific to wireless networks, then it runs the connect scripts like it's supposed to. Weird. So it's sounding more and more like a udev thing then. Good, I was beginning to think this was going to be easy. :-)
Attachment:
dmesg.out
Description: Binary data