Raspberry Pi wireless Access Point: This repo automates the config of hostapd, dnsmasq, dhcpcd & wpa_supplicant to transform a Pi into an AP. Requires: a Pi, Ethernet cable & DHCP-enabled port on a broadband router or a switch connected to this router. For other interesting & practical Pi solutions, my Stack page is: https://raspberrypi.stackexchange.com/users/97613/f1linux
Hello and thanks for this amazing collection of scripts. I used different methods of creating an AP so far with the pi, and they all work to an extent, but your script is by far not only the fastest to set up but also gives (for me at least) the most reliable, faster AP I could come up with.
Now my issue is: devices on my local network can ping each other only if they 're connected to the AP, or to the router. Devices connected to the AP can ping devices plugged into the router, but not the other way round. I guess it's because your script creates a subnet that (explicitly so) needs to NOT be in the same subnet as the router for example. And indeed, giving the same subnet in variables.sh before running the script results in the AP being broken. My question is: is there a way to configure pi-ap so that it puts the pi in repeater mode somehow, where it just propagates the local network and everyone can happily ping each other ? On a more general note, can you tweak the behavior of the AP without running the install script all over again ? I guess I could try some iptables routing, or changing the dnsmasq configuration and so on, but so much gets done during the install script (including ufw rules that I don't fully understand) that i'd be afraid of breaking something. Thank you so much for your time.
Hello and thanks for this amazing collection of scripts. I used different methods of creating an AP so far with the pi, and they all work to an extent, but your script is by far not only the fastest to set up but also gives (for me at least) the most reliable, faster AP I could come up with.
Now my issue is: devices on my local network can ping each other only if they 're connected to the AP, or to the router. Devices connected to the AP can ping devices plugged into the router, but not the other way round. I guess it's because your script creates a subnet that (explicitly so) needs to NOT be in the same subnet as the router for example. And indeed, giving the same subnet in variables.sh before running the script results in the AP being broken. My question is: is there a way to configure pi-ap so that it puts the pi in repeater mode somehow, where it just propagates the local network and everyone can happily ping each other ? On a more general note, can you tweak the behavior of the AP without running the install script all over again ? I guess I could try some iptables routing, or changing the dnsmasq configuration and so on, but so much gets done during the install script (including ufw rules that I don't fully understand) that i'd be afraid of breaking something. Thank you so much for your time.