Below is a list of versions that are available for the packetFilter plugin. To find other plugins, please review this listing of most recent releases of all plugins.
Plugins extend and enhance the functionality of Openfire. To install plugins, copy the .jar file into the plugins directory of your Openfire installation.
On 30 October 2020, the git repository was rewritten to remove unrelated content from this repository.
The packet filter plugin allows you to create rules that will block or reject certain packets to the server.If you are upgrading, this version *WILL DELETE ALL YOUR OLD RULES!* I wasn't happy with some of the designof the 1.0 version so I fixed it. The old format of the rules was unworkable with the new and I couldn't finda good way to convert from the old format, sorry.
By default the packet filter plugin will auto-create rules on Shared Group changes ensuring groups can always communicate with each other.
To disable this behaviour set the following Openfire System Property to false:
Copy packetFilter.jar into the plugins directory of your Openfire installation. Theplugin will then be automatically deployed. To upgrade to a new version, copy the newpacketFilter.jar file over the existing file.
Currently only the following databases are supported :
The Packet Filter plugin can be configured under "Server"-"Server Settings"-"Packet Filter Rules".
Actions come in 3 types Pass, Drop and Reject.
This allows you to quickly disable a rule without deleting it. Disabled rules will still appear on the main rule page but will have a strike through like so :
This specifies what type of packets you want to disable your choices are :
This specifies the source base JID. Currently resource specific rules aren't supported. The options for specifying a source are :
This specifies the destination base JID. The options for selecting the destination JID are the same as above.
This prints a message to the info.log when the rule is executed. This is recommend only for trouble shooting as it can fill up the logs pretty quickly in production environments. Some example output :
Rejecting packet from bart@nate-putnams-computer.local/Adium to lisa@nate-putnams-computer.local/Psi
The first rule that matches an incoming packet will be executed. For example consider the following rules :
Here we don't want any of the Simpson's talking to each other so every message from members of the Simpson group to each other are dropped. However, Marge and Homer should be able to talk to each other. To accomplish this rules allowing Homer to send message packets to Marge and vice versa are placed before the drop rule. New rules are automatically appended to the rule list. Rules can be moved at anytime using the arrows in the UI. When a rule is moved the changes take effect immediately.
Releases | Info | File | Version | Released | Openfire Version | ||||
|
![]() ![]() |
Download | 3.3.1 | Nov 10, 2020 | 4.0.0 + | ||||
|
![]() ![]() |
Download | 3.3.0 | Oct 12, 2015 | 4.0.0 + | ||||
|
![]() ![]() |
Download | 3.2.0 | Sep 13, 2013 | 3.9.0 + | ||||
|
![]() ![]() |
Download | 3.0.1 | May 7, 2011 | 3.7.0 + | ||||
|
![]() ![]() |
Download | 2.0.2 | Dec 8, 2007 | 3.5.0 + |
The plugins below, so-called SNAPSHOTS, are build automatically by the continuous integration system. They represent the latest development, but are untested.
Snapshots | Info | File | Version | Built at | Openfire Version | ||
|
![]() ![]() |
Download | 3.3.1 | 4.0.0 + | |||
|
![]() ![]() |
Download | 3.3.0 | 4.0.0 + | |||
|
![]() ![]() |
Download | 3.2.0 | 3.9.0 + | |||
|
![]() ![]() |
Download | 3.0.1 | 3.7.0 + | |||
|
![]() ![]() |
Download | 2.0.2 | 3.5.0 + |