1 |
----- Original Message ----- |
2 |
|
3 |
> From: Mick <michaelkintzios@×××××.com> |
4 |
> On Tuesday 06 Sep 2011 15:24:33 BRM wrote: |
5 |
>> ----- Original Message ----- |
6 |
>> > From: Mick <michaelkintzios@×××××.com> |
7 |
>> > On Saturday 03 Sep 2011 15:14:27 BRM wrote: |
8 |
>> >> ----- Original Message ----- |
9 |
>> > I think the above should be either: |
10 |
>> > |
11 |
>> > ctrl_interface=/var/run/wpa_supplicant |
12 |
>> > ctrl_interface_group=wheel |
13 |
>> > |
14 |
>> > or, |
15 |
>> > |
16 |
>> > DIR=/var/run/wpa_supplicant GROUP=wheel |
17 |
>> |
18 |
>> Ok. Corrected that to the first one. |
19 |
> |
20 |
> Fine. I note that you said the wpa_gui won't scan further down this thread, |
21 |
> |
22 |
> just in case ... is your user part of the wheel group? |
23 |
|
24 |
Yes, so I can use sudo. |
25 |
|
26 |
>> >> #ctrl_interface_group=wheel |
27 |
>> >> ap_scan=1 |
28 |
>> >> fast_reauth=1 |
29 |
>> >> # This blank configuration will automatically use DHCP for any |
30 |
> net.* |
31 |
>> >> # scripts in /etc/init.d. To create a more complete |
32 |
> configuration, |
33 |
>> >> # please review /etc/conf.d/net.example and save your |
34 |
> configuration |
35 |
>> >> # in /etc/conf.d/net (this file :]!). |
36 |
>> >> |
37 |
>> >> # Standard Network: |
38 |
>> >> config_eth0=( "dhcp" ) |
39 |
>> > |
40 |
>> > The old syntax you use here, which was ( "value" ) is now |
41 |
> deprecated. |
42 |
>> > You |
43 |
>> > should replace all such entries by removing the brackets, e.g. the |
44 |
> above |
45 |
>> > becomes: |
46 |
>> > |
47 |
>> > config_eth0="dhcp" |
48 |
>> > |
49 |
>> > This is explained in: |
50 |
> http://www.gentoo.org/doc/en/openrc-migration.xml |
51 |
>> |
52 |
>> Corrected that one too. eth0 was working fine though. |
53 |
> |
54 |
> Yes, because eth0 will default to dhcp, after the old syntax you were using |
55 |
> errors out or is ignored. |
56 |
|
57 |
Ok. |
58 |
|
59 |
>> > modules="wpa_supplicant" |
60 |
>> > wpa_supplicant_wlan0="-Dwext" |
61 |
>> > config_wlan0="dhcp" |
62 |
>> |
63 |
>> I re-enabled those and added the last line. |
64 |
> |
65 |
> OK, wpa_supplicant should now work as intended. |
66 |
> |
67 |
> |
68 |
>> > You need to add or uncomment the following to your |
69 |
> wpa_supplicant.conf: |
70 |
>> > ===================== |
71 |
>> > network={ |
72 |
>> > key_mgmt=NONE |
73 |
>> > priority=0 |
74 |
>> > } |
75 |
>> > ===================== |
76 |
>> > The above will let latch on the first available AP. |
77 |
>> |
78 |
>> I wasn't sure that that one was for. I've re-enabled it and the |
79 |
> original |
80 |
>> one for my network. |
81 |
> |
82 |
> OK, this is useful for open AP which accept connections. If they need |
83 |
> encryption you can add this using the wpa_gui. |
84 |
|
85 |
Interesting. Good to know. Thanks! |
86 |
|
87 |
>> > Also, you can then add any AP of preference with passphrases and what |
88 |
>> > not: ===================== |
89 |
>> > # Home Network |
90 |
>> > network={ |
91 |
>> > ssid="MY-NETWORK" |
92 |
>> > # key_mgmt=IEEE8021X <--You don't need these entries |
93 |
> here, unless |
94 |
>> > # eap=TLS <--you run SSL certs for authentication |
95 |
>> > wep_key0=DEADBEAF0123456789ABCDEF000 |
96 |
>> > priority=1 |
97 |
>> > auth_alg=OPEN |
98 |
>> > } |
99 |
>> > ===================== |
100 |
>> |
101 |
>> Interestingly, wpa_supplicant complains if those two lines are not there |
102 |
>> even though I am not doing SSL auth. |
103 |
> |
104 |
> Hmm ... what is the error/warning that comes up? |
105 |
|
106 |
I'll have to check after I get home. |
107 |
|
108 |
> Either way, can you please add: |
109 |
> |
110 |
> eapol_version=1 |
111 |
|
112 |
Will do this evening. |
113 |
|
114 |
>> I'd rather use the NetworkManager in KDE than wpa_gui. |
115 |
>> That said, NetworkManager in KDE seems to be using wicd for some reason. |
116 |
> You need someone else to chime in here, because I use neither of these. As |
117 |
> far as I read in this M/L wicd is more or less fool-proof. |
118 |
>> I also have KDE running under Kubuntu on my work computer (4.6.2) and the |
119 |
>> Network Manager is completely different (don't know why) - it's not |
120 |
> wicd |
121 |
>> as far as I can tell. |
122 |
>> |
123 |
>> However, They are still not working. wpa_gui refuses to scan and find |
124 |
>> networks; while wicd is not finding networks either - but there's so |
125 |
>> little information in the GUI that it is practically useless to say why. |
126 |
>> Perhaps I've got something at the KDE layer screwed up? |
127 |
> I don't know if one is causing a clash with the other, so don't try to |
128 |
> use |
129 |
> both at the same time. If wicd is started automatically when you boot/login, |
130 |
> then just use that. |
131 |
|
132 |
Well, I figured this part out. Essentially, I had wpa_supplicant, and wicd installed. |
133 |
However, what I really wanted to NetworkManager and KNetworkManager installed. |
134 |
So I removed wicd, and installed NetworkManager and KNetworkManager. |
135 |
I now get the interface I expected under KDE and don't need to use wpa_gui any more. |
136 |
Still, it doesn't scan. |
137 |
|
138 |
> When wpa_gui refuses to scan what message do you get? What do the logs say. |
139 |
> Also, if wpa_gui or wicd fail to scan for APs what do you get from: |
140 |
> # iwlist wlan0 scanning |
141 |
|
142 |
At least from the applications I am not getting any error messages. I'll have to check the logs tonight and let you know. |
143 |
|
144 |
This morning I checked the antennae to verify they were properly connected to the mini-PCI card (as I had opened it up a few weeks ago to see whether it was mini-PCI or mini-PCIe; but I didn't remove/disconnect anything at that time). Everything checked out. So it shouldn't be a hardware issue unless the card is completely fried for some reason. |
145 |
|
146 |
I'll check the logs this evening and let you know. |
147 |
|
148 |
Thanks! |
149 |
|
150 |
Ben |