DHCP reservation anomaly
-
I have a Linksys Velop mesh wireless setup with five boxes set to bridge mode scattered around the house, each connected to cat 5 wiring running through the walls and to a gigabit switch. I added a TP-Link Omada wifi 7 access point connected at 2.5 gigabit to a 10 gigabit switch in my office. They both connect to my 192.168.1.0 LAN on my pfSense box. I keep the Velops up because Alexa and the doorbell camera and so on talk to that wireless network since it's scattered throughout the house, but laptops and so on connect to the Omada. Each network has its own SSID. There are DHCP reservations on the LAN for iPads and phones. The weird thing is how those devices only get assigned their reserved IPs if they connect to the Velop wireless. If they connect to the Omada, they get a random IP from the DHCP pool. I have no idea if that's a pfSense thing or layer 2 weirdness or something else.
-
If they connect to the Omada, they get a random IP from the DHCP pool. I have no idea if that's a pfSense thing or layer 2 weirdness or something else.
TP-Link Omada thing (and whatever it might be doing at L2).
Privacy Policy · Cookie Policy