Hi, I just noticed that what you do is somewhat similar to DNAv4 [1][2]. Would not it be better to separate DHCP and movement detection to separate modules? So others than DHCP could use the decision of the movement detection too. And by the way, there is also ongoing work on DNAv6 to detect network attachment in IPv6 [3].
Regards, Gabor [1] http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-18.txt [2] http://www.drizzle.com/~aboba/DNA/ [3] http://www1.ietf.org/html.charters/dna-charter.html On Monday 27 February 2006 01:07, you wrote: > > In 802.11 networks when connecting to a new AP on the same networks > > (same SSID & security settings) you typically don't have to do DHCP > > again - but with some networks setups you do. In order to detect this, > > when connecting to a new AP always issue an ARP request for the default > > gateway - if you don't get a response, then kick off a dhcp request. > > I've just implemented the feature. As the client does not know the specific > wireless settings, I've chosen this approach to verify the IP address: > > -downtime must be lower than 60 seconds > -T1 (RENEWal time) has not passed yet > -IP address of default gateway is ARP probed and must answer with the known > MAC address of the default gateway. Maximum 3 (is configurable) tries with .5 > sec delay. > > If any of this fails, the client tries to verify the IP address via DHCP for > four seconds, then drops IP configuration and restarts if it is NAKed or not > answered. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
