On 9/4/05, Adam Papai <[EMAIL PROTECTED]> wrote: > Eric Dillenseger wrote: > > > Just a remark, in /etc/horname.if you don't write the 'up' keyword. > > Otherwise, I don't see what's wrong. Once the card is configured, can > > you post a ifconfig -a output? First, remove hostname.ath?, reboot and > > try to configure only with ifconfig, if there's an error, ifconfig > > should say something. > > > > You can monitor the DHCP requests with tcpdump. > > > > Is the access point filtering mac adresses? > > > > Hi Eric. > > The router don't filter mac-addresses. > > When I attach the card I see this in dmesg: > > ath0 at cardbus0 dev 0 function 0 "Atheros Communications, Inc., > AR5001-0000-0000, Wireless LAN Reference Card": irq 5 > ath0: AR5212 7.9 phy 4.5 rf2112 5.6 rf2112 5.6, NONE, address > 00:11:95:93:eb:53 > > After this I have to set up nwid and mode and media for it. > > # ifconfig ath0 nwid asuka media autoselect mode autoselect chan 1 > # ifconfig ath0 > ath0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:95:93:eb:53 > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid asuka chan 1 > > if I try to set up a static ip then I type: > > # ifconfig ath0 192.168.1.2 > ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:95:93:eb:53 > media: IEEE802.11 autoselect (DS1 mode 11b) > status: no network > ieee80211: nwid asuka chan 1 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::211:95ff:fe93:eb53%ath0 prefixlen 64 scopeid 0x7 > > But the card status is "no network" and I can't ping 192.168.1.1 ( wlan > router ip ). I changed the router mode "B only" so the "G" mode couldn't > be the problem. > > If I set ath0 the way like this: > > #ifconfig ath0 192.168.1.2 mode autoselect mediaopt hostap chan 1 nwid asuka > > #ifconfig ath0 > ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:95:93:eb:53 > media: IEEE802.11 autoselect hostap (autoselect mode 11b hostap) > status: active > ieee80211: nwid asuka chan 1 bssid 00:11:95:93:eb:53 > inet6 fe80::211:95ff:fe93:eb53%ath0 prefixlen 64 scopeid 0x7 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > > Now it's running in host AP mode, but neither kismet nor airsnort sees > it's broadcasted ssid. This is the only case when ifconfig shows me > "status: active". > > In that case, when I try to get ip by typing: "dhclient ath0" after > setting up nwid, chan, mode the result is: > > # ifconfig ath0 mode autoselect chan 1 nwid asuka > > # ifconfig ath0 > > ath0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:95:93:eb:53 > media: IEEE802.11 autoselect > status: no network > ieee80211: nwid asuka chan 1 > # dhclient ath0 > > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 1 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 2 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11 > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 3 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > #ifconfig ath0 > ath0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:95:93:eb:53 > media: IEEE802.11 autoselect (DS1 mode 11b) > status: no network > ieee80211: nwid asuka chan 1 > inet6 fe80::211:95ff:fe93:eb53%ath0 prefixlen 64 scopeid 0x8 > > Yesterday I tried ad-hoc mode ( peer to peer ) between iBook and my > laptop. But they didn't see each other. :/ > > > # uname -a > OpenBSD larva.portable.wooh.hu 3.8 GENERIC#1 i386 > > It seems that I can't get this card to work. > > So I don't have any idea. The AP works well with this card and > Linux/madwifi. > > -- > Adam PAPAI > D i g i t a l Influence > E-mail: [EMAIL PROTECTED] > Phone: +36 30 33-55-735 >
Hello Adam, I must say that I have no other idea. This morning I tried another DWL-G520 and found it wouldn't work. The card is correctly identified, configured with the hostname.if of the other one, but no connection. The only difference I found between the two is the revision and firmware version. I think that D-Link is changing too much things between revisions of cards and the driver don't handle all revisions correctly. My cards have the same chipset, but one is rev B2 and fw 3.1.6 and the other B3/4.2.11. Both are DWL-G520 rebB, not G520+ (wich has a TI chipset). Maybe your card is a bit to newly reviewed by D-Link to be properly supported by the ath(4) driver.
