Indiestory

[Log in to get rid of this advertisement]

Im running slackware 11, with a broadcom bcm4318 airport extreme2 card, got that running no bother

Im pretty sure ive got wpa set up through editing /etc/rc.d/rc.inet1.conf, not too sure if ive got that right ,but thats not the problem at the moment.

With other distros(debian and based) up until now its been a case of cutting the firmware, bringing up the device and running dhclient. All works until dhclient, turns out that no devices are configured by default. Fair enough, I think im going to need some help setting this little file up. The man page shed a little light on this but i have no idea whats needed. Cheers for any help, much appreciated

comprookie2000

I would use dhcpcd
Find out the interface
ifconfig
lets say it is eth1
ifconfig eth1 up
dhcpcd eth1
ifconfig
And see if you have an eth1 interface with an IP

Indiestory

just tried it, and got nothing. Is there normally alot of output from dhcpcd? because i invoke it and it seems to hang for a couple of minutes, and then kicks me out with eth0(wireless interface) put down. Am i missing something i should have set up else where

Quakeboy02

If wpa_supplicant isn't configured properly, you are simply not going to get an IP from dhclient or dhcpcd. Could you post the output from both iwconfig and ifconfig? Also, what method did you use to generate the wpa_supplicant.conf file?

2Gnu

There's not usually an output from dhcpcd. If it works, it will respond pretty quickly. If it goes on for a while (default timeout for Slack is 60 seconds), it's not working.

You won't be able to get an IP address until you've successfully associated with the AP and, if it has security enabled, authenticated.

Post the output of iwconfig <interface_name> to see if you're getting that far. Try it with no security enabled to eliminate variables.

Then, run wpa_supplicant in the foreground, with debug on instead of from inet1. That way, you can see if it's working and, if not, why not.

Indiestory

my wpa_supplicant.conf file is the default that came with my wpa_supplicant.tgz

i whipped out my other config file because it seemed to be interfering so i reverted to a backup.

ive got the inter face set up with
as it is that seems okay i can find my network with iwlist eth0 scan.
im running wpa with the example from the man page
it seems to be finding my network ( i see a received bytes from interface style message, so i think that it is) , but then it comes up with some messages about being unable to associate an AP with network. My wpa_supplicant is set up with my network and with an open one. Right now my network is completely open. Could someone maybe translate my problem for me

Quakeboy02

Since you have "key off" then you don't need to run wpa_supplicant. You don't have either WEP or WPA configured on your router, right? All you should need to do is "ifconfig eth0 up" and then "dhclient eth0" to get an ip. "dhcpcd" or "dhclient" both will print our your ip as the response. They both take 10-20 seconds to work.

2Gnu

With no modifications? Have you entered your SSID, WPA type, etc.? If not, I wouldn't expect it to work.
You're running it in background mode (B) but with extra verbosity (d), which isn't going to help you unless you look at the log. Try running in foreground. You're also not calling out a driver. Try Dwext or Dbcm43xx.

Indiestory

no ive got an open connection setting with wpa as well as secured so it should use that if theres no secure network. Its the default file ,but i have my ssid and psk set. Wpa's not set up on my router at the moment.

I wasnt running it in the back ground ,but with -d option, could someone point me at the logs. Not at home right now will try later tonight

2Gnu

Take out the -B option and run wpa_supplicant separately to see what's happening. Send the output to a file to make it easier to review or post.

First, though, back to my earlier suggestion: Let's see if you're getting to first base with the unsecured WLAN. Post the output of iwconfig for the wireless interface. If it's not associated, try manually setting the wireless parameters with iwconfig and pulling an IP address. Post any errors.

Once you confirm you have basic connectivity, then move onto WPA.

Indiestory

sorry wasnt running wpa in the background, the first line of the output was an error message about the broadcom driver. Im gonna try ( and keep trying) to build a newer kernel Thanks for the help

2Gnu

Why build a new kernel? Why will you not post details, answer questions or take suggestions? I can only help if you want help.

Good luck.

basileus

Kernel rebuild will not probably help, unless your wireless card's drivers are really new. The problem is most likely in wpa_supplicant.conf - "man wpa_supplicant.conf" might help.

wildar

2Gnu is right, kernel rebuild aint gonna fix it. Step 1 is to try without protection. Cause if you can't connect with it wide open then its like trying to unlock a door that is nailed shut.

Indiestory

2Gnu sorry if i seem to be ignoring your suggestions its that i have been doing these things anyway.
Can you explain about pulling an ip address not sure what you mean by that.

heres basically what im doing, i pulled out the udev rule that was associating the network cards, seemed to be throwing out errors.

checked with iwconfig and everything seems right.

sits there for a minute then throws me back to the prompt, ifconfig only comes up with lo, if i put eth1 back up, im unable to find any networks until i remove the module. That was my reasoning for a newer kernel. sorry if i dont seem to take advice, im either already doing it and posting sloppily or just not understanding