ath(4) major update

[Sepherosa Ziehau]

On 2/5/07, Ja'far Railton <ibn.richard at gmail.com> wrote:
I am pleased to report an improvement with this patch. I used the
example from the DF handbook - there isn't any access point available yet.
Do you mean ath(4) does not associate?

~ > sudo ifconfig ath0 inet 192.168.0.20 netmask 255.255.255.0 ssid \
my_net
This configure means your AP is not using any protection (e.g. WEP, WPA ...)

What's the output of:
ifconfig ath0 up scan
Please refer to following link for an up-to-date wireless
configuration guidance:
http://leaf.dragonflybsd.org/~sephe/sam_wireless.html
Note, the WPA rc script part in the above document does not apply to
dfly.  I will be more than happy if someone can make it work :)
ath0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
IFF_RUNNING was not turned on.  Have you seen any of following
messages in your /var/log/messages or on you console when you
configured your ath(4):
"unable to reset hardware; hal status X"
"unable to start recv logic"
        inet6 fe80::20d:88ff:fe82:96d%ath0 prefixlen 64 scopeid 0x4
        inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255
        ether 00:0d:88:82:09:6d
        media: IEEE 802.11 Wireless Ethernet autoselect
        status: no carrier
        ssid my_net channel 1
        authmode OPEN privacy OFF txpowmax 100 bmiss 7 protmode CTS burst
Best Regards,
sephe
--
Live Free or Die