Can someone please have a look at the below ACL rule and tell me what I am doing wrong, hopefully its something simple but I would have thought rule number 1 would allow the traffic on port 9191 and the second rule blocking all other traffic.... If I only have the default allow all rule I can access the service on port 9191 so its not a tagging issue.
@PhilipDAth Yes I changed that shortly after but from the device listed in Rule one I cannot send traffic via port 9191 to the destination subnet. I cant work out why this isn't working.
If I change it to this it works.... The problem is I only want to allow that single IP access.
Setting the dest port to any works. The software is PaperCut and I am accessing the server via a webrowser with the URL http://192.168.1.5:9191
I tried creating another rule for 9192 which is their HTTPS port but this didnt work either.
Odd, I have done exactly the same setup with a firewall rather than a switch and it worked just using port 9191. Thanks for your help but we might just go down the firewall avenue.
As ACL doesn't support adding in ranges and a ton of our services use a range of ports I'd rather not have to add in a rule for every single port.
Thanks again for your help.
I believe ACLs in switches work little differently as compared to MX.
Did you get a chance to look at the following url