I’m not entirely convinced that I have a wireless issue so much as a network issue, but eth0 works fine. I can’t get wlan0 to work for the life of me.
I’ve updated my firmware and my card is authenticating against my router. Although I use static IP’s when I switch my router and laptop over to DHCP, my laptop even pulls an address correctly. With all that said and done, I still can’t access the 'Net or ping anything other than the laptop itself. This machine was working fine with Suse 10.2 on it. I reloaded it with 11.1 this morning and have been fighting with it ever since. I have 11.1 on my work laptop with an Intel 4965 chipset and it’s working like a dream. I’ve made certain that both machines have all the same settings but I’m at a loss to explain why one works fine while the other doesn’t. I will gladly accept any advice that anyone may offer.
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0
KevDavison wrote:
> I’m not entirely convinced that I have a wireless issue so much as a
> network issue, but eth0 works fine. I can’t get wlan0 to work for the
> life of me.
>
> I’ve updated my firmware and my card is authenticating against my
> router. Although I use static IP’s when I switch my router and laptop
> over to DHCP, my laptop even pulls an address correctly. With all that
> said and done, I still can’t access the 'Net or ping anything other than
> the laptop itself. This machine was working fine with Suse 10.2 on it. I
> reloaded it with 11.1 this morning and have been fighting with it ever
> since. I have 11.1 on my work laptop with an Intel 4965 chipset and it’s
> working like a dream. I’ve made certain that both machines have all the
> same settings but I’m at a loss to explain why one works fine while the
> other doesn’t. I will gladly accept any advice that anyone may offer.
>
>
> Code:
> --------------------
> # route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.2.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 wlan0
> --------------------
Your routing table looks fine. From here, I would suggest the following series
of ping trials:
All three tests failed. Like I mentioned, I can’t ping anything other than the laptop itself. Whether I use the laptops assigned address or localhost, both work but I can’t ping my router or anything else on my network.
KevDavison wrote:
> All three tests failed. Like I mentioned, I can’t ping anything other
> than the laptop itself. Whether I use the laptops assigned address or
> localhost, both work but I can’t ping my router or anything else on my
> network.
Your wireless has not authenticated/associated. You fooled me with that IP
address, which obviously was not created via DHCP. Backing up a couple of steps
Your wireless has not authenticated/associated. You fooled me with that IP
address, which obviously was not created via DHCP. Backing up a couple of steps
run the following:
dmesg | grep b43
/usr/sbin/iwlist scan
and report the results.
The wireless has indeed authenticated and connects easily. While the address that I displayed was not pulled via DHCP I did mention that when I reconfigure for DHCP, the machine authenticates and pulls an address successfully.
Thanks for your help. This one really has me banging my head. I’ve been a professional Linux Admin for 4 years, using Suse for the last 3 and either this one is totally new on me or I’ve done something incredibly stupid.
$ dmesg |grep b43
b43-pci-bridge 0000:02:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
b43-phy0: Broadcom 4306 WLAN found
input: b43-phy0 as /devices/virtual/input/input8
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Sorry, forgot to mention that “iwlist scan” displayed all of the AP’s in my neighbourhood. There were 15 in the area so I didn’t bother to post the output, but it did return exactly what I would expect it to.
KevDavison wrote:
> Sorry, forgot to mention that “iwlist scan” displayed all of the AP’s in
> my neighbourhood. There were 15 in the area so I didn’t bother to post
> the output, but it did return exactly what I would expect it to.
OK, then we need to look at the logs. Check /var/log/wpa_supplicant.log and
/var/log/NetworkManager to see if any problems show up.
The wpa_supplicant log is might hefty. I’ve found a recurring pattern and just posted one iteration of that. The remainder of the log is just a re-occurrence of the last 5 lines.
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Authentication with 00:04:e2:a7:75:95 timed out.
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Authentication with 00:04:e2:a7:75:95 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Associated with 00:04:e2:a7:75:95
WPA: Key negotiation completed with 00:04:e2:a7:75:95 [PTK=TKIP GTK=WEP-104]
CTRL-EVENT-CONNECTED - Connection to 00:04:e2:a7:75:95 completed (reauth) [id=0 id_str=]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Authentication with 00:04:e2:a7:75:95 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Authentication with 00:04:e2:a7:75:95 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Associated with 00:04:e2:a7:75:95
WPA: Key negotiation completed with 00:04:e2:a7:75:95 [PTK=TKIP GTK=WEP-104]
CTRL-EVENT-CONNECTED - Connection to 00:04:e2:a7:75:95 completed (reauth) [id=0 id_str=]
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Authentication with 00:04:e2:a7:75:95 timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:04:e2:a7:75:95 (SSID='DAVNET' freq=2437 MHz)
Associated with 00:04:e2:a7:75:95
WPA: Key negotiation completed with 00:04:e2:a7:75:95 [PTK=TKIP GTK=WEP-104]
CTRL-EVENT-CONNECTED - Connection to 00:04:e2:a7:75:95 completed (auth) [id=0 id_str=]
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
Here’s a the last connection instance from the NetworkManager. I left the laptop running and “connected” overnight. As a result the last two lines repeat over and over for the remainder of the log so I truncated it. I haven’t had to dive into the NetworkManager in a long time so I’m not seeing much that calls my attention. I highlighted the items I found interesting.
<snip>Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) starting connection 'DAVNET'
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> (wlan0): device state change: 3 -> 4
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> (wlan0): device state change: 4 -> 5
**Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0/wireless): access point 'DAVNET' has security, but secrets are required.**
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> (wlan0): device state change: 5 -> 6
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> (wlan0): device state change: 6 -> 4
Feb 14 18:47:28 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): device state change: 4 -> 5
**Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0/wireless): connection 'DAVNET' has security, and secrets exist. No new secrets needed.**
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'ssid' value 'DAVNET'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'scan_ssid' value '1'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'psk' value '<omitted>'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'proto' value 'WPA'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: added 'pairwise' value 'TKIP'
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Config: set interface ap_scan to 1
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: inactive -> scanning
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'DAVNET'.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> (wlan0): device state change: 5 -> 7
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Feb 14 18:47:29 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.850842] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.864122] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.864351] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.2.1'
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> Clearing nscd hosts cache.
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> (wlan0): device state change: 7 -> 8
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.879694] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.902141] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'
Feb 14 18:47:30 linux-28t1 NetworkManager: <debug> [1234655250.902442] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.2.1'
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> Clearing nscd hosts cache.
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> Policy set 'DAVNET' (wlan0) as default for routing and DNS.
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> Activation (wlan0) successful, device activated.
Feb 14 18:47:30 linux-28t1 NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Feb 14 20:48:29 linux-28t1 NetworkManager: <debug> [1234662509.776203] periodic_update(): Roamed from BSSID 00:04:E2:A7:75:95 (DAVNET) to (none) ((none))
Feb 14 20:48:35 linux-28t1 NetworkManager: <debug> [1234662515.780231] periodic_update(): Roamed from BSSID (none) ((none)) to 00:04:E2:A7:75:95 (DAVNET)
Feb 14 20:50:29 linux-28t1 NetworkManager: <debug> [1234662629.860203] periodic_update(): Roamed from BSSID 00:04:E2:A7:75:95 (DAVNET) to (none) ((none))<snip>
Can I take it that you’ve disabled NetworkManager and are manually controlling your connection? I’ve done that on other machines, but I’m really hoping to make better use of the improvements in NetworkManager this time around. Given that it’s working extremely well now that I’m running 11.1 on my work laptop, I know that it’s at least somewhat reliable and I’m keen to make use of it on my home laptop as well.
In my case I’m not having any trouble with my connection starting on boot. It fires up, associates to the AP, and claims that it’s connected. I just can’t seem to get network access. It’s behaving exactly like you would expect if the router had MAC address filtering enabled (I’ve double and triple checked to make sure that MAC filtering is disabled).Even though I had MAC filtering enabled once upon a time, this machine is in the table and has been working fine up until my 11.1 installation.
KevDavison wrote:
>
> The dmesg is jam packed with the following
>
> Code:
> --------------------
> ll header: ff:ff:ff:ff:ff:ff:00:80:c6:ec:93:f6:08:00
> martian source 192.168.2.255 from 192.168.2.11, on dev wlan0
> --------------------
Are your mask and broadcast addresses OK? What does ‘ifconfig wlan0’ show?
That “ll header” message looks like an IPV6 MAC address. Do you need IPV6? If
not, turn it off with YaST.
OK, I had a feeling that I had done something stupid here. Unfortunately, I fixed the something stupid but it didn’t resolve my problem. The address that I’ve been working with 192.168.2.11, was in use on a another machine that I had forgotten about. I fixed that and moved the laptop in question to 192.168.2.7. I still cannot access the 'Net or ping anything, but that machine now shows up on the nmap scans from my work laptop.
I can’t find any trace of the MAC that was turning up in the martian source entries. That one still has me scratching my head.
$nmap -sP 192.168.2.0/24
Starting Nmap 4.75 ( http://nmap.org ) at 2009-02-15 12:24 EST
Host tick (192.168.2.1)(My Router) appears to be up.
MAC Address: 00:04:E2:A6:82:5A (SMC Networks)
Host 192.168.2.6 (My Fileserver)appears to be up.
MAC Address: 00:03:47:E5:AE:3D (Intel)
Host 192.168.2.7 (The laptop that won't connect)appears to be up.
MAC Address: 00:90:4B:A1:2A:7B (GemTek Technology Co.)
Host 192.168.2.10 (My Home Automation system)appears to be up.
MAC Address: 00:13:D3:2A:B8:E8 (Micro-star International CO.)
Host 192.168.2.11 (Token Win box)appears to be up.
MAC Address: 00:80:C6:EC:93:F6 (National Datacomm)
Host 192.168.2.12 (My Work Laptop)appears to be up.
Host 192.168.2.100 (MYTHTV server)appears to be up.
MAC Address: 00:50:BF:A3:F0:EA (Mototech)
Host 192.168.2.101 (MYTHTV Satellite)appears to be up.
MAC Address: 00:03:47:89:F3:D5 (Intel)
Host 192.168.2.110 (New Desktop-still running DHCP)appears to be up.
MAC Address: 00:05:5D:08:2B:16 (D-Link Systems)
Nmap done: 256 IP addresses (9 hosts up) scanned in 4.49 seconds
I don’t have any need for ipV6 and I turned it off late yesterday. It’s worthy of note that those martian source entries were the last items in the dmesg as of this morning and I haven’t received any since I started working on it this morning so they must have been related to ipV6 being turned on.
KevDavison wrote:
> OK, I had a feeling that I had done something stupid here.
> Unfortunately, I fixed the something stupid but it didn’t resolve my
> problem. The address that I’ve been working with 192.168.2.11, was in
> use on a another machine that I had forgotten about. I fixed that and
> moved the laptop in question to 192.168.2.7. I still cannot access the
> 'Net or ping anything, but that machine now shows up on the nmap scans
> from my work laptop.
>
> I can’t find any trace of the MAC that was turning up in the martian
> source entries. That one still has me scratching my head.
>
>
>
> Code:
> --------------------
> $nmap -sP 192.168.2.0/24
>
> Starting Nmap 4.75 ( http://nmap.org ) at 2009-02-15 12:24 EST
> Host tick (192.168.2.1)(My Router) appears to be up.
> MAC Address: 00:04:E2:A6:82:5A (SMC Networks)
> Host 192.168.2.6 (My Fileserver)appears to be up.
> MAC Address: 00:03:47:E5:AE:3D (Intel)
> Host 192.168.2.7 (The laptop that won’t connect)appears to be up.
> MAC Address: 00:90:4B:A1:2A:7B (GemTek Technology Co.)
> Host 192.168.2.10 (My Home Automation system)appears to be up.
> MAC Address: 00:13:D3:2A:B8:E8 (Micro-star International CO.)
> Host 192.168.2.11 (Token Win box)appears to be up.
> MAC Address: 00:80:C6:EC:93:F6 (National Datacomm)
> Host 192.168.2.12 (My Work Laptop)appears to be up.
> Host 192.168.2.100 (MYTHTV server)appears to be up.
> MAC Address: 00:50:BF:A3:F0:EA (Mototech)
> Host 192.168.2.101 (MYTHTV Satellite)appears to be up.
> MAC Address: 00:03:47:89:F3:D5 (Intel)
> Host 192.168.2.110 (New Desktop-still running DHCP)appears to be up.
> MAC Address: 00:05:5D:08:2B:16 (D-Link Systems)
> Nmap done: 256 IP addresses (9 hosts up) scanned in 4.49 seconds
> --------------------
>
>
> dmesg is also now giving me
>
> Code:
> --------------------
>
> wlan0: authenticate with AP 00:04:e2:a7:75:95
> wlan0: authenticated
> wlan0: associate with AP 00:04:e2:a7:75:95
> wlan0: RX AssocResp from 00:04:e2:a7:75:95 (capab=0x431 aid=13)
> wlan0: associated
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.7 DST=224.0.0.251 LEN=370 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=350
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.7 DST=224.0.0.251 LEN=260 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=240
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.7 DST=224.0.0.251 LEN=370 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=350
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.7 DST=224.0.0.251 LEN=370 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=350
> SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.2.7 DST=224.0.0.251 LEN=340 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=320
> b43-phy0 ERROR: PHY transmission error
> b43-phy0 ERROR: PHY transmission error
> b43-phy0 ERROR: PHY transmission error
The PHY transmission errors won’t cause a problem, but what is at 224.0.0.251? I
tried nslookup on it but wouldn’t resolve to anything.
Have you tried turning off the firewall until you get it working?
I wondered about that 244.0.0.251 myself. Running dmesg on my work laptop shows the same DST=244.0.0.251. While it might need to be corrected, it’s certainly not hindering my work laptop at all.
I stopped the firewall yesterday during testing to no avail. I just shut it down again and then restarted the network services but no joy.
It’s weird after a network restart to watch NetworkManager automatically re-associate to my AP but still not be able to connect.
A quick Google shows 224.0.0.251 to be a common multicast address associated with mDNS as well as Rendezvous and it sends on 5353 which was also in the dmesg entry. As my G5 isn’t powered up I’m pretty sure there isn’t any necessity for Rendezvous but mDNS seems to be a pretty common occurance in a default Linux installation. In any case, I don’t believe that multicasting over the Internet is something that works as yet and I don’t think it’s at the root of what’s causing this.
In the past week I too installed 11.1 (via a KDE 4.2 Live CD). I’m on a Dell Vostro 1000 laptop with a wireless card using the Broadcom chip. My experience is identical to yours. Using Larry’s suggested one line command to install the firmware brought up the wireless lan but I just couldn’t and still can’t get an IP from the router. When I try to use the Network Manager plasmoid to create a network connection the applet crashes. I have been through the forum postings for days now and have tried all manner of things but without success. In one posting I recollected reading a comment from a poster with similar difficulty. He had tracked the time of the loss of his wlan to a kernel upgrade. On reading your posting I made a Version 11.0 Live CD and booted from that. Ran Larry’s one line firmware installaion command, added a network connection using Network Manager, got an IP address from the router and browsed on to the forums just a simply as that. When I alternate between booting in to the 11.0 Live CD and my 11.1 installation, it’s now you see it, now you don’t.
Larry, does this not imply that the problem lies in the most recent kernel?
I had been using 10.3 for a long time. My recollection was that getting the wireless lan to work on 10.3 was difficult. I can’t remember how I sorted it in the end. The one line firmware installation command Larry refers to in many of his postings and the work they have been doing in creating Broadcom Linux drivers really does make it simple but not alas when using 11.1 it seems.