Easy Way: wicd

[floppy]

my recommendation:
- again: kill the dhcp process or bootcode NODHCP; the cable disconnected is not enough
- go for ndiswrapper (perhaps you achieve something very quick)
- when your wife sleep, make nightshifts for moving to a linux driver (as per current try)
I know the pressure for making running a PC in a family..
Honestly, if your wife is benchmarking the laptop of her girlfriends, which are apple or weandooze, then forget linux: any few issue coming up with linux later (with openoffice.. text or format lost by exchanging files with weandooze..), will be massiv because the benchmark will come up immediatly "it runs at my girlfriend laptop". Girls dont have in my opinion such patience as boys for technical things running differently or a bit unstable. Sorry girls.. (but my wife has much more patience for learning a video-recorder command than me.. here I dont have any second of patience for a stupid engineer wanted me to learn how to use a complicated video setup).

[floppy]

adopt a puppy

I made it with Puppy on my old box, too !
But I achieved TCL, later (it tooks me.. >1 month..)
So, mister, I achieved a bit more than you..;-) ... (just to see if you are a sportsman)
Now: I use a LAN adapter for electricity network. So, I am hardwired via my electricity network which is 200% better than WLAN. Weandooze? oh no.. this is like you are hungry and you go to MacDonalds instead of having a "Steack Frites" at a nice french restaurant in Brittany (where you get a glas of house wine with it). terrible decision..

[Lee]

Thanks a bunch guys.  I've got that stupid tune stuck in my brain now.  And when It comes to whistling, I've been told I couldn't carry a tune in a bucket! 

[Juanito]

#?unsure what following 3 commands accomplish
sudo modprobe lib80211_crypt_tkip
sudo modprobe lib80211_crypt_wep
sudo modprobe lib80211_crypt_ccmp

These kernel modules deal with wifi encryption - strictly speaking you only need lib80211_crypt_wep, but you might as well load them all.

[tinypoodle]

Without looking into details at this moment, do not use (Security mode) "restricted", as it works with Security mode:open.
(That was my suspicion since 14 posts ago...)

[floppy]

juanito & tinypoodle, thanks for sticking with me

ok, spent the weekend culling through wifi stuff
here's what's on my plate for this evening, would appreciate your review/questions/comments

in shell script format, however, will run all commands manually from the cli

#variables - network specific
#essid (text), wepkey (hex 00:00:00:00:00:00:00:00:00:00)
wlan=eth1
essid=
wepkey=

#detect wifi device, load the applicable driver, will load manually as tce-load did not work
#tce-load -i pci-utils.tcz
#tce-load -i ip...

first "pkill udhcpc"
then the whole stuff

[floppy]

why not using wpa_supplicant, with WEP, too?
Anyhow, WPA is much better than WEP, so perhaps it would run with WPA?

[tinypoodle]

why not using wpa_supplicant, with WEP, too?
Anyhow, WPA is much better than WEP, so perhaps it would run with WPA?

Why not? 
Because complicating things before the basics work somehow - i.e. achieving a connection with simple means - does not help at all!

And no, if taking the approach of changing router settings, WPA would not help with troubleshooting when it does not work with WEP - turning off encryption entirely could make sense.

If you do not understand, please read all posts of the thread in order.

[tinypoodle]

Next thing to achieve would be "seeing" your AP with

Code: [Select]

iwlist eth1 sunder TC, the same way as you can see it under puppy.

[tinypoodle]

???at this point, is there any reason to keep typing the commands manually as opposed to a script???

Yes of course, scripting doesn't make sense before you have managed to get a functional connection manually.

[floppy]

perhaps you need the wpa_supplicant?

wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf

with wpa_supplicant.conf (from ubuntu page http://wiki.ubuntuusers.de/wlan/wpa_supplicant  ; see in the forum here too)

==============
network={
        ssid="Netzwerkname"
        scan_ssid=1
        key_mgmt=NONE
        wep_tx_keyidx=0
        wep_key0="Netzwerkschlüssel"
}
==============

[curaga]

It is possible your router does not like the busybox udhcpc. You can try one of the other dhcp clients in the repo (isc-dhcp).

[Rich]

Hi lmart

while trying to reduce the variables, changing dhcp would add one to the mix ...

Actually you would be replacing one variable with another to try to either confirm or eliminate it as
a possible source of your problems. If nothing changes you can always go back to the original dhcp.

[floppy]

floppy; appreciate your help, you are staying the course on wpa and, you may be correct, i know nothing about wpa, w/ Puppy all i do in enter my wep and it works so if wpa is at play, it must be in the background ... as promised, will try your recommendation after i exhaust the current course,

the name is wpa_supplicant.
the parameters inside were for wep.
But you can use wpa2.. (tinypoodle would like it, too.. ;-).
You will get it.. it took me 1 month..

wpa_supplicant: here http://wiki.tinycorelinux.net/wiki:setting_up_wifi  or here http://hostap.epitest.fi/wpa_supplicant/

[tinypoodle]

perhaps you need the wpa_supplicant?

wpa_supplicant -B -Dwext -ieth1 -c/etc/wpa_supplicant.conf

with wpa_supplicant.conf (from ubuntu page http://wiki.ubuntuusers.de/wlan/wpa_supplicant  ; see in the forum here too)

==============
network={
        ssid="Netzwerkname"
        scan_ssid=1
        key_mgmt=NONE
        wep_tx_keyidx=0
        wep_key0="Netzwerkschlüssel"
}
==============

Have you even read Reply #62??
Have you read all the 67(!!) preceeding posts of this thread in correct order?