Reboot pfsense and traffic shaper activated

cyberpf

Dear all,

I've got a problem with my pfsense firewall about traffic shaper (version 1.2.3).

Then the fw is up and I activate the traffic shaper or I desactivate the traffic shaper, I have not error.
And it's working well (queues worked).

But if the traffic shaper is enable and I reboot the fw, I've got problems and errors. Following the message error :
<<
Acknowledge All .:. 11-18-10 13:00:31 - [filter_load]There were error(s) loading the rules: pfctl: DIOCADDRULE: Invalid argument The line in question reads [ DIOCADDRULE]:

If the traffic shaper is disable and I reboot the fw, and after it's enable I have no errors.

Could you help me to find a solution without human intervention ?

postpone the start of the traffic shaper ?
during the shutdown process, disable it ?

Thanks for your help

joelserrano

I'm having the same problem.

When I activate shaper and press 'save' I always get:

Feb 9 12:14:24 pfsense check_reload_status: reloading filter
Feb 9 12:14:25 pfsense php: : New alert found: There were error(s) loading the rules: pfctl: DIOCADDRULE: Invalid argument The line in question reads [ DIOCADDRULE]:
Feb 9 12:14:25 pfsense php: : There were error(s) loading the rules: pfctl: DIOCADDRULE: Invalid argument - The line in question reads [ DIOCADDRULE]:

If I deactivate shaper and press 'save' then it reloads config OK.

I've been working with this installation for 3 years no problem, (shaper on). Everything config change has been done through the GUI.

I needed to create 50 alias, queues, rules, etc. So I backups up ALIAS-config, RULES-config and SHAPER-config, modified the XML's and restored them back. And this is were the problems begin…

When I reference any alias created 'by hand' in the shaper config, it fails on reload. (everything else works perfect.)

I'm going to compare my config, with the one generated by the GUI to see if I'm missing anythin and I'll post back.

Regards,

Joel.

joelserrano

Just compared the config (hand made XML with GUI made XML), everything is exactly the same.

Don't understand what is going on :-(

Is there any queue limitation?

I have 34 queues created right now and it's OK. If I create queue #35 I start getting the error again…

Any advice?

Thanks in advanced.

Joel.

eri--

In 1.2.3 there is a limit that you are hitting.
This has been upped quite a lot in 2.0