After iw wlan0 scan, Broadcom BCM4311 still not connecting to internet, Suse 12.1, installed firmware and driver via ethernet cable connection to internet, believe I installed correct driver, no hostname specified, sees and names router properly,YAST does not say not connected, must be something simple but cannot figure it out, going bald fast, please help, thanks

Hello,

could you please open a terminal and look at the output of "ifconfig" and "iwconfig". The iwconfig-command will tell you, if wlan0 is connected to any accesspoint.

If this is not the case, please post the output ofMarkus

linux-2gif:~ # iwconfig

lo no wireless extensions.


eth0 no wireless extensions.


wlan0 IEEE 802.11bg ESSID:"Westbrook1338"

Mode:Managed Frequency:2.462 GHz Access Point: E0:91:F5:5D:20:A0

Bit Rate=1 Mb/s Tx-Power=20 dBm

Retry long limit:7 RTS thrff Fragment thrff

Encryption keyff

Power Managementff

Link Quality=69/70 Signal level=-41 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:9 Invalid misc:17 Missed beacon:0


linux-2gif:~ # ifconfig

eth0 Link encap:Ethernet HWaddr 00:1C:23:B2:FC:C6

inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: 2002:328a:f178:e472:1091:9930:a8d5:79f3/64 Scope:Global

inet6 addr: 2002:328a:f178:e472:21c:23ff:feb2:fcc6/64 Scope:Global

inet6 addr: fe80::21c:23ff:feb2:fcc6/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:32847 errors:0 dropped:5 overruns:0 frame:0

TX packets:12000 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:23232863 (22.1 Mb) TX bytes:1174433 (1.1 Mb)

Interrupt:10


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:3676 errors:0 dropped:0 overruns:0 frame:0

TX packets:3676 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:294973 (288.0 Kb) TX bytes:294973 (288.0 Kb)


wlan0 Link encap:Ethernet HWaddr 00:1D9:6B:CA:C4

inet6 addr: fe80::21d:d9ff:fe6b:cac4/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:0 (0.0 b) TX bytes:588 (588.0 b)


linux-2gif:~ # lspci -k | grep -iA4 broadcom

03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)

Subsystem: Dell Device 01f1

Kernel driver in use: b44

03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)

Subsystem: Dell Device 01f1

--

0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)

Subsystem: Dell Wireless 1390 WLAN Mini-Card

Kernel driver in use: b43-pci-bridge

Well,
you are connected to an accesspoint with an ssid (networkname) is Westbrook1338. Your Broadcom-adapter is working!

If you don't have a connection to the internet, you should check your DNS settings, please post the output of

Code:

cat /etc/resolv.conf

you should execute (as root) in order to require a ip-configuration via DHCP.

Markus

I did believe the wireless to be working, but how does Linux know to use it instead of the NIC? I think that is the issue, but:
linux-2gif:~ # dhcpcd wlan0
err, wlan0: timed out
warn, wlan0: using IPV4LL address 169.254.152.135
linux-2gif:~ # dhcpcd wlan0
err, wlan0: dhcpcd already running on pid 17889 (/var/run/dhcpcd-wlan0.pid)
linux-2gif:~ #
The second time I used the command, I connected the ethernet cable. Thanks for your help here, I have another laptop to do as well. I do know how to get my IP address if I need to, in fact I have it saved. Steve

Hi,

you should at first (before executing dhcpcd) use iwconfig and check if the laptop is really connected to the accesspoint. When the second error (dhcpcd already running) occurs, you may use "killall dhcpcd" as root in order to kill this process.

Linux does not automatically select one of the adapters (eth0 or wlan0). I think if you're using Suse, there should be a configuration in YAST where you can tell it to use wlan0 instead of eth0. You should read the documentation for your distribution.

On the commandline you can simply execute "ifconfig eth0 down" as root (or with sudo) in order to kill eth0.

Markus

After your killall, and my attempts to create a dhcp connection, I no longer have access to the router (and what is the "access point")? If anyone out there has been following this thread, this appears to be a Suse 12.1 issue, anyone who can look at these past listings of configurations and, at a glance, determine a YAST configuration that will resolve it would be so helpful, the GUI is thorough but I need to know what I am doing and I do not. Thanks for helping Markus, there is more to this than it seems easy to resolve. Steve

The accesspoint is the basis of your wireless network, in a homenetwork probably your router. You may check the output of iwlist (as you posted above) in order to check this.
Note that we have also a forum for Suse here at LQ http://www.linuxquestions.org/questions/suse-novell-60/ maybe you ask there. I know that there are some very knowledgeable people here at LQ using Suse.

Markus