AnsweredAssumed Answered

Packet Filter Plugin not working correctly?

Question asked by SF on May 10, 2011
Latest reply on Jul 16, 2011 by natep

Looks like there is a bug in PFP (unless I am using it incorrectly)

 

Openfire Server: 3.70

PFP version: I used .jar under 3.01 document, still showing up as 3.0.0 in Admin Console

Clients used: Spark 2.60 and Pidgin

 

I am using LDAP to configure User groups.

 

I have GROUP1 with User1 being a member of the group, and GROUP2 with User2 being a member of that group.

 

I setup two rules:

 

Reject from GROUP1 to GROUP2, Packet Type ANY log false

Reject from GROUP2 to GROUP1, Packet Type ANY log false

 

When I use regular chat - communication is blocked, but if User1 and User2 are in the same Chat Room - communication is not blocked.

 

when I added two more rules:

 

Reject from GROUP1 to GROUP2, Packet Type MUC log false

Reject from GROUP1 to GROUP2, Packet Type MUC log false

 

That does not change anything.

 

What I need to achieve is that if communication between User1 and User2 is not allowed - it is blocked on all levels.

 

Thanks.

 

 

UPDATE:

 

When I create a rule:

 

Reject from GROUP1 to First-Room1@myconference.service type ANY

 

That blocked GROUP1 member from entering the room.

 

All my room (I have around 60 rooms and around 200 users in 12 groups) are created with strict naming rules enforced:

 

Example: First-Room1, First-Room2, Second-Room1  e.t.c.

 

When I try to use a wildcard so my rule looks like:

 

Reject from GROUP1 to First-*@myconference.service type ANY

 

User is no longer blocked. 

 

I can use that "workaround" but it will result in hundreds of rules that will need to be created.

 

So my question is updated - how I can be able to enforce "no talk" policy without creating a rule for any possible combination of groups and chatrooms?

Outcomes