[TAG] LG 127 Wifi

[Benjamin A. Okopnik]

On Fri, Aug 11, 2006 at 07:40:20PM +0100, Martin Hooper wrote:
> On 11/08/2006 Benjamin A. Okopnik wrote:
> > > Aug  6 14:49:14 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 6
> > > > Aug  6 14:49:20 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 12
> > > > Aug  6 14:49:32 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 11
> > > > Aug  6 14:49:43 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 21
> > > > Aug  6 14:50:04 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 7
> > > > Aug  6 14:50:11 localhost dhclient: DHCPDISCOVER on wlan0 to 
> > 255.255.255.255 port 67 interval 4
> > > > Aug  6 14:50:15 localhost dhclient: No DHCPOFFERS received.
> > > > Aug  6 14:50:15 localhost dhclient: No working leases in 
> > persistent database - sleeping.
> > 
> > This looks like 'dhclient' is doing all the right things - but your 
> > card
> > isn't "hearing" any responses. This could be because 1) it's not
> > actually sending anything out - but I doubt that, since you do connect
> > in a secured-channel scenarion - or 2) because it's not "hearing" any
> > DHCP "offers". I'm guessing that it's the latter. There are, in fact,
> > two places where it can fail: the router may not get the broadcast 
> > DHCP
> > requests that are being sent out by your card, or your card may not be
> > picking up those offers.
> 
> Port 67 firewalled?

[blink] It's a good thought - I'll admit that I missed considering that
perspective - but I think not.

``
ben at Fenrir:~$ grep '\<67/' /etc/services
bootps          67/tcp                          # BOOTP server
bootps          67/udp
''

If the querent was trying to boot his machine via BOOTP (i.e., if it was
a thin client or something like that), I'd agree that it would be a
show stopper. As it is, it's worth checking out of curiosity, but I
can't see it preventing DHCP negotiation.


* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://linuxgazette.net *