Wifi @ Nashua Library?

[Neil Joseph Schelly]

I've been on public networks before where I can't get a DHCP response, while 
Windows users don't have a problem.  I've never come up with a thorough 
explanation and it's rare enough for me that I've never really investigated.

I'd install tcpdump and see if you can see the network addresses in use.  
Then, you can try guessing at a number that's open and see how it works for 
you.  It's worked for me, though not recommended for friendliness to whoever 
uses that IP of course.
-Neil

On Wednesday 26 August 2009 04:18:09 pm Ben Scott wrote:
> On Wed, Aug 26, 2009 at 3:49 PM, Marc Nozell (marc at nozell.com)
>
> <nozell at gmail.com> wrote:
> > I see in the logs that dhclient isn't getting a lease ...
>
>   Well, if DHCP isn't getting a lease, you're not getting an IP
> address, which means the problem isn't some sort of walled
> garden/captive portal thing -- those all need IP to work.
>
>   I'm guessing a link layer problem.  Perhaps compatibility between
> your wireless NIC and the access point.  Look for newer
> drivers/firmware for your card.  Possibly explore options to tweak
> things like data rate.  iwconfig exposes some of that stuff.
>
> > It looks like NetworkManager is hardcoded to only wait 45s before timing
> > out.
>
>   Really, if you haven't gotten a DHCP lease within 45 seconds, you're
> almost certainly not going to.  It normally happens in seconds.
>
> -- Ben
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/