search

lukicdarkoo / rpi-wifi

Configures simultaneous AP and Managed Mode Wifi on Raspberry Pi
GNU General Public License v3.0
532 stars 120 forks source link

Access the RPI from the WLAN0 not possible #10

Open dop0qob opened 4 years ago

dop0qob commented 4 years ago

Hi, I dont know exactly how this happens but there is a point when it is no longer possible to reach the raspberry thru the WLAN0 ip address when connected to the same WIFI Router. But it is possible to connect thru the RPI AP and, once inside, its also possible to reach any destination behind the WLAN0 (Internet included).

Its like if there is a firewall blocking incoming connections from the WLAN0.

But it was working before... I manually changed the details of the /etc/wpa_supplicant/wpa_suppliant.conf but don't think that is the issue.. because it is correctly connected to the Router and the RPI can access the network behind the WLAN0.

what could be happening?

Kind regards.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/83635992-access-the-rpi-from-the-wlan0-not-possible?utm_campaign=plugin&utm_content=tracker%2F97445956&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F97445956&utm_medium=issues&utm_source=github).
Carl-jackslabs commented 4 years ago

Same issue for me, (Thanks for a nice clean script btw! )

I can't SSH through the home router but when connected to the AP SSH is fine.

In addition, I am not able to access internet through the AP, I get a name resolution error so maybe something is not bridged correctly.

FYI, Raspbian 3B+ Buster September

Edit: Actually, it might be an issue because my home router ssid has spaces and punctuation in it. It may not be connected to the router at all, explaining basically everything. Posting my potential (stupid) error here in case it affects you @dop0qob too

Edit2: Confirmed that was it. I was unable to enter the "!" and " " in the bash script even with quotes so I used the "\" which didn't work. So I SSH'd into via AP and changed the wpa_supplicant.conf to the correct name manually. Good bridge and stability is great. For reference, the SSID in question was "FRITZ!Box 4040 EP" , a default for a common model router in Switzerland and Germany as far as I know

Edit3: Single quotes worked instead of double quotes. For some dumb reason I thought double would be a stronger assertion than single quotes. Wrong!

lukicdarkoo commented 4 years ago

@Carl-jackslabs Nice catch! The script should be updated accordingly.

Just to confirm, single quotes in /etc/wpa_supplicant/wpa_supplicant.conf work fine? With double quotes, it doesn't work? Are you sure that the script arguments are passed correctly - that you used quotes when executing the script?