Linksys DHCP behavior
dr
Not really related to Kismet, but good information to get out anyhow.

It would appear that the DHCP server in Linksys routers has some very unusual behavior,
that can lead to seemingly inexplicable failures attempting to get a lease.

Scenario:

A client from another network connects to a linksys configured to hand out addresses in
the 192.168.1.100-150 range.  The client has a DHCP lease from the other network, for
10.10.10.50.  It issues a dhcp request, including its current address in an attempt to regain 
the same IP.  The linksys dhcp server won't give it the same, obviously, so it appears to
do a "best fit":  It offers the same final octet with the new network, 192.168.1.50.  The
typical behavior for the client is to then do another dhcp request to officially request the
IP which it has been assigned.  It does so.  At this point, the Linksys <b>REJECTS</b> the IP, 
because it is not within the range of IPs allowed for DHCP.

Knowing this behavior can go a long way towards explaining the seemingly random connection problems
of "I get a great signal but it won't give me an IP".

The fix, obviously, is to release the old IP before requesting an IP on the linksys network.