You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2021. It is now read-only.
after messing up a lot with Hostapd & the like I've to say that I really like your very convenient script, but I'm experiencing a problem that, no matter how much I try, I'm not managing to solve
I'm on a raspberry PI with Jessie with two wifi cards and I've with three adaptors: eth0, wlan0 (I want this to be my AP) and wlan1.
I've assigned a static IP to wlan0 as suggested in many hostapd tutorials. When I run create_ap everything works fine if I'm connecting wlan0 to eth0, the AP is created, I can connect with my laptop and surf the web with traffic going trough eth0.
If I try exactly the same command replacing eth0 with wlan1 I can stilll connect but there isno internet access. Please note that wlan1 is correctly connected to another router and the PI has internet connectivity.
I've tried to unplug eth0 in case some strange internal service was disabling forwarding to wlan1 if eth0 was up and running but no success.
I'm really stuck. Anyone experience this before? Anything I have to do?
Thanks for your help.
Franco
EDIT:
Some additional info, in case it helps. I've created the access point with:
wlan1 is connected to a local wifi. Interestingly if I connect my windows pc to my newly created access point (the ip I get assigned is 192.168.12.62), I can succesfully ping any computer that is in the same network as wlan1 ( for instance I can succesfully ping 192.168.1.16) so some routing seem to be in place, but for some reason I cannot ping computers that are on the internet (for example 95.110.194.204).
I don't have enough experience with routing to solve this myself, I'm afraid...
Edit2:
ok, I've found a work around, so I can now connect both trough eth0 and wlan0. But the last problem is the WPA2 authentication. No matter what I try but the only way to connect to the AP is to use no authentication at all. As soon as I specify a password no pc of phone can connect. Very weird.
The text was updated successfully, but these errors were encountered:
Dear all,
after messing up a lot with Hostapd & the like I've to say that I really like your very convenient script, but I'm experiencing a problem that, no matter how much I try, I'm not managing to solve
I'm on a raspberry PI with Jessie with two wifi cards and I've with three adaptors: eth0, wlan0 (I want this to be my AP) and wlan1.
I've assigned a static IP to wlan0 as suggested in many hostapd tutorials. When I run create_ap everything works fine if I'm connecting wlan0 to eth0, the AP is created, I can connect with my laptop and surf the web with traffic going trough eth0.
If I try exactly the same command replacing eth0 with wlan1 I can stilll connect but there isno internet access. Please note that wlan1 is correctly connected to another router and the PI has internet connectivity.
I've tried to unplug eth0 in case some strange internal service was disabling forwarding to wlan1 if eth0 was up and running but no success.
I'm really stuck. Anyone experience this before? Anything I have to do?
Thanks for your help.
Franco
EDIT:
Some additional info, in case it helps. I've created the access point with:
create_ap --driver rtl871xdrv wlan0 wlan1 MyAccessPoint
wlan1 is connected to a local wifi. Interestingly if I connect my windows pc to my newly created access point (the ip I get assigned is 192.168.12.62), I can succesfully ping any computer that is in the same network as wlan1 ( for instance I can succesfully ping 192.168.1.16) so some routing seem to be in place, but for some reason I cannot ping computers that are on the internet (for example 95.110.194.204).
I don't have enough experience with routing to solve this myself, I'm afraid...
Edit2:
ok, I've found a work around, so I can now connect both trough eth0 and wlan0. But the last problem is the WPA2 authentication. No matter what I try but the only way to connect to the AP is to use no authentication at all. As soon as I specify a password no pc of phone can connect. Very weird.
The text was updated successfully, but these errors were encountered: