eth0 != wlan0

uans · September 26, 2008, 10:01pm

Greetings,

First time posting to this site.
I was following a thread that had a wireless primer in it.
When I got to step# 4, I seemed to run in to a problem.
The interface was named eth0 instead of wlan0 and no ESSID name.
Printout posted below.
Any further suggestions!

Step# 2(b)
05:08.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev 81)

06:00.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

06:00.0 Class 0280: 14e4:4318 (rev 02)

Step# 3
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off

Step# 4
eth3 IEEE 802.11b/g ESSID:off/any Nickname:“Broadcom 4318”
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Step# 5
nrs:/home/radmin # iwlist scan
lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

eth1 Interface doesn’t support scanning.

eth2 Interface doesn’t support scanning.

eth3 Interface doesn’t support scanning : No such device

sit0 Interface doesn’t support scanning.

THKS,
Vince

lwfinger · September 26, 2008, 10:35pm

Your udev rules are what is changing the names. You should look in the
directory /etc/udev/rules.d for a file with “persistent” and “network”
in the name. In most systems, eth0 is the wired interface, and wlanX
is used for wireless.

What version of openSUSE are you running? The driver bcm43xx is no
longer part of the kernel (since 2.6.25) and is not supported.

Larry

uans · September 27, 2008, 12:21am

I am running SUSE v10.2

These are the only files with the words network and/or presistent in them:
nrs:/home/radmin # vi /etc/udev/rules.d/
29-net_trigger_firmware.rules
30-net_persistent_names.rules
31-network.rules
60-persistent-input.rules
60-persistent-storage.rules

lwfinger · September 27, 2008, 1:32am

uans wrote:
> I am running SUSE v10.2

> 30-net_persistent_names.rules

This is the one. Perhaps you might want to post its contents.

Larry

uans · September 27, 2008, 10:48am

/30-net_persistent_names.rules

SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:13:d4:3b:18:cc”, IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:48:54:3f:7c:ce”, IMPORT="/lib/udev/rename_netiface %k eth2"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:13:d4:3b:20:38”, IMPORT="/lib/udev/rename_netiface %k eth1"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:04:e2:f2:45:aa”, IMPORT="/lib/udev/rename_netiface %k ath0"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:21:29:cf:dd:7c”, IMPORT="/lib/udev/rename_netiface %k eth3"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:21:29:e2:20:c8”, IMPORT="/lib/udev/rename_netiface %k wlan0"

lwfinger · September 27, 2008, 4:07pm

You have the most net rules that I have ever seen on a machine. How
many wired interfaces does the the machine have? Have several
different cards been used?

From the iwlist output you sent earlier, you can certainly delete the
rules for eth3 and ath0.

You do have a rule for wlan0. Does the MAC address “00:21:29:e2:20:c8”
match your BCM4318?

Larry

uans · September 27, 2008, 10:54pm

I removed eth0 and ath0.

No, this was the wrong mac address so corrected it.

Step# 4
wlan0 IEEE 802.11b/g ESSID:off/any Nickname:“Broadcom 4318”
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Step# 5
nrs:/home/radmin # iwlist scan
wlan0 Interface doesn’t support scanning : No such device

Vince

lwfinger · September 28, 2008, 2:27am

Vince,

I’m not sure what the problem is, but please post the output of ‘dmesg
| grep bcm’

In addition, please post the output of ‘ls /lib/firmware’.

Larry

uans · September 28, 2008, 3:33am

Larry,

I hope this help!
I may have to install openSUSE v11.0 if we cannot find the problem.

nrs:/home/radmin/downloads # dmesg | grep bcm
bcm43xx driver
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: PHY connected
bcm43xx: Error: Microcode “bcm43xx_microcode5.fw” not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)
bcm43xx: Error: Microcode “bcm43xx_microcode5.fw” not available or load failed.
bcm43xx: core_up for active 802.11 core failed (-2)
bcm43xx: set security called, .active_key = 0, .level = 1, .enabled = 1, .encrypt = 1

nrs:/home/radmin/downloads # ls /lib/firmware/
3CCFEM556.cis atmel_at76c504c-wpa.bin ipw-2.2-bss_ucode.fw LA-PCM.cis
3CXEM556.cis atmel_at76c505a-rfmd2958.bin ipw-2.2-ibss.fw LICENSE.ipw2200-fw
atmel_at76c502_3com.bin atmel_at76c505-rfmd2958.bin ipw-2.2-ibss_ucode.fw LICENSE.ipw2x00
atmel_at76c502_3com-wpa.bin atmel_at76c505-rfmd.bin ipw-2.3-boot.fw LICENSE.ipw3945-ucode
atmel_at76c502.bin atmel_at76c506.bin ipw-2.3-bss.fw MT5634ZLX.cis
atmel_at76c502d.bin atmel_at76c506-wpa.bin ipw-2.3-bss_ucode.fw NE2K.cis
atmel_at76c502d-wpa.bin COMpad2.cis ipw-2.3-ibss.fw PCMLM28.cis
atmel_at76c502e.bin COMpad4.cis ipw-2.3-ibss_ucode.fw PE-200.cis
atmel_at76c502e-wpa.bin DP83903.cis ipw-2.3-sniffer.fw PE520.cis
atmel_at76c502-wpa.bin E-CARD.cis ipw-2.3-sniffer_ucode.fw ql2100_fw.bin
atmel_at76c503-i3861.bin ipw2100-1.3.fw ipw-2.4-boot.fw ql2200_fw.bin
atmel_at76c503-i3863.bin ipw2100-1.3-i.fw ipw-2.4-bss.fw ql2300_fw.bin
atmel_at76c503-rfmd-0.90.2-140.bin ipw2100-1.3-p.fw ipw-2.4-bss_ucode.fw ql2322_fw.bin
atmel_at76c503-rfmd-acc.bin ipw2200-bss.fw ipw-2.4-ibss.fw ql2400_fw.bin
atmel_at76c503-rfmd.bin ipw2200-ibss.fw ipw-2.4-ibss_ucode.fw ql6312_fw.bin
atmel_at76c504_2958-wpa.bin ipw2200-sniffer.fw ipw-2.4-sniffer.fw RS-COM-2P.cis
atmel_at76c504a_2958-wpa.bin ipw-2.2-boot.fw ipw-2.4-sniffer_ucode.fw tamarack.cis
atmel_at76c504.bin

THKS,
Vince

lwfinger · September 28, 2008, 3:58am

uans wrote:
> Larry,
>
> I hope this help!
> I may have to install openSUSE v11.0 if we cannot find the problem.
>
>
> nrs:/home/radmin/downloads # dmesg | grep bcm
> bcm43xx driver
> bcm43xx: Chip ID 0x4318, rev 0x2
> bcm43xx: Number of cores: 4
> bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
> bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
> bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
> bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
> bcm43xx: PHY connected
> bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
> bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
> bcm43xx: Radio turned off
> bcm43xx: Radio turned off
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
> bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
> bcm43xx: PHY connected
> bcm43xx: Error: Microcode “bcm43xx_microcode5.fw” not available or load
> failed.
> bcm43xx: core_up for active 802.11 core failed (-2)
> bcm43xx: Error: Microcode “bcm43xx_microcode5.fw” not available or load
> failed.
> bcm43xx: core_up for active 802.11 core failed (-2)
> bcm43xx: set security called, .active_key = 0, .level = 1, .enabled =
> 1, .encrypt = 1

You do not have the firmware installed. Please do the following:

wget http://bu3sch.de/b43/fwcutter/bcm43xx-fwcutter-006.tar.bz2
tar xjf bcm43xx-fwcutter-006.tar.bz2
cd bcm43xx-fwcutter-006
make
cd …
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
sudo ./bcm43xx-fwcutter-006/bcm43xx-fwcutter -w
“$FIRMWARE_INSTALL_DIR” wl_apsta-3.130.20.0.o

For this to work, you will need to have wget, gcc, and libc installed.

Larry

uans · September 28, 2008, 5:29am

It wil not scan!!!

nrs:/home/radmin # ls /lib/firmware/

bcm43xx_initval01.fw
bcm43xx_initval02.fw
bcm43xx_initval03.fw
bcm43xx_initval04.fw
bcm43xx_initval05.fw
bcm43xx_initval06.fw
bcm43xx_initval07.fw
bcm43xx_initval08.fw
bcm43xx_initval09.fw
bcm43xx_initval10.fw
bcm43xx_microcode11.fw
bcm43xx_microcode2.fw
bcm43xx_microcode4.fw
bcm43xx_microcode5.fw
bcm43xx_pcm4.fw
bcm43xx_pcm5.fw

nrs:/home/radmin # dmesg | grep bcm
bcm43xx driver
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1

nrs:/home/radmin # iwlist scan
wlan0 Interface doesn’t support scanning : No such device

Vince

uans · September 28, 2008, 5:39am

Will not scan!!!

nrs:/home/radmin # ls /lib/firmware/
bcm43xx_initval01.fw
bcm43xx_initval02.fw
bcm43xx_initval03.fw
bcm43xx_initval04.fw
bcm43xx_initval05.fw
bcm43xx_initval06.fw
bcm43xx_initval07.fw
bcm43xx_initval08.fw
bcm43xx_initval09.fw
bcm43xx_initval10.fw
bcm43xx_microcode11.fw
bcm43xx_microcode2.fw
bcm43xx_microcode4.fw
bcm43xx_microcode5.fw
bcm43xx_pcm4.fw
bcm43xx_pcm5.fw

nrs:/home/radmin # dmesg | grep bcm
bcm43xx driver
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 2, .enabled = 1, .encrypt = 1
bcm43xx: set security called, .level = 4, .enabled = 1, .encrypt = 1

nrs:/home/radmin # iwlist scan
wlan0 Interface doesn’t support scanning : No such device

Vince

lwfinger · September 28, 2008, 4:16pm

uans wrote:
> nrs:/home/radmin # iwlist scan
> wlan0 Interface doesn’t support scanning : No such device

This one is new to me. Please save your persistent rules file in
/etc/udev/rules.d and delete the file. After rebooting, see what happens.

Larry

uans · September 28, 2008, 11:31pm

It seems we are back to where we started!

eth3 IEEE 802.11b/g ESSID:off/any Nickname:“Broadcom 4318”
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

nrs:/home/radmin # iwlist scan
eth3 Interface doesn’t support scanning : No such device

Vince

uans · September 28, 2008, 11:36pm

less /etc/udev/rules.d/30-net_persistent_names.rules
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:48:54:3f:7c:ce”, IMPORT="/lib/udev/rename_netiface %k eth2"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:13:d4:3b:18:cc”, IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:13:d4:3b:20:38”, IMPORT="/lib/udev/rename_netiface %k eth1"
SUBSYSTEM==“net”, ACTION==“add”, SYSFS{address}==“00:21:29:cf:dd:7c”, IMPORT="/lib/udev/rename_netiface %k eth3"

Vince

lwfinger · September 29, 2008, 4:16am

uans wrote:
> It seems we are back to where we started!
>
>
> eth3 IEEE 802.11b/g ESSID:off/any Nickname:“Broadcom 4318”
> Mode:Managed Access Point: Invalid
> RTS thr:off Fragment thr:off
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> nrs:/home/radmin # iwlist scan
> eth3 Interface doesn’t support scanning : No such device

Do you really have 4 different network devices on your machine?

I have no idea why the BCM4318 should give the result “No such
device”, other that some other part of networking has been corrupted.

Is it possible for you to update to 11.0? That might be best. Once you
have installed 11.0, then you will need to connect with the wired
connection, and issue the command:

sudo /usr/sbin/install_bcm43xx_firmware

That will install the firmware needed by your BCM4318. It is different
with the new driver than for bcm43xx - the old driver.

Larry

uans · September 30, 2008, 5:12pm

I up graded to v11.0. I am able to due a successful iwlist scan!!!

I did a iwconfig wlan0 and the essid was correct and the levevls were excellent

The ifconfig command showed that I had the correct ip address from dhcp.

But I thuoght when you configure the wireless connect in YaST that the dhcp would automaticlly fill in the nameserver and default gateway. I have Update DNS data via DHCP checked.

Vince