At least you now know the problem is in the wireless layer, and not (necessarily!) dhcp. Once you get rid of the dreaded 00:00:00:00:00:00, you're there.
I'd suggest temporarily removing all security from your ap, and getting everything working, then upping to WEP, and so on. TBH, I only use WEP at home - not too many bigtime bandwidth thieves in Diamond Harbour (: Please note that these suggestions are from practical experience, and there may well be configurations of AP that will never broadcast their mac address for all I know - I've just never seen them. Steve On Wed, 26 Jul 2006 09:16:54 +1200 Roger Searle <[EMAIL PROTECTED]> wrote: > No, it does not. I have now tried getting on the work wireless ap and > have experienced the same outcome... > > > Steve Holdoway wrote: > > Does iwconfig ath0 show a mac address for the access point??? If not, then > > it's a problem at the wireless level. > > > > Steve > > > > On Tue, 25 Jul 2006 20:25:46 +1200 > > Roger Searle <[EMAIL PROTECTED]> wrote: > > > > > >> Nick Rout wrote: > >> > >>> On Tue, 25 Jul 2006 19:34:03 +1200 (NZST) > >>> Roger Searle <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > >>>> I have a functional wireless card now, but when the card goes looking > >>>> for the > >>>> router no dhcpoffer is received by the card. > >>>> > >>>> [EMAIL PROTECTED]:~$ sudo ifup ath0 > >>>> Internet Systems Consortium DHCP Client V3.0.3 > >>>> Copyright 2004-2005 Internet Systems Consortium. > >>>> All rights reserved. > >>>> For info, please visit http://www.isc.org/products/DHCP > >>>> > >>>> Listening on LPF/ath0/00:13:46:74:9a:d0 > >>>> Sending on LPF/ath0/00:13:46:74:9a:d0 > >>>> Sending on Socket/fallback > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 7 > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12 > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16 > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9 > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 13 > >>>> DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4 > >>>> No DHCPOFFERS received. > >>>> No working leases in persistent database - sleeping. > >>>> > >>>> I have set the router so that it is NOT filtering by MAC address, it is > >>>> WPA > >>>> pre-shared key, and I have checked there is a match with the channel, > >>>> ssid and > >>>> password from /etc/network/interfaces: > >>>> > >>>> auto lo > >>>> iface lo inet loopback > >>>> > >>>> auto eth0 > >>>> iface eth0 inet dhcp > >>>> > >>>> auto eth1 > >>>> iface eth1 inet dhcp > >>>> > >>>> auto eth2 > >>>> iface eth2 inet dhcp > >>>> > >>>> auto ath0 > >>>> iface ath0 inet dhcp > >>>> pre-up /sbin/iwpriv ath0 mode 0 > >>>> pre-up /sbin/iwconfig ath0 essid rnsRouter channel 10 key abcde12345 > >>>> > >>>> auto wlan0 > >>>> iface wlan0 inet dhcp > >>>> > >>>> Anyone have any suggestions what I could do? > >>>> > >>>> Cheers, > >>>> Roger > >>>> > >>>> > >>>> > >>> consult with don > >>> > >>> > >> i'll pass, prefering to have on-topic discussions... > >> > >>> no, seriously now, turn off wpa and see if it works. if it does at that > >>> point, the trouble is your wpa setup. > >>> > >>> > >> unsuccessful. though to be honest i'm guessing a little about the > >> corresponding changes that are needed in the interfaces file. I've > >> tried no change, just removing the "key abcde12345" part, and altering > >> to "essid any". all fail. i have turned off all security related > >> options I can find on the router (it's a linksys wag54g if that's > >> helpful... ) and still same result. > >> > >> tomorrow i can try getting it going on the work router which is a > >> different model (and will need different settings in the interfaces file > >> of course). will be good to see how that goes if i get no further tonight. > >> > >> > >> > >> > >> > > > > > >
