[NCLUG] setting up wireless to use dns
Daniel Herrington
daniel at iherr.com
Mon Jul 30 00:03:19 MDT 2007
Just an update...
In the end I decided to replace the 2GB CF flash card with a 5GB CF
hard drive and load a full 4.0r0 debian installation including glibc
and real binaries instead of uclibc/busybox. It's been a real bear
getting the kernel to behave -- I needed to use 2.6.20.?? since that
was the version that the usb wireless card driver was written for
(the at76c503a-source package). I think 2.6.20.15 may finally be
working now... I haven't had any "kernel oops" messages during the
last two days on it like I did on some other versions of 2.6.20 and
2.6.22. I can successfully load the wireless lan driver and dhclient
and then ping/wget with real host names with no name resolving problems.
Thanks for all the help. I agree that the effort to deal with uclibc
and busybox just isn't worth it with storage being so cheap nowadays.
Daniel
On Jul 21, 2007, at 10:07 AM, Benson Chow wrote:
> Boo. uclibc. heh.
>
> I recall having similar issues of not being able to resolve
> hostnames that I was never able to 'resolve' (sorry, bad pun) on my
> Zaurus. I don't know if you're seeing the same problem.
>
> To test to see whether or not you're seeing the same issue (but
> does not provide a solution), try:
>
> while true; do
> telnet www.google.com 80
> done
>
> and let it hammer that host (which won't succeed to actually hammer
> google because the first time it is actually successful it will
> block.) The symptom I see with my Zaurus is that it _will_
> eventually resolve after a couple hundred attempts!
>
> Why, I never figured out. I stopped futzing with the Zaurus after
> being quite unsatisfied with how OpenZaurus (and I assume Angstrom
> too) is not even trying to keep everything within the limited
> capacity of the Zaurus SL-5600 (specificially, the 32MB RAM. They
> were virtually forcing Poodle users to use swap - swap to what?
> Flash?). But I digress, perhaps someone has some clues about the
> delayed resolve issue?
>
> On my "embedded" ia32 machine, I ended up deciding to just use
> glibc. While it's nice to be small with uclibc, since I had enough
> space on the CF card, it wasn't worth the effort to deal with the
> library
> incompatibilities with the glibc on the development host...
>
> -bc
>
> On Fri, 20 Jul 2007, Daniel Herrington wrote:
>
>> Date: Fri, 20 Jul 2007 19:54:37 -0600
>> From: Daniel Herrington <nclug at iherr.com>
>> Reply-To: Northern Colorado Linux Users Group <nclug at nclug.org>
>> To: Northern Colorado Linux Users Group <nclug at nclug.org>
>> Subject: Re: [NCLUG] setting up wireless to use dns
>> I found Stephen's post in the archives on the nclug website. I
>> don't have tcpdump installed on either machine, so if that might
>> help in debugging, I'll need to install it (and libpcap, I guess).
>>
>> I tried removing the "search Belkin" line from the resolv.conf,
>> but it doesn't appear to change anything.
>>
>> Maybe I should just get rid of uclibc/busybox altogether and use
>> glibc with standard binaries? I'm on version 0.9.23 of uclibc.
>>
>> I guess what's puzzling to me is that everything works fine with
>> eth0, just not with wlan0.
>>
>> Daniel
> _______________________________________________
> NCLUG mailing list NCLUG at nclug.org
>
> To unsubscribe, subscribe, or modify your settings, go to: http://
> www.nclug.org/mailman/listinfo/nclug
More information about the NCLUG
mailing list