Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Forcing AirPort to lengthen DHCP searches' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Forcing AirPort to lengthen DHCP searches
Authored by: Spencerian on Feb 12, '03 03:49:00PM

I've been using these lease control commands (which did appear in an earlier hint) to try to make an AirPort card in my PowerBook G4 1GHz obtain a DHCP lease from a third-party wireless hub (A Lucent AeroNet, I believe). On AirPort, I get the dreaded 169.254.x.x self-assigned address. On another PowerBook, before the company went to a hidden network, I used AirPort just fine.

Using ifconfig commands to release DHCP to try to get a real address on my company net does no good. Normal DHCP leasing over our 100Mb Ethernet works fine. Other Windows clients use things just fine. Apple's info on this matter did little good. We use WEP, and, with the key in place, AirPort does pick up the existence of the network (it's hidden) and the wireless admin does see my card and MAC address.

Some thoughts: I think AirPort is too impatient to find a DHCP server. I think it spends too little time searching, and gives up too early, therefore giving the 169.254 default self-assigned address.

Is there a UNIX command to force a network interface (in this case, the interface for AirPort) to wait longer while searching for a DHCP server?

[ Reply to This | # ]