03-23-2026 04:15 PM - edited 03-23-2026 04:19 PM
While setting up Layer 3/4 ACLs in Unleashed it seems that specific IP addresses or subnets in the Source and/or Destination field will make a rule getting ignored. In this case, the choosen default action (allow or deny) will be applied. The only way to have an ACL rule getting applied is when Source and Destination are set to ANY.
For testing I created the following example:
Default = deny
Rule 3 = allow ANY
Expectation: connection to other devices should be possible
Result: pinging other devices is possible
When i enter an IP adress or subnet in either Source or Destination Field or both, all traffic is denied even though all devices should be able to contact 192.168.90.10.
Default = deny
Rule 3 = allow Source 192.168.90.1/24 to Destination 192.168.90.10/32
Expectation: Connection to 192.168.90.10 should be possible, all other devices should be isolated
Result: pinging 192.168.90.10 or any other device is not possible.
Can someone confirm this?
Is there someting obvious I am missing?
Ruckus R510 with Unleashed 200.15.6.212.27
Solved! Go to Solution.
04-28-2026 08:36 PM
Hi,
I have tried to replicate this issue in lab, but the policy is working fine.
I have tried this in 200.19 and not on 200.15 as the issue is already fixed in upper releases and 200.15 is pretty old version.
