On Fri, January 26, 2007 10:40 pm, Gus Wirth wrote:
> Chris Mauricio wrote:
>> Google is not my friend...
>>
>> Recently did a fresh install from FC4 to FC6. I had noticed this issue
>> sporadically in FC4, where dhcp would fail to pick up the gateway every
>> odd
>> router or so.  This issue has become full blown in FC6.
>>
>> I cannot retrieve the GW on any wireless router, but successfully get
>> IP,
>> netmask, DNS.  I have been resorting to manually adding GW via 'route
>> add'
>> but this is a pain in the ass when travelling from starbux to starbux.
>>
>> relevant info:
>>
>> Linux hekate 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686
>> i686
>> i386 GNU/Linux
>>
>> 02:01.0 Network controller: Intel Corporation PRO/Wireless 2200BG
>> Network
>> Connection (rev 05)
>>
>> ipw2200-firmware-3.0-3.src.rpm
>> wireless-tools-28-1.fc6.src.rpm
>> wlassistant-0.5.5-4.fc6.src.rpm
>> dhcp-3.0.5-1.fc6.src.rpm
>>
>> Any help appreciated.
>
> Unfortunately, the problem is probably not in Linux but in the DHCP
> server. I discovered that many DHCP servers (Microsoft, cheap wireless
> access points) are brain dead and take the RFC's as suggestions and not
> as requirements and do not present the gateway in the correct manner.
>
> One way to help troubleshoot would be to see if you can sniff the
> connection, either by running the DHCP client in debug mode or maybe
> with Wireshark (the new name for Ethereal). I had to do that at the
> Installfest at National City Adult School.
>
> Gus
>
>

I suspected as much in Portland. Is there a workaround? I would have added
a GW by hand but didn't know how to detect or guess it.

-- 
Lan Barnes

SCM Analyst              Linux Guy
Tcl/Tk Enthusiast        Biodiesel Brewer


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to