topic Blocking Client to Client communication in ExtremeWireless (Identifi)

Blocking Client to Client communication

dcsdne — Thu, 13 Feb 2020 02:36:46 GMT

I am attempting to block client to client communication on B@AP topologies.

I found this:

https://extremeportal.force.com/ExtrArticleDetail?an=000080875

But just like it says this feature does not work on B@AP topologies.

I then moved onto this solution:

https://extremeportal.force.com/ExtrArticleDetail?an=000067499

Using this I am able to reach the gateway on my 10.x.x.x network, but I’m unable to reach anything on my 172.x.x.x network where my DNS lies. It would stand to reason that the deny rule is only for the 10.x.x.x network. I want to block the clients from talks to each other not block them from file/print servers.

Am I missing something?

Re: Blocking Client to Client communication

Ronald_Dvorak — Thu, 13 Feb 2020 16:59:04 GMT

Could you please post a screenshot of the rule set that you use in the role.

-Ron

Re: Blocking Client to Client communication

dcsdne — Thu, 13 Feb 2020 23:06:23 GMT

Re: Blocking Client to Client communication

Ronald_Dvorak — Thu, 13 Feb 2020 23:19:40 GMT

Could you also post the settings for the other tab (example below)…..

I’d assume that the client topology is 906 in your example.

In that case set it as above to contain VLAN and use the 906 topology and set the last rule to allow instead of action 906.

In that case the rule set would ….

allow the default GW of 10.5.0.1
deny the rest of 10.5.0.0/22
allow all other traffic (i.e. DNS)

Ron

Re: Blocking Client to Client communication

dcsdne — Fri, 14 Feb 2020 00:34:58 GMT

Correct and That worked. Thank you very much for your help.