Sent from my phone.
On Oct 22, 2009, at 9:00 PM, Dan McGhee <[email protected]> wrote:
Reimundo Heluani wrote:
I think he means you need to authenticate to an AP before running
dhcp on that interface. Something like iwconfig eth0 essid any for
example
But I might have fallen in the lazyness of replying without reading
the whole thing
<snip>
Thanks, Reimundo. If what you say is true, I have done that on both
of my devices. This is what's so frustrating. Since I can't connect
with either device, the problem lies in something common to the both
of them. There are only a limited number of options: kernel
configuration, configuration files and bootscripts.
From you previous email it sounds like you're tryng to configure your
scripts to connect at boottime, but have you succesfully connected
manually on this CLFS?
R.
I have compared the configuration file--/etc/dhclient.conf--and the
bootscripts to those in my other laptop and they are identical. That
leaves the kernel and I just don't see what's wrong there either.
I'm hoping that someone can see another avenue to explore.
Dan
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org
