Need an Introduction to Tiny Core? Or peruse Core Concepts.
udhcpc appears to be the most fragile part in the process it either connects, now with the constant error message, see attached
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
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
Quote from: Juanito on July 22, 2012, 11:28:16 PMIn 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 connectingMight be a good idea to use boot code "nodhcp" when planning to use wireless net.
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