Re: [MLUG] linksys WAP/router dhcp problems...

[Jonathan King <EMAIL:PROTECTED>]

On Sun, 1 Sep 2002, Mikhail Kovalenko wrote:

> Jonathan King wrote:
> > OK, so I have one of those great Linksys BEFW11S4 units (wireless access 
> > point/router + 4 port switch).  Everything used to work just fine: the 
> > machines in the house got IP addresses via dhcp from the Linksys, and 
> > everything was good.  Recently, I upgraded one of them (an iBook) to OS X 
> > 10.2 (although I'm not sure that's important in solving the problem).  
> > Now, whenever I try to connect wirelessly (or by plugging in directly to 
> > the router), I cannot get my address via DHCP; instead the Mac 
> > not-so-cleverly self-assigns a bogus 169.254.whatever address.  I presume 
> > this means that it could not get a real IP via DHCP from the router.  
> 
> Check under Preferences > Networking options to make sure the upgrade 
> didn't change IP addressing from DHCP to bootp or something else.

Yes, I did check that. Many times.  One important piece of info I left
out last time was that I did test to see whether the iBook would work with
other wireless networks, and it did just fine.  (Specifically, I, er, 
"war-walked" across the quad and picked up a connection from a WEP-less 
WAP whose name was "tsunami" (Cisco default?).  So I figured it had to be
something either in my connection to a linksys in particular changed by 
10.2 (a different time-out for dhcp assignment?), some issue with the 
router itself, or some weirdness being propogated to me from mediacom.

> > Frustratingly, it can *see* the router just fine (I can ping the router's 
> > address just fine).
> 
> That doesn't sound right. Is your router on 169.254 subnet too?

No, it advertises a 192.168.xxx.xxx address on the inside, but picks up
an (I believe) 10.whatever address via dhcp from Mediacom.

Now, the good news this morning was that my wife's un-upgraded iBook took
a 169.bogus address this morning, presumably when its lease from the 
linksys on its previous IP expired.  Since nothing had changed on that
machine at all, I was confident that it must be the linksys somehow 
getting confused (although this had never happened before).  So I 
power-cycled that, and, voila!  Joy was restored.  Of course, I'd still 
like to know what *it's* problem was, but the immediate emergency has 
passed.

Now, I would have power-cycled the linksys before (and done other stuff
too) except the one thing worse than my notebook not getting a DHCP
address would be everybody else in the household getting hosed on top of
that.

jking

 

--
To unsubscribe, go to http://mlug.missouri.edu/members/edit.php

Archives are available at http://mlug.missouri.edu/list-archives/