WiFi - Not connecting to access point

[lmart]

Juanito
Thanks. FYI, TC on usb uses extlinux. Appended syslog to file /boot/extlinux/extlinux.conf.


DEFAULT core
LABEL core
KERNEL /boot/vmlinuz
APPEND initrd=/boot/core.gz quiet  waitusb=5:UUID="2ae0196d-ad7f-43fd-bae2-e303759a07da" tce=UUID="2ae0196d-ad7f-43fd-bae2-e303759a07da" syslog

[Juanito]

I guess (without checking) that the "prompt 1" is what causes it to pause - this would allow you to add boot codes by entering:

core syslog
core base norestore (useful to check things and run e2fsck)
core etc, etc

[lmart]

well ... unusual things seem to be happening

attached is the messages file (copied immediately after boot) and, output from my script attempting to walk through a manual wifi setup
as you will see, didn't get far

thoughts?

[tinypoodle]

Use a root terminal for wifi/net commands.

[lmart]

indeed, forgot the sudo in front of each command, thus the "Newbie" under my username

[lmart]

Manual WiFi Setup
sudo iwconfig eth1
sudo iwconfig eth1 essid 398VC
sudo iwconfig eth1 enc wepkey
sudo iwconfig eth1 key wepkey
sudo iwconfig eth1 commit (error for wireless request "commit changes" (8B00): operation not supported)
sudo pkill udhcpc
sudo udhcpc -i eth1 would sometimes give an error, but then connect

entered these commands manually, several times throughout the day. entered ping google.com and received an acknowledgement from the site

?Next Steps? If these commands work, why do you suppose the tcp wifi script did not work
FYI, roberts suggested using sudo -s with the above commands. However, sudo -s either did not work or I used it incorrectly

[coreplayer2]

Either I'm confused or your pc is confused..   

eth1 ??  this means there is an eth0 hiding somewhere trying to confuse the whole deal, right?  besides, I thought all wifi was automatically declared as wlan0 etc etc

[Juanito]

However, sudo -s either did not work or I used it incorrectly

If you enter "sudo su" <cr> the terminal will switch from user to root to save you having to enter "sudo" before every command.

eth1 ??  this means there is an eth0 hiding somewhere trying to confuse the whole deal, right?  besides, I thought all wifi was automatically declared as wlan0 etc etc

In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting

[coreplayer2]

interesting,  is that (eth1) a result of the wifi card firmware or udev rules?

[gerald_clark]

The name is compiled into the driver.

[tinypoodle]

Either I'm confused or your pc is confused..   

eth1 ??  this means there is an eth0 hiding somewhere trying to confuse the whole deal, right?  besides, I thought all wifi was automatically declared as wlan0 etc etc

Not really hiding, most likely presence of an ethernet card.
I happened to remove my ethernet card recently, and since then my radio instead of eth1 has eth0 assigned.

[lmart]

If you enter "sudo su" <cr> the terminal will switch from user to root to save you having to enter "sudo" before every command.

Thanks Juanito

In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting

iwconfig lists my ethernet card as eth0
will try ps aux | grep udhcpc and report back

Thanks everyone for sticking with me.

[lmart]

"ps aux | grep udhcpc"
    see attachment

udhcpc appears to be the most fragile part in the process
    it either connects, now with the constant error message, see attached
    or, it keeps sending discoveries and, I have to CTRL-C to exit, then start all over again


?What are my Next Steps?

[Juanito]

Code: [Select]

# ps aux | grep udhcpc
 2668 root     grep udhcpc
That means there's no other instance of udhcpc running, which is a good thing.

I guess the next step could be to try something slightly different - for example:

Code: [Select]

sudo iwconfig eth1 essid "ssid"
sudo iwconfig eth1 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE [replace with your wep key]
sudo udhcpc -b -i eth1 -x hostname:box -p /var/run/udhcpc.eth1.pid

[tinypoodle]

In fact many wifi cards use eth1 - it's worth entering "ps aux | grep udhcpc" to check if udhcpc is trying to connect a wired ethernet adapter eth0, I've found this sometime seems to prevent wifi from connecting

Might be a good idea to use boot code "nodhcp" when planning to use wireless net.