Sat Dec 21 16:16:49 2024 daemon.warn dnsmasq-dhcp[1]: not giving name E8450Hall.lan to the DHCP lease of 192.168.87.175 because the name exists in /tmp/hosts/dhcp.cfg01411c with address 192.168.86.245
Sat Dec 21 16:16:49 2024 daemon.warn dnsmasq-dhcp[1]: not giving name E8450Hall to the DHCP lease of 192.168.87.175 because the name exists in /tmp/hosts/dhcp.cfg01411c with address 192.168.86.245
I found this in the syslog. I want the dumb AP to be accessible only on 192.168.86.245. I have clearly mentioned this in my infinite static DHCP leases. However, 192.168.87.175 is assigned to the same Dumb AP and it is accessible on the guest network.
I have 2 Linksys E8450 and running latest openwrt stable.
Your screenshot does not show whether or not your guest network gets provided with IP addresses from your dumb AP as well or not. Even though I don't think it makes much sense, you can have both, an interface to have its IP address assigned via DHCP and give out other IP addresses on the same interface at the same time.
But your screenshot shows:
You have a WAN interface, which is something you don't need on a dumb AP. Even if that is unrelated to the issue you mentioned.
You have your guest network as DHCP client. Which is not something you need either, just put that guest network to "none".
You say it's a dumb AP but you don't appear to be using bridges for lan or guest, so how are you getting any kind of wireless connecting through to any ethernet ?
Basically you have two options:
You have br-lan already, and you're using that to do vlan filtering on ports it looks like. You should probably make a bridge underneath ** like br-dsa or br-switch, do the filtering off that. Then you have br-lan assinged to lan and have br-dsa.99 as a member. For the guest the same method, you make br-guest it's assigned to guest and have br-dsa.4 as member. It sounds like you might also want to change the connection type for guest to 'unmanaged'. **This style doesn't always work with some devices though so while playing around with this perhaps be careful and keep a way to access the device going with a usb adapter or something.
You stop using the bridge filtering where you've made the vlans off the br-lan bridge, you just have br-lan assigned to lan and br-guest assigned to guest and put whatever ports in them how they go. Eg if br-lan has lan1 and lan4.99 and br-guest has lan2 and lan4.4 etc etc and do it that way instead and again for guest I don't know exactly what you're trying to do but you might need to set the connection type to unmanaged.
Hi @psherman ! Long ago, you had helped me with an issue on OpenWrt and I am grateful for it. Currently, I have hit up another snag. I am no OpenWrt expert, and I code in python for a living. It would be great if you could help me get this sorted, thank you so much either ways!
It's late here and my bedtime, hopefully one of the guys that are very good with this step in soon. Posting your configs isn't a bad idea though and it probably one of the first things they'll ask you to do anyway.
Hi @lleachii ! In a very humble tone, kindly please try to understand I am a python dev and unable to understand the network engineer level technicals you are saying. I have updated my main post with entire settings. So kindly please explain in simple terms or tell me which settings to change.
My Problem:
I want my dumb AP to be ONLY accessed on the main VLAN which is 192.168.86.0. However, 192.168.87.175 is assigned to the Dumb AP, and it is accessible on the guest network. So right now, its accessed on both main VLAN and guest VLAN with different internal ipv4. So people on the guest network can view the router page. I simply don't want this for many reasons which I am not listing here.
Expected solution:
Dumb AP accessed only on the main VLAN which is 192.168.86.0
Additionally, I want guest network to give out DHCP in 192.168.87.0 range. I want this functionality. It's only that I don't want the dumb AP here.
