WiFi - Not connecting to access point

[lmart]

tinypoodle

thanks, the commands used are from http://wiki.tinycorelinux.net/wiki:setting_up_wifi

will try your recommendations shortly, to confirm

iwconfig ${wlan} commit remove this line
pkill udhcpc
udhcpc -i ${wlan}

Yes | No?


another question, you seem to be in the know on thing 'core', I wanted to download leafpad, there are 2 files a .tcz and a locale file.  what is the locale file and should I download it?

[tinypoodle]

Looks ok, though there is no necessity to remove "commit", just that error output could be disregarded.

For a new unrelated question please open a new thread in adequate subforum

[lmart]

roberts,Juanito and, tinypoodle

success, me thinks ... will download a browser and know for sure
thank you for your help!


here's the sequence of events
#1) wrote a small script an incorporated the changed tinypoodle suggested. Script follows.
#2) modified Juanito's code to capture the script output ($ sudo /usr/local/bin/wifi.sh auto 2>&1 > /tmp/wifi.log) The following message appeared on the screen but not in the log file: route: SIOCDELRT: No such process.
#3) This 'success' gives rise to many questions. Why didn't the original wifi script work on my system. What is unique about my system? Where should I place my script to run on boot? etc ...

my script
#!/bin/sh
# chmod +x filename.sh
# Example usage:
#    sudo sh filename.sh
#    sudo ./filename.sh
# source: http://wiki.tinycorelinux.net/wiki:setting_up_wifi
#sh-4.1# chmod +x /mnt/sdb1/mywifi.sh
#sh-4.1# ls -al /mnt/sdb1/mywifi.sh
#-rwxr-xr-x 1 root root 401 2012-07-18 19:36 /mnt/sdb1/mywifi.sh



wlan=eth1
essid=398VC
wepkey=

iwconfig ${wlan}
iwconfig ${wlan} essid ${essid}
iwconfig ${wlan} enc ${wepkey}
iwconfig ${wlan} key ${wepkey}
#iwconfig ${wlan} commit ; changed per tinypoodle
pkill udhcpc
#udhcpc -H box -b -i ${wlan} ; changed per tinypoodle
udhcpc -i ${wlan}
#
iwconfig ${wlan}

[Juanito]

udhcpc -H box -b -i ${wlan}
  option -h NAME is deprecated, use -x hostname:NAME

You can use:

Code: [Select]

udhcpc -b -i ${wlan} -x hostname:box -p /var/run/udhcpc.{wlan}.pid

route: SIOCDELRT: No such process.

I think you can ignore this.

Where should I place my script to run on boot? etc ...

place the script in /opt and then call it from /opt/bootlocal.sh

[lmart]

Juanito
thanks for your help
will try your suggestions and let you know

learned a couple of things along the way, thanks for staying with me on this challenge

[lmart]

well ...

yesterday the script worked, today it doesn't
it appears to make it to udhcpc -i ${wlan} and it just keeps sending discovery notices until I control-c out of the script

recommendations?

[gerald_clark]

udhcoc cannot get an IP address if you are not associated with an access point.
Use iwconfig to troubleshoot the connection.
Make sure the transmitter is on.

[lmart]

gerald_clark

thanks for your reply
from the script above, which command(s) associate with my access point?
the transmitter is on

having a hard time understanding why the original wifi script doesn't work and, the above script works then doesn't work
not quite sure how to troubleshoot to provide help to you folks

download another linux 2 days ago, wifi works flawlessly, is there anything I can cull from that distro to help me with tc+?

[tinypoodle]

Boot with code "syslog".
In an aterm do "tail -f /var/log/messages"
Then configure wireless step by step while always having an eye on output from syslog to get feedback
IMHO it is futile to use a script until connecting manually step by step works reliably.

[lmart]

tinypoodle

IMHO it is futile to use a script until connecting manually step by step works reliably.

agree! worked through wifi setup  manually, then used the script
will try your recommendations, then let you know

? will the script command capture all output to the terminal so I can post ?

[Juanito]

will the script command capture all output to the terminal so I can post

Yes

[lmart]

Boot with code "syslog".
In an aterm do "tail -f /var/log/messages"
Then configure wireless step by step while always having an eye on output from syslog to get feedback
IMHO it is futile to use a script until connecting manually step by step works reliably.

how do i get the usb to boot with code "syslog"?

[Rich]

Hi hitsware
When you get to the boot prompt (the screen with the F2, F3, or F4 message) enter:

Code: [Select]

tc syslog

[lmart]

On usb, Syslinux message, then it launches boot sequences immediately. No boot prompt.
Is there a boot sh where I can insert the option?

[Juanito]

There should be a file named boot/syslinux/syslinux.conf or syslinux.cfg or something like that, which should look something like this:

Code: [Select]

display boot.msg
default core

label core
kernel /boot/vmlinuz
append initrd=/boot/core.gz quiet noswap tce=UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3 waitusb=10:UUID=aaab6273-4a6c-4118-8eb2-e31a9b31edb3 host=boxdell text

implicit 0
prompt 1
timeout 300
F1 boot.msg
F2 f2
F3 f3
F4 f4

add "syslog" somewhere on the line analogous to "append initrd=/boot/core.gz" or you can type something like "core syslog" delending on what label your conf file uses.