topic Re: R510 Unleashed: Layer 3/4 ACL not working in Unleashed

R510 Unleashed: Layer 3/4 ACL not working

PeterPan — Mon, 23 Mar 2026 23:19:09 GMT

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

Re: R510 Unleashed: Layer 3/4 ACL not working

Rohit_W — Mon, 13 Apr 2026 16:50:54 GMT

Hi Peter,

I would recommend you to create a ticket with us to troubleshoot this issue.

Please use the below link to create a new ticket:
https://support.ruckuswireless.com/contact-us

Regards,
Rohit Walawalkar
Technical Support Engineer -EMEA
Work Hours: Monday-Friday, 9 AM to 5 PM GMT
Location: India

Re: R510 Unleashed: Layer 3/4 ACL not working

sanjay_kumar — Wed, 29 Apr 2026 03:36:18 GMT

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.