"wmaster0 unknown address type 801" and failed DHCP with wireless on home portal

silencestone · 11-03-2008, 08:45 AM

The internal wireless has been very troublesome on this Gateway MT6707 laptop. The interface identifies as a Realtek RTL8187 on USB. Now, it connects to my homeportal wirelessly running Windows Vista without problem, but no matter what Linux distro and kernel, it doesn't successfully connect wirelessly to my homeportal (WEP or unsecured), although I've had success on some free, unsecured wifi hotspots.

So far, I've tried various Linux configurations. 2.6.24 and up kernels have the driver for the card included in them. 2.6.21 and 2.6.22 kernels didn't have the driver in the kernel, so I tried ndiswrapper with Windows 98, XP, and 2000 drivers. When the driver actually loaded and a network interface for the card appeared, it still wouldn't connect to my home network after bringing up the interface, scanning to make sure it saw my network, configuring the interface for my network, and attempting IP through DHCP. The failure looks like this:

root@mt6707#: dhclient wlan0
wmaster0: Unknown hardware address type 801
wmaster0: Unknown hardware address type 801

And then it seems to "authenticate", but times out on "associate" on the access point.

Here's part of the syslog on Linux Mint 5.0, before I uninstalled Network Manager due to its possible interference:

Quote:

Sep 8 05:50:43 mint NetworkManager: <info> Old device 'wlan0' activating, won't change.
Sep 8 05:51:17 mint last message repeated 4 times
Sep 8 05:51:30 mint last message repeated 2 times
Sep 8 05:51:33 mint kernel: [ 675.465525] wlan0: Initial auth_alg=0
Sep 8 05:51:33 mint kernel: [ 675.465537] wlan0: authenticate with AP <MY_AP_WAS_HERE>
Sep 8 05:51:33 mint kernel: [ 675.640901] wlan0: Initial auth_alg=0
Sep 8 05:51:33 mint kernel: [ 675.640909] wlan0: authenticate with AP <MY_AP_WAS_HERE>
Sep 8 05:51:33 mint kernel: [ 675.645072] wlan0: RX authentication from <MY_AP_WAS_HERE> (alg=0 transaction=2 status=0)
Sep 8 05:51:33 mint kernel: [ 675.645080] wlan0: authenticated
Sep 8 05:51:33 mint kernel: [ 675.645085] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:51:33 mint kernel: [ 675.650931] wlan0: authentication frame received from <MY_AP_WAS_HERE>, but not in authenticate state - ignored
Sep 8 05:51:33 mint kernel: [ 675.843275] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:51:34 mint kernel: [ 676.043042] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:51:34 mint kernel: [ 676.242808] wlan0: association with AP <MY_AP_WAS_HERE> timed out
Sep 8 05:51:38 mint NetworkManager: <info> Old device 'wlan0' activating, won't change.
Sep 8 05:51:38 mint NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), asking for new key.
Sep 8 05:51:38 mint NetworkManager: <info> Activation (wlan0) New wireless user key requested for network '<MY_ESSID_WAS_HERE>'.
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) New wireless user key for network '<MY_ESSID_WAS_HERE>' received.
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep 8 05:52:12 mint NetworkManager: <info> Activation (wlan0/wireless): access point '<MY_ESSID_WAS_HERE>' is encrypted, and a key exists. No new key needed.
Sep 8 05:52:13 mint NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Sep 8 05:52:13 mint NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I'
Sep 8 05:52:13 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> kernel_driver for non broadcast check: rtl8187 (has_scan_capa_ssid=1)
Sep 8 05:52:14 mint NetworkManager: <info> Fully supported scan_capa_ssid mode.
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was '0'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 3257495245303333'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Sep 8 05:52:14 mint NetworkManager: <info> SUP: response was 'OK'
Sep 8 05:52:14 mint NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep 8 05:52:16 mint NetworkManager: <info> Old device 'wlan0' activating, won't change.
Sep 8 05:52:32 mint last message repeated 2 times
Sep 8 05:52:32 mint kernel: [ 734.360365] wlan0: Initial auth_alg=0
Sep 8 05:52:32 mint kernel: [ 734.360375] wlan0: authenticate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:32 mint kernel: [ 734.535936] wlan0: Initial auth_alg=0
Sep 8 05:52:32 mint kernel: [ 734.535946] wlan0: authenticate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:32 mint kernel: [ 734.535967] wlan0: Initial auth_alg=0
Sep 8 05:52:32 mint kernel: [ 734.535972] wlan0: authenticate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:32 mint kernel: [ 734.543542] wlan0: RX authentication from <MY_AP_WAS_HERE> (alg=0 transaction=2 status=0)
Sep 8 05:52:32 mint kernel: [ 734.543550] wlan0: authenticated
Sep 8 05:52:32 mint kernel: [ 734.543554] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:32 mint kernel: [ 734.547530] wlan0: authentication frame received from <MY_AP_WAS_HERE>, but not in authenticate state - ignored
Sep 8 05:52:32 mint kernel: [ 734.742166] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:33 mint kernel: [ 734.941945] wlan0: associate with AP <MY_AP_WAS_HERE>
Sep 8 05:52:33 mint kernel: [ 735.141697] wlan0: association with AP <MY_AP_WAS_HERE> timed out

silencestone · 11-08-2008, 04:45 AM

Okay, this info is from the installed OS, Linux Mint 5.0, an Ubuntu derivative. It has a 2.6.24-16-generic kernel; the whole line from dmesg is:

Quote:

2.6.24-16-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008 (Ubuntu 2.6.24-16.30-generic)

The network interfaces as listed in lshw(the command was 'lshw -C network'):

Code:

  *-network DISABLED
       description: Ethernet interface
       product: 88E8038 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 14
       serial: 00:e0:b8:c4:28:f9
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.20 firmware=N/A latency=0 link=yes module=sky2 multicast=yes port=twisted pair
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:c0:a8:d3:a8:0f
       capabilities: ethernet physical wireless
       configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

It just so happens that the internal wireless interface is on a USB controller, so here it is in lsusb:

Code:

Bus 005 Device 003: ID 0bda:8187 Realtek Semiconductor Corp.

The rest of the laptop hardware as recognized in lspci:

Code:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
03:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
03:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
03:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)

greeeenchap · 11-08-2008, 09:11 AM

hello,

same problem on unbuntu 8.10.

I first thought it was my madwifi driver but same problem on my wifi0 interface.

"unknown hardware address type 801"

ubuntu problem ?

thx,
greeeechap

silencestone · 11-14-2008, 01:04 PM

I'm not sure about that "wmaster unknown..." part, but I've had the same bewildering difficulty with this laptop on Mandriva, Sabayon, and Wolvix, so I can't single out Ubuntu. Don't know what the problem could be, but I'd like to investigate the way driver loads upon recognizing my wifi card, the interface configuration, and the particulars of my network configuration. Any general pointers on how to do any of this would be great.

Surely the "wmaster0 unknown..." message has some significance, some bearing on this. I feel like I perform all the correct steps for getting the wireless interface up and configured, and it goes through the motions of scanning, finding the correct network, authenticating. Then association fails. And I do the whole thing over again.

silencestone · 11-14-2008, 03:42 PM

Nevermind. I'm online right now with the same laptop at an unsecured public wifi hotspot. I was unable to get on my home network even unsecured. At this point, full blame is on my router--it's old and needs replacing, anyway.

BTW, when connecting at the wifi hotspot, the "wmaster unknown..." message appears, but the connection still succeeds. Here's what happens after bringing up the interface (wlan0), scanning for a network, configuring wlan0 in iwconfig:

Code:

me@laptop ~ $ sudo dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:c0:a8:d3:a8:0f
Sending on   LPF/wlan0/00:c0:a8:d3:a8:0f
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 192.168.160.209 from 192.168.160.1
DHCPREQUEST of 192.168.160.209 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.160.209 from 192.168.160.1
bound to 192.168.160.209 -- renewal in 266 seconds.

david_north · 12-06-2008, 01:46 PM

After getting the latest kernel release, 2.6.27.8 (out since yesterday), for the first time ever my rtl8187b is detected without having to get funny drivers and patches. I can't connect to my home network either. I get the same

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

and the DHCPDISCOVER repeats itself over and over again on higher and higher intervals.
Some help please, I think my problem is with DHCP.

silencestone · 12-21-2008, 07:43 PM

Quote:

Originally Posted by david_north

After getting the latest kernel release, 2.6.27.8 (out since yesterday), for the first time ever my rtl8187b is detected without having to get funny drivers and patches. I can't connect to my home network either. I get the same

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on LPF/wlan0/xx:xx:xx:xx:xx:xx
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

and the DHCPDISCOVER repeats itself over and over again on higher and higher intervals.
Some help please, I think my problem is with DHCP.

Unfortunately, I haven't solved this problem--not with that NIC on my home router. My router's an old one, 2Wire Homeportal 1000SW, a combo DSL modem/router/wireless router; it's only capable of WEP encryptions. I wonder, what router are you attempting to connect to?

kalyansundhar · 12-28-2008, 05:15 AM

I use wireless internet on my Ubuntu 8.10 laptop. I too see 'wlan0' and 'wmaster0', when I do ifconfig. Also there are messages "dhclient: wmaster0: unknown hardware address type 801" in syslog.

But I don't have any issue connecting to internet. When I did a google search, I found the following.

"Lets clarify device names first. Regularly you should only see two new device names:

* wmaster0
* wlan0

The wmaster0 device is what we call the master device. The master device is an internal master device used only by mac80211. It should be ignored by users. If possible we will try to hide it from users later."

Please visit http://linuxwireless.org/en/users/Download and have a look at "Known issues" section for the above detail.

Looks like wmaster0 is not something to worry about.

- Kalyan

silencestone · 12-31-2008, 07:11 PM

Well, somebody did something somewhere. I just booted the Linux Mint 6 liveCD (Ubuntu 8.10 based), and the wireless worked without trouble on the same laptop and home portal. Many thanks to all developers. Also, thanks to all repliers for dealing with my stabs in the dark here. I spent a lot of time booting into various distro's, configuring the wireless network, and scanning through dmesg, messages, syslog, and anything else for funny things that I couldn't immediately explain, looking for the point at which things went wrong, and how to eliminate that. I learned some new things, but failed to fix the problem through these efforts.

@kalyansundhar: I see what you mean; even now with the connection working, that message is in the syslog. Did I mention how clueless I was?