Hi Matt
I have recently configured the Route 10 router but do not have any Alta AP’s, does that mean I cannot block a device as I do not see the cross icon rather just a delete icon.
I created a firewall rule to drop traffic to the specific device based on IP but it doesn’t do the job, some of the features still run and only way I can do is to have the DL/UL speed set to very very low like 0.00001
Any help would be appreciated
Thanks
Hi @binodnepal and welcome to the community!
That’s correct. Right now, there is no wired blocking like you would normally see for wireless devices. This is something actively being worked on.
But this doesn’t mean you’re out of luck. You should be able to block via firewall rules. If you can share a screenshot of the rule(s) you created that aren’t working, we should be able to correct them to block traffic.
Additionally, you could override any number of settings for the client(s) in the Devices tab; the first one that comes to mind is to override the VLAN to one that doesn’t exist.
1 Like
Hi Matt
Thank you so much for the reply.
Please check the screenshot, One more thing while changing the settings on an individual device it keeps on popping up saying multiple device will be affected so it just make it so confusing, like,
am I changing only for the selected device or will it affect others too.
thanks
Binod
Thanks DN,
I will give it a try
it is working, thanks heaps
1 Like
You may also consider setting the source as a MAC address instead, since the DHCP lease can expire and the client can regain access by just turning the computer off for a day.
3 Likes
Good to know! My devices that are blocked are static though I will probably use this method going forward.
1 Like
I initially had the same opinion. However, I’ve come to find that this warning is very crucial if you’re running mixed vendor networks (which is often the root of why you’ll see the warning in the first place). If you’re making interface changes on a port that is upstream for another vendor’s switch, the outcome may not be what you’re expecting. It’s simply a stop gap if there are more than 1 MAC address detected downstream of the relevant change you’re making.
1 Like
I would agree if the change had an interface specified. The warning is saying you are updating the settings for all devices connected to this port which doesn’t make sense in this case. No port is being specified, it’s a single ip, which I think is where the confusion comes from when people get that warning. I know I hesitated when I got it the first time and tried to make sense of it but had to come to the forum to find the answer. Ultimately, I don’t think it’s that big of a deal, the language chosen is just confusing when the changes you are making dont reflect what its warning you about.
1 Like
Hi Matt
I tried assigning a VLAN that doesn’t exist, e.g. 2 and it I thought it was only supposed to change this device, rather what it did was it changed the VLAN of my unifi AP that the device was connecting to it and brought the whole network down. Why will this happen, does it go and change the VLAN for the physical port that the unifi ap was connected to, I am puzzled with this VLAN on device setting.
Any help is appreciated.
Thanks
Binod