I have a simple new OpenWRT setup with a main wifi network at a guest wifi network setup through LuCI (following instructions in a YouTube video). It worked great for a few months, then this morning the guest wifi stopped allowing devices to get an IP address and the log shows this:
daemon.warn dnsmasq-dhcp[1]: no address range available for DHCP request via phy0-ap1
The main wifi network still works fine. I tried creating a new Network Interface, but it still had the same issue. It wasn't until I created a new Wireless network that the issue went away. (Specifically it seems the 802.11ac/n wireless network was the issue.) The settings of the old and new Wireless network appear the identical in LuCI.
Is there a logical reason why a Wireless network setup would start causing a DHCP issue?
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
Your first guest network is lacking a subnet mask. The guest2 network is overlapping with guest -- it must be a different subnet.
Your guest3 network is the only one that is associated with wireless SSIDs. However, you've got more than one SSID associated with the guest3 network, so you must have a bridge defined (which you do not have currently). The requirement to use a bridge will be true for any network that will connect to more than one radio and/or radio+ethernet or multiple ethernet ports.
Thanks for the reply. I think that first part about guest is probably not the original issue. When the issue started, I hadn't yet created guest2 or guest3, and it did have a subnet mask of 255.255.255.0 before I started messing with the settings to try to fix the issue.
But the bridge thing sounds like a possible thing I need to do. But is there a reason why it worked for months and then suddenly stopped working? Possibly a device connected to the other wifi radio for the first time (802ac/n vs 80211b/g/n)?
config device
option name 'br-guest'
option type 'bridge'
config interface 'guest'
option device 'br-guest'
option proto 'static'
... more options
Notice this is exactly like the default configuration with br-lan however no Ethernet ports are (yet) included in br-guest. Whenever a wifi AP is attached with option network guest, it will then be included in br-guest. You can confirm that with the command brctl show which shows the running bridges and their members.
If they look in Network/Interfaces in LuCI it will show, with icons, what device is in what interface.
It is easier to visualize when first using OpenWrt.
Well you have to.
The image translators work for the construct program but there's way too much information to decode the matrix.
You get used to it I I don't even see the code; all I see is blonde, brunette redhead.
Even if it wasn't part of the original issue, it does need to be fixed. I'm honestly not sure what size network results if a subnet mask (or CIDR value) is not declared -- it might be a /32, but it also could be larger or just simply will cause an error.
That's possible... it's hard to know the circumstances, but a bridge is required if more than one physical interface is linked to your network interface.
Ok, yeah after doing some more experimenting, it's pretty clear that the issue was having more than one wireless interface associated with a network interface without having a bridge. I was able to reproduce the issue any time I had more than one wireless network using the same network interface.
Yeah, that guide could use to be updated. I actually don't like that it creates the wifi SSID first -- personally, I prefer to create the bridge, then the network interface, dhcp server, and firewall configs, then add the SSID and associate it with the network.
