Easy Way: wicd

[tinypoodle]

I use similar commands every day without "ifconfig eth1 up" and it works every time, but that's not to say it might not be needed in your case  

I suspect that might be driver specific, and for the same reason I refrained to mention a specific order and was also cautious in my choice of words [could not harm != needed].    

[Juanito]

a dmesg before the 8 commands and after the 8 commands are executed should be OK.

[Juanito]

I remembered I had an old toshiba with intel wifi, here's what I get, albeit for wpa2 instead of wep:

Code: [Select]

$ lspci
01:0a.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)

$ sudo cp /mnt/hda2/conf/wpa_jnet_configure.conf /etc/wpa_configure.conf
$ tce-load -i /mnt/hda2/tce_3x/optional/ipw2100_firmware.tcz
$ tce-load -i /mnt/hda2/tce_3x/optional/wireless_tools.tcz
$ tce-load -i /mnt/hda2/tce_3x/optional/wpa_supplicant.tcz
$ sudo modprobe lib80211_crypt_tkip
$ sudo modprobe lib80211_crypt_wep
$ sudo modprobe lib80211_crypt_ccmp
$ sudo iwconfig eth1 essid "jnet"
$ sudo wpa_supplicant -B -Dwext -i eth1 -c/etc/wpa_configure.conf
$ sudo udhcpc -b -i eth1
udhcpc (v1.18.3) started
Sending discover...
Sending select for 192.168.1.112...
Lease of 192.168.1.112 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 195.229.241.222
adding dns 213.42.20.20

$ dmesg | tail -20
...
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11
ipw2100 0000:01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11 (level, low) -> IRQ 11
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
ipw2100 0000:01:0a.0: firmware: requesting ipw2100-1.3.fw
lib80211_crypt: registered algorithm 'TKIP'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP
perhaps you don't have the correct firmware?

[Juanito]

The output from "lspci" - just the line concerning your wireless hardware - would be useful.

Are you sure the firmware was loaded before wireless-2.6.33.3-tinycore.tcz? The dmesg you uploaded seemed to indicate that might not have been the case?

[Juanito]

when you ask if the firmware was loaded, are you referring to JasonW's ipw2200.tcz extension?  if so, that includes wicd?

By firmware, I mean the ipw2200 extension, not wicd.

Could you post the output of "lspci" for your wireless hardware.

[tinypoodle]

small problem, no lspci ...

Install pci-utils 

[Juanito]

OK, so your hardware and driver version are:

Code: [Select]

06:0b.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
So, according to http://ipw2200.sourceforge.net/firmware.php, your firmware choices are:

driver versions v1.1.1 and newer firmware v3.0 , firmware v3.1

Jason provided firmware v3.1 in his ipw2200.tcz extension, so things should work if you have your ssid and wep code entered correctly.

Sorry, but I'm not sure what you could try next..

[tinypoodle]

Post the output of

Code: [Select]

sudo iwconfig&

Code: [Select]

ifconfigright before the udhcpc step
Alter the key of first before posting

[floppy]

my commands (captured via 'script') follow; if this does not help you and you want me to start from a completely fresh frugal install of tinycore, will do; pls advise

after reading the whole efforts of a huge number of hardworkers.. a question: are you communicating here with your box with wired lan?
if this is the case, I would kill the wired lan process before starting the wireless process ( or use the onboot code "nodhcp", or perhaps blacklist the wired ethernet module?.. who knows.. both are from Intel..).

[tinypoodle]

When all works fine in puppy, does iwconfig also show "Security mode:restricted" ?

With

Code: [Select]

sudo iwlist eth1 scan you see your AP?

[Juanito]

The iwconfig command should look like this:

Code: [Select]

sudo iwconfig wlan0 key restricted 54:B0:DB:75:B1:54:0C:A5:D1:89:C3:6B:ED
..i.e. the code should not be enclosed in quotes

also, did you issue the command:

Code: [Select]

sudo modprobe lib80211_crypt_wep..I don't see the results in the dmesg you post above.

[Juanito]

Maybe this is tempting fate, but you could try using the iw extension instead of wireless_tools - I don't think it would be a problem to have both of them loaded at the same time, the commands would then be something like:

Code: [Select]

$ sudo iw eth1 connect ssid keys 1:00112233445566778899AABBCC
$ iw list [to list available devices]
$ iw dev eth1 scan [to look for access points]
$ iw dev eth1 link [to check the link status]

[tinypoodle]

FWIW, I have had both extensions loaded many times and never observed any particular issue about.

[tinypoodle]

Generally  speaking: If there are difficulties with setting up wireless and one has the opportunity it is preferable to turn off encryption entirely until connecting to an open AP works, and only then to look into the encryption part.

[Rich]

Hi lmart
Tell your wife  "It's the thrill of making the trip, getting there is just a bonus.".