Re: ath not setting media type?

From: Niki Denev <nike_d_at_cytexbg.com>
Date: Wed, 19 Oct 2005 12:32:15 +0300
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sam Leffler wrote:
> 
> I still haven't seen you say what os version you're running or what
> ifconfig ath0 shows.  Here is what I see when devd runs at boot on my t42.
> 
> Processing event '+ath0 vendor=0x168c device=0x1014 subvendor=0x17ab
> subdevice=0
> x8331 class=0x020000 at slot=2 function=0 vendor=0x168c device=0x1014
> subvendor=
> 0x17ab subdevice=0x8331 class=0x020000 on pci2'
> Pushing table
> setting device-name=ath0
> setting vendor=0x168c
> setting device=0x1014
> setting subvendor=0x17ab
> setting subdevice=0x8331
> setting class=0x020000
> Processing attach event
> Testing device-name=ath0 against ^ed50
> Testing device-name=ath0 against ^ukbd0
> Testing device-name=ath0 against ^ums[0-9]+
> Testing media type of ath0 against 0x20
> ath0 has media type 0x80
> Testing media type of ath0 against 0x80
> ath0 has media type 0x80
> Executing '/etc/pccard_ether ath0 start'
> 
> The machine is running a recent vintage of current.
> 
> If you don't see the interface name then devd cannot query the media
> type so you won't match based on media type.
> 

I'm running about week old 7.0-CURRENT.

ifconfig ath0 shows:
ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::205:4eff:fe4f:7beb%ath0 prefixlen 64 scopeid 0x2
        ether 00:05:4e:xx:xx:xx
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
        ssid "" channel 1
        authmode OPEN privacy OFF txpowmax 34 protmode CTS bintval 100

when booting with devd_flags="-D" i get:

Processing event '+ath0 vendor=0x168c device=0x1014 subvendor=0x17ab
subdevice=0x8331 class=0x020000 at slot=2 function=0 vendor=0x168c
device=0x1014 subvendor=0x17ab subdevice=0x8331 class=0x020000 on pci2'
Pushing table
setting device-name=ath0
setting vendor=0x168c
setting device=0x1014
setting subvendor=0x17ab
setting subdevice=0x8331
setting class=0x020000
Processing attach event
Testing device-name=ath0 against ^ed50
Testing device-name=ath0 against ^ukbd0
Testing device-name=ath0 against ^ums[0-9]+
Testing device-name=ath0 against ^ubt[0-9]
Testing media type of ath0 against 0x20
ath0 has media type 0x80
Testing media type of ath0 against 0x80
ath0 has media type 0x80
Executing '/etc/pccard_ether ath0 start'
Popping table

my devd.conf is the default with added section for usb bluetooth
devices (ubt[0-9]) (which executes /etc/rc.bluetooth start $device)

So, devd sees the device name properly. And the media type is correctly
set. (sorry for blaming ath(4) due to my ignorance)
But the problem i have is with the notify events for LINK_UP/DOWN,
the attach/detach events seems to be processed properly.

Here is what i got when i kill wpa_supplicant and dhclient,
bring ath0 down, then start devd in debug mode and then
associate to my AP manually with wpa_supplicant

Processing event '!system=IFNET subsystem=ath0 type=LINK_UP'
Pushing table
setting system=IFNET
setting subsystem=ath0
setting type=LINK_UP
Processing notify event
Testing system=IFNET against ^ACPI
Testing system=IFNET against ^ACPI
Testing system=IFNET against ^IFNET
Testing type=LINK_UP against ^LINK_UP
Testing media type of  against 0x20
Testing system=IFNET against ^IFNET
Testing type=LINK_UP against ^LINK_UP
Testing media type of  against 0x80
Popping table

and if i comment media-type "802.11"; in the notify event section in
devd.conf :

Processing event '!system=IFNET subsystem=ath0 type=LINK_UP'
Pushing table
setting system=IFNET
setting subsystem=ath0
setting type=LINK_UP
Processing notify event
Testing system=IFNET against ^ACPI
Testing system=IFNET against ^ACPI
Testing system=IFNET against ^IFNET
Testing type=LINK_UP against ^LINK_UP
Testing media type of  against 0x20
Testing system=IFNET against ^IFNET
Testing type=LINK_UP against ^LINK_UP
Executing '/etc/rc.d/dhclient start ath0'
Popping table

in rc.conf i have :
ifconfig_ath0="DHCP WPA"

I can provide any other info that is needed,
and will cvsup and rebuild later today to see if the problem
persists.


- --niki
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDVhKeHNAJ/fLbfrkRAnr4AKCGqWG+9DqPBp90mVujaE6BfZDKWACcCEF9
Mnxx2dnz2ZBhoBSc7Jv1nAU=
=plny
-----END PGP SIGNATURE-----
Received on Wed Oct 19 2005 - 07:31:14 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC