Good afternoon all,
I am prepping for my Route10 (Monday, yes!!!) and was setting up my vlan’s and scopes. I went to set a static IP for a few of my devices and received an error about adjusting the IP on the port level and not the device. Am I doing something wrong?
Also, I am using DHCP on my pi-hole… is it possible to turn off DHCP for VLAN1 for instance and let my pi-hole continue to manage?
I have this same problem; am trying to set a single device on one of my VLANs to have a static IP, but doing so gives me a prompt that I am setting this for all devices on the port. Going ahead causes ALL the devices connected downstream to that port (L4) to not have any connection until I delete that static IP configuration.
In my case, the only Alta Labs device is the Route 10. L4 is connected to a Ubiquiti USW-Aggregation where the rest of the network is connected. (I am evaluating performance of the Route 10 before gradually switching to a full Alta Labs setup).
All VLANs configured on the Route10 are tagged on the USW-Aggregation as well.
Ignore original text below. The dialog is misleading and works as the entry UI would suggest. Static entries are working per-device.
Thought I’d chime in as well. I’m having this exact issue of not being able to setup per-device static IPs. Please let me know what additional information I could provide in order to assist in any troubleshooting.
Setup:
Route10 → Wireless AP
Two VLANs: ID1 is main network, ID2 is IoT
Selecting any device connected to the wireless AP in order to setup a singular static IP results in the message of applying it to everything that comes through the AP (which clearly, we don’t want).
The wired side is directly to a rack server hosting 4 ESXi guests. Selecting any of these guests and attempting to assign a singular static IP also gives the message of assigning it at the port level.
Please advise.
I have the exact same problem. I could not set static IP and keep getting this message about it getting set at port level than device level.
This warning is that the downstream link appears to be multiple devices, because we’re seeing multiple MAC addresses associated to the interface. Usually the warning may be ignored, but you may have some devices which misbehave.
If you have an issue after setting the address, please report what devices are downstream of the interface and what issues you are seeing on them.
Just an update:
I selected to make the change anyway - Nothing disconnected. Phew!
Would this message always be displayed on TRUNK ports ?
All my links downstream from the route 10 are trunk ports to a Managed switch. Passing VLAN1 as native and various VLANs.
So multiple devices will be present on one interface/port. ?
Tested with some ESP32 devices connected to a third-party AP (which broadcasts 4 different SSIDs, each for a different VLAN) that is connected directly to one of the PoE+ ports on the Route 10.
Assigning them an IP address within the reserved range, and then rebooting the device, the device doesn’t get an IP address, and when visiting the reserved IP Address on a web browser on a laptop connected to another of the Route 10’s ports with the same VLAN as that of the ESP32 device, the Route 10’s controller page is presented instead.
Like Quackers, these ports are trunked.
@Alta-Jeff I would love to help troubleshoot this. Let me know on discord if you want me to do some testing.
There isn’t a way to assign an IP address based on the connected port. You would need to assign the IP for a specific MAC. The warning is simply notifying that other settings, such as UL/DL rate, would also apply to anything else on that port, but can be ignored in most cases.
