1 |
Todd Goodman <tsg@×××××××××.net> [15-07-28 19:48]: |
2 |
> * Meino.Cramer@×××.de <Meino.Cramer@×××.de> [150728 13:25]: |
3 |
> > Todd Goodman <tsg@×××××××××.net> [15-07-28 19:08]: |
4 |
> > > * Meino.Cramer@×××.de <Meino.Cramer@×××.de> [150728 11:28]: |
5 |
> > > [..SNIP..] |
6 |
> > > > Hi Todd, |
7 |
> > > > |
8 |
> > > > thanks for your help! :) |
9 |
> > > > |
10 |
> > > > I will to adjust the config file and see what will happen... |
11 |
> > > > Dont worry about the password...it is a fake one. If everything is |
12 |
> > > > running fine, if will choose a more random one. |
13 |
> > > > |
14 |
> > > > By the way...While tumbling down the google hole ;) I came across |
15 |
> > > > "hostapd" which exactly seems to be build for the purpose I want: An access point. |
16 |
> > > > |
17 |
> > > > BUT: |
18 |
> > > > I could not decide, what tutorial is correct: |
19 |
> > > > Do I still need wpa_supplicant with hostapd or |
20 |
> > > > Don't I neeed wpa_supplicant? |
21 |
> > > > |
22 |
> > > > Thank you very much in advance for any help! |
23 |
> > > > Best regards, |
24 |
> > > > Meino |
25 |
> > > |
26 |
> > > Hi Meino, |
27 |
> > > |
28 |
> > > I don't think you need wpa_supplicant if you're using hostapd (unless |
29 |
> > > you need to also connect to a WAP in additional to being a WAP |
30 |
> > > yourself, and in that case I don't know if it requires a different |
31 |
> > > interface to do that.) |
32 |
> > > |
33 |
> > > I think wpa_supplicant is a supplicant (i.e., client only) component. |
34 |
> > > |
35 |
> > > But I could be wrong and hopefully someone else will chime in with more |
36 |
> > > hostapd experience than I have. |
37 |
> > > |
38 |
> > > Regards, |
39 |
> > > |
40 |
> > > Todd |
41 |
> > > |
42 |
> > |
43 |
> > Hi, |
44 |
> > |
45 |
> > Slowly but surely I got a lot of ants in my head...or it feels like. |
46 |
> > There are SO MANY tutorial out there and every doc says something |
47 |
> > different. |
48 |
> > |
49 |
> > No I got this: |
50 |
> > |
51 |
> > >rfkill list |
52 |
> > 1: phy1: Wireless LAN |
53 |
> > Soft blocked: yes |
54 |
> > Hard blocked: no |
55 |
> > |
56 |
> > Damn! This is the by far the most complicated thing which came across |
57 |
> > my way with linux... |
58 |
> > |
59 |
> > |
60 |
> > Best regards, |
61 |
> > Meino |
62 |
> > |
63 |
> > |
64 |
> |
65 |
> Hi Meino, |
66 |
> |
67 |
> Since it's soft blocked I think you need an: |
68 |
> |
69 |
> rfkill unblock wifi |
70 |
> |
71 |
> But I haven't had to worry about rfkill before so might have it wrong. |
72 |
> |
73 |
> Todd |
74 |
> |
75 |
|
76 |
|
77 |
Hi Todd, |
78 |
|
79 |
I unblocked with rfkill and I am a step further: |
80 |
The SSID is shown on my tablet together with a |
81 |
boobastic signal strength (no wonder: distance is below 30 cm...;) |
82 |
BUT: No connect...: |
83 |
|
84 |
I start hostapd by hand since wpa_supplicant seems to be hardcoded |
85 |
somewhere... |
86 |
|
87 |
Now I got this (stderr of hostapd) |
88 |
|
89 |
wlan0: interface state COUNTRY_UPDATE->ENABLED |
90 |
wlan0: AP-ENABLED |
91 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: authenticated |
92 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: associated (aid 1) |
93 |
wlan0: AP-STA-CONNECTED ac:9e:17:e7:c7:bd |
94 |
wlan0: STA ac:9e:17:e7:c7:bd RADIUS: starting accounting session 55B7C32D-00000000 |
95 |
wlan0: STA ac:9e:17:e7:c7:bd WPA: pairwise key handshake completed (RSN) |
96 |
wlan0: AP-STA-DISCONNECTED ac:9e:17:e7:c7:bd |
97 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: disassociated |
98 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) |
99 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: authenticated |
100 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: associated (aid 1) |
101 |
wlan0: AP-STA-CONNECTED ac:9e:17:e7:c7:bd |
102 |
wlan0: STA ac:9e:17:e7:c7:bd RADIUS: starting accounting session 55B7C32D-00000001 |
103 |
wlan0: STA ac:9e:17:e7:c7:bd WPA: pairwise key handshake completed (RSN) |
104 |
wlan0: AP-STA-DISCONNECTED ac:9e:17:e7:c7:bd |
105 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: disassociated |
106 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) |
107 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: authenticated |
108 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: associated (aid 1) |
109 |
wlan0: AP-STA-CONNECTED ac:9e:17:e7:c7:bd |
110 |
wlan0: STA ac:9e:17:e7:c7:bd RADIUS: starting accounting session 55B7C32D-00000002 |
111 |
wlan0: STA ac:9e:17:e7:c7:bd WPA: pairwise key handshake completed (RSN) |
112 |
wlan0: AP-STA-DISCONNECTED ac:9e:17:e7:c7:bd |
113 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: disassociated |
114 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) |
115 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: authenticated |
116 |
wlan0: STA ac:9e:17:e7:c7:bd IEEE 802.11: associated (aid 1) |
117 |
wlan0: AP-STA-CONNECTED ac:9e:17:e7:c7:bd |
118 |
wlan0: STA ac:9e:17:e7:c7:bd RADIUS: starting accounting session 55B7C32D-00000003 |
119 |
wlan0: STA ac:9e:17:e7:c7:bd WPA: pairwise key handshake completed (RSN) |
120 |
|
121 |
What's happening here...? |
122 |
|
123 |
I am sure, it is a layer 8 failure.... ;) |
124 |
(me) |
125 |
|
126 |
Best regards, |
127 |
Meino |