1 |
Todd Goodman <tsg@×××××××××.net> [15-07-28 19:08]: |
2 |
> * Meino.Cramer@×××.de <Meino.Cramer@×××.de> [150728 11:28]: |
3 |
> [..SNIP..] |
4 |
> > Hi Todd, |
5 |
> > |
6 |
> > thanks for your help! :) |
7 |
> > |
8 |
> > I will to adjust the config file and see what will happen... |
9 |
> > Dont worry about the password...it is a fake one. If everything is |
10 |
> > running fine, if will choose a more random one. |
11 |
> > |
12 |
> > By the way...While tumbling down the google hole ;) I came across |
13 |
> > "hostapd" which exactly seems to be build for the purpose I want: An access point. |
14 |
> > |
15 |
> > BUT: |
16 |
> > I could not decide, what tutorial is correct: |
17 |
> > Do I still need wpa_supplicant with hostapd or |
18 |
> > Don't I neeed wpa_supplicant? |
19 |
> > |
20 |
> > Thank you very much in advance for any help! |
21 |
> > Best regards, |
22 |
> > Meino |
23 |
> |
24 |
> Hi Meino, |
25 |
> |
26 |
> I don't think you need wpa_supplicant if you're using hostapd (unless |
27 |
> you need to also connect to a WAP in additional to being a WAP |
28 |
> yourself, and in that case I don't know if it requires a different |
29 |
> interface to do that.) |
30 |
> |
31 |
> I think wpa_supplicant is a supplicant (i.e., client only) component. |
32 |
> |
33 |
> But I could be wrong and hopefully someone else will chime in with more |
34 |
> hostapd experience than I have. |
35 |
> |
36 |
> Regards, |
37 |
> |
38 |
> Todd |
39 |
> |
40 |
|
41 |
Hi, |
42 |
|
43 |
Slowly but surely I got a lot of ants in my head...or it feels like. |
44 |
There are SO MANY tutorial out there and every doc says something |
45 |
different. |
46 |
|
47 |
No I got this: |
48 |
|
49 |
>rfkill list |
50 |
1: phy1: Wireless LAN |
51 |
Soft blocked: yes |
52 |
Hard blocked: no |
53 |
|
54 |
Damn! This is the by far the most complicated thing which came across |
55 |
my way with linux... |
56 |
|
57 |
|
58 |
Best regards, |
59 |
Meino |