Feature #2302: Uploaded Layer 7 patterns not saved in config, backed up, or synced - pfSense - pfSense bugtracker

Actions

Copy link

Feature #2302

closed

Uploaded Layer 7 patterns not saved in config, backed up, or synced

Added by Jim Pingle almost 13 years ago. Updated over 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Traffic Shaper (ALTQ)

Target version:

2.2

Start date:

03/20/2012

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Description

If you upload a custom Layer 7 pattern, it's dropped into /usr/local/share/protocols/ and that's it. If you restore a config using a custom pattern, it would not be fully functional until the pattern was uploaded again. Also in a CARP setup the pattern would have to be manually uploaded to both units or it would be possible to create a broken rule if the pattern only existed on the master but the l7 shaper config is sync'd to the slave.

Would be better if we stored the uploaded .pat files in the config and wrote them out to /usr/local/share/protocols/ as needed, as we do with some other things in the GUI (CP pages, SSH keys, etc) and also included these in the config sync for XMLRPC when the Layer7 box is checked.