1

I use raspberry pi 3. I have followed the official documentation + some troubleshooting to get it to work. I will share my configuration files. I have a suspicion that it has something to do with my /etc/dnsmasq.conf, but I am not sure.

My /etc/dhcpcd.conf

interface wlan0
static ip_address=172.16.2.201/16
static routers=172.16.2.201
static domain_name_servers=8.8.8.8

My /etc/dnsmasq.conf

interface=wlan0
domain-needed
bogus-priv
dhcp-range=172.16.2.230,172.16.2.240,12h

My /etc/hostapd/hostapd.conf

interface=wlan0
driver=nl80211
ssid=myssid*
hw_mode=g
channel=7
wmm_enabled=0
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=mypassword*

* Note that ssid and wpa_passphrase are not real

My /etc/default/hostapd

DAEMON_CONF="/etc/hostapd/hostapd.conf"

This is where I stopped following the documentation because I don't need internet access just the access point.

I left on my access point overnight and another raspberry connected to it. When I checked it the following day myssid was not showing and I have no idea why after I executed the following commands the access point was working again.

sudo systemctl unmask hostapd
sudo systemctl enable hostapd
sudo systemctl start hostapd
sudo reboot

Does my problem has something to do with this line dhcp-range=172.16.2.230,172.16.2.240,12h in /etc/dnsmasq.conf?

Stu076
  • 13
  • 4

1 Answers1

1

The installation of hostapd has changed since its latest update. If you have installed it with sudo apt install hostapd then its service is masked now. You have to configure it first and then unmask and enable it what you have done later. It should work now. I do not understand why it works the first time.

Ingo
  • 42,961
  • 20
  • 87
  • 207