I laughed so hard when I looked at the photo presenting evidence of "suspicious, sophisticated digital equipment" that got three Russians expelled from Montenegro... Laptop, BMD or AJA converters, Streamdeck, random cables, APs, tripod etc. basically what every AV person carries around on the job 🤣
/rant
They try to sell this as an open standard ecosystem with interoperability between various devices but, without mentioning names, brand X controller won't discover new brand Y devices on the network until you change something only brand Y controller can do.
Brand Z controller does matrix switching with any brand endpoint but you can't really change any settings.
Brand Y controller gives you options to change settings 1-6, but you need brand X controller to change settings 5-10 while it does not have settings 1-4.
Brand X endpoints overheat and go insane broadcast flood mode on the network unless they are in a chilled server room (so not under a meeting room table or behind TV where you need them).
Brand Y manual says you can't use more than 50 brand Y endpoints on one network/controller while they happily work with any other controller.
Brand X endpoint can receive signals from brand Y, but not the other way around.
Brand Z endpoint says it can scale any signal to whatever output you want but in reality only handles exactly the same input to output resolution/framerate.
Brand Z controller will keep every single endpoint ever connected on its list of devices/matrix and you cannot delete them (there is a delete button that does nothing).
Brand X,Y & Z controllers all have buttons to reboot and factory reset endpoints that do nothing at all.
Brand X controller recognizes an endpoint as device model F, while brand Y controller says that same device is model G.
I could probably go on. It's a shit show across the board with all the major brands.
But the real question is, will IPMX be any better or is that wishful thinking about vaporware?
I thought this would be easy but assumption is the mother of...
Anyway, for some testing I want to block UDP traffic on a specific port (call it 6666, specific number is irrelevant because it's configurable on the sender). But for some reason Netgear (could be others, I don't know) has this weird implicit deny all rule:
from the manual:
An implicit deny all rule is included at the end of an ACL list. This means that if an ACL is applied to a packet and if none of the explicit rules match, then the final implicit deny all rule applies and the packet is dropped
So the logic is to allow specific ports and automatically deny everything else. What's the point of having explicit deny rules then? Like deny 6666, but also deny everything else as well?!
Anyone know if there's a way to do what I want without having an ACL list with 100+ allowed ports to block the one I actually want?