WPA setup via bash

[mudba]

hello,

I'm trying to connect to a wireless network. I'm currently running xfre and I'm able to find the network and connect to it through the GUI, but I want connect to it via the bash promt to automate the setup during a kickstart boot.

I've done the following

wpa_passphrase mysid mypassword >/wpa.conf


wpa_supplicant -K -Dwext -i wlan0 -c /wpa.conf

I get the following over and over again

Tring to assoiate to MAC (SSID:'mysid' freq=2412MHZ)
Associated with MAC
CTRL-EVENT-DISCONNECTED basssid=MAC reason=0

What am I donig wrong?

[smr54]

If the network is hidden, you have to add scan_ssid=1 to wpa.conf

I have a page on this at http://home.roadrunner.com/~computer.../wireless.html that covers, among other things, trying to set up wpa manually.

It may also just be the card is one of those that doesn't work that well in Linux.

[mudba]

I followed your steps and I got the same exact problem.

==============
Trying to Asssoiate with 00:14:6c:a:d7:7c (SSID='MYWIRELESS' freq=2412 Mhz)
Associated with 99:14:6c:ac:d7:7c
CTRL-EVENT-DISCONNECTED bssid=00:14:6:ac:d7:7c reason=0
==============

from XFRE:
if I go upto the top and click the upper right corner of the screen and click the network icon I see my wireless network and I select it. I'm then prompted the the password which I enter. It then connects me without issue.

iwconfig results before connected:
wlan0 IEEE 802.11bgn essid:off/any
mode:managed frequency 2.412GHZ access point: not associated
tx-power=14 dBm
retry long limit:7 res thr:off fragment thr:off
encrpytion key:off
power management: on

iwconfig after connecting with gui
wlan0 IEEE 802.11bgn essid:"mynetwork"
mode:managed frequency 2.412GHZ access point: 00:14:6c:ac:d7:7c
bit rate=54 Mb/s TxPower=27 dBm
tx-power=14 dBm
retry long limit:7 rts thr:off fragment thr:off
encrpytion key:off
power management: on
link quality=70/70 signal level=-30dBM
rx invalid nwid:0 rx invlaid crypt:0 rx invalid frag:0
tx exessive retries:0 invalid misc:15: missed beacon:0

[sea]

Your commands seem right, howver, no spaces between argument-commands and the according value.
Example "-iwlan0" not "-i wlan0".
Further, you might want to try the -B (background)-

---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------

Your commands seem right, howver, no spaces between argument-commands and the according value.
Example "-iwlan0" not "-i wlan0".
Further, you might want to try the -B (background)-

[smr54]

Interesting. I haven't run into that--where the GUI tool works and wpa doesn't. One thing I would mention--if you are logging in graphically, that is if X is running, I would make sure that there are no other network tools running, that is, NetworkManager or whatever XFCE uses. In other words, making sure it's disabled in services, then rebooting.

Actually, I have run into that, in the old Acer Aspire One, they were loading essential wireless card modules with one of the X startup scripts. That's about the only other thing I can think of.

I don't know how much work you feel like putting into this, but the things I would try are first, to boot in text mode and see if it worked any better if X isn't running. (Also, do lscpi and get the model of the card, then google that and see if there are known issues--or if some module has to be loaded, because then it is possible that Fedora or XFCE does it that way, and does it through some X startup scripts. At any rate, google the card listing, as returned by lspci and see if there are known issues.

I'd also try it with another flavor of Linux to see if you have the same problem. Again, it depends how much work you feel like putting into it.

---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------

@sea, spaces or no space hasn't seemed to make a difference in my experience with wpa_supplicant. I'm not saying you're incorrect, just that it hasn't been an issue when I've accidentally put them in--things still worked. It's quite possible that I've simply been lucky.

[mudba]

Got it. THe problem was NetworkManager running.

Now my new problem is that I'm building a kickstart file for this so I need to script up everything up to happen during the ks install. I have to figure out how to disable networkmanager in the kickstart file

[AndrewSerk]

Originally Posted by mudba

Got it. THe problem was NetworkManager running.

Now my new problem is that I'm building a kickstart file for this so I need to script up everything up to happen during the ks install. I have to figure out how to disable networkmanager in the kickstart file

Hi,
That can usually be done with something like this above the repo line:

services --enabled=network --disabled=NetworkManagerk,sshd

Hope this helps,