1 |
On Sunday 02 Aug 2015 01:50:21 Fernando Rodriguez wrote: |
2 |
> Hello, |
3 |
> |
4 |
> After installing hostapd I can successfully connect to the AP, I can get |
5 |
> DHCP from it, but I cannot access the network through it (neither lan or |
6 |
> internet). |
7 |
|
8 |
This sounds like a (network) routing problem, rather than a hostapd issue. |
9 |
|
10 |
|
11 |
> This is an existing router box so iptables and everything else |
12 |
> is already properly configured. |
13 |
> |
14 |
> I'm using this minimal config: |
15 |
> |
16 |
> interface=wlp0s10 |
17 |
> #driver=nl80211 |
18 |
> hw_mode=g |
19 |
> channel=6 |
20 |
> #ieee80211d=1 |
21 |
> #country_code=FR |
22 |
> #ieee80211n=1 |
23 |
> #wmm_enabled=1 |
24 |
> |
25 |
> ssid=LinuxAP |
26 |
> auth_algs=1 |
27 |
> wpa=2 |
28 |
> wpa_key_mgmt=WPA-PSK |
29 |
> rsn_pairwise=CCMP |
30 |
> wpa_passphrase=hello linux ap |
31 |
> |
32 |
> iw list shows the following supported modes: |
33 |
> * IBSS |
34 |
> * managed |
35 |
> * AP |
36 |
> * AP/VLAN |
37 |
> * monitor |
38 |
> |
39 |
> The ebuild warns that in order for hostapd to work I need to set the card |
40 |
> in master mode (the wiki makes no mention of it). |
41 |
|
42 |
I think this is a matter of nomenclature. Your AP & AP/VLAN would/should be |
43 |
the equivalent to master mode. |
44 |
|
45 |
|
46 |
> But when I try to do |
47 |
> that (either through the net init scripts or through iwconfig) I get the |
48 |
> following error: |
49 |
> |
50 |
> Error for wireless request "Set Mode" (8B06) : |
51 |
> SET failed on device wlp0s10 ; Invalid argument. |
52 |
|
53 |
Did you try setting it up as AP, or AP/VLAN to see if it works? In the latter |
54 |
you will also need to setting a route for the AP VLAN to access the default |
55 |
(V)LAN and Internet. |
56 |
|
57 |
|
58 |
|
59 |
> However after starting hostapd it appears that it was able to set the card |
60 |
> to master mode according to iwconfig: |
61 |
> |
62 |
> wlp0s10 IEEE 802.11bg Mode:Master Tx-Power=20 dBm |
63 |
> Retry short limit:7 RTS thr:off Fragment thr:off |
64 |
> Power Management:off |
65 |
|
66 |
What mode is shown if you use AP or AP/VLAN? |
67 |
|
68 |
|
69 |
> So, is this card supported or not? Will I be able to connect and get dhcp |
70 |
> from the server if it didn't? |
71 |
|
72 |
I believe that your card is supported for hostapd use, or otherwise you would |
73 |
not be able to get a dhcp address from the server. |
74 |
|
75 |
|
76 |
> Avahi also _sortof_ works. If I add the wifi |
77 |
> card to the deny-interfaces list on avahi-daemon.conf and try to ping the |
78 |
> AP using the avahi name the avahi daemon (on the AP) logs the following: |
79 |
> |
80 |
> Received packet from invalid interface. |
81 |
> |
82 |
> |
83 |
> This is the output of rc-service hostapd start: |
84 |
> |
85 |
> Configuration file: /etc/hostapd/hostapd.conf |
86 |
> Using interface wlp0s10 with hwaddr 00:14:a5:cb:4d:8a and ssid "LinuxAP" |
87 |
> wlp0s10: interface state UNINITIALIZED->ENABLED |
88 |
> wlp0s10: AP-ENABLED [ ok ] |
89 |
> |
90 |
> |
91 |
> Any suggestions? |
92 |
|
93 |
Check that your routing is set up to allow connections from your client IP |
94 |
through the network of the AP. |
95 |
|
96 |
-- |
97 |
Regards, |
98 |
Mick |