alfa awus036h slackware current dhcpcd wont connect
 

Hi im wondering where the problem might be

slackware-current kernel 2.6.35.10-smp

for instance if i just want to connect to wep ap

i done
i read somwhere that its not working good with slackware 13.1 can you please clarify? and if theres something else to configure please
thanks

Well, first you need to make sure of the current module. what is you chipset? Provide lsmod, lspci, iwconfig output.

BTW, WEP is not very useful. Is there a reason why you want to use WEP? It's flawed by design and cannot be secured. All it does is slow down an attacker and discourage passers-by from connecting. You should consider buying a better router if yours does not support WPA.

I concur. WEP can be hacked in seconds these days. WPA2-AES is what I use at home with a Netgear WNDR3700. This router I highly recommend.

I confess, I use Slackware as my router. :) An Atheros ath5k NIC and hostapd(8) built from a newer version variant of http://slackbuilds.org/repository/13.1/network/hostapd/ .

Sweet. But do you have 2.4GHz and 5 GHz dual band with separate ssids, with extra guest ssid outside the firewall? PLUS, NAS capability and 4 port gigbit router?

Sorry, matters, I am drifting OT - been one of those days. Do post again and we will try to help.

everything works, the signal was low, im now connected through it and it works perfectly. thanks

dhcpcd wlan0 timed out
 

I have the same problem, slackware 13.1 doesn't works with dhcpcd. I've searched
for weeks about some solution without results. I updated dhcpcd but it sends me the
same message. I installed wicd with the last two versions and they send the message
"bad password". I'm going to come back to my previous version of slackware. It's a
shame because I like the new one. I hope developers solve the bug soon.

There is probably no bug, but if there is, it probably has nothing to do with dhcpcd. You have to be methodical and scientific if you hope to solve problems like this. Saying it doesn't work and calling it a "bug" accomplishes nothing. (Nothing positive, that is.)

First look at the device and its driver; read about possible issues at their linuxwireless.org pages. Check your iwconfig(8) output. Is it associated with the access point?

wicd is just a frontend. It's a nice one to have for wireless with WEP/WPA, but when there are problems, you still have to look behind it to see what's going on.

To make to work to connect to others AP one must do

before connecting with wicd on access point of their choice, some time 5.5M works aswell with that you can use current kernel and can connect without getting disconnected . hopefully the patch will be provided any time soon, if you still dont like it just reverse to 2.6.29.6 kernel untill patch will be provided.