Project

General

Profile

Bug #3688

firewall rule syntax error with Diffserv Code Point

Added by James Dietrich about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
06/02/2014
Due date:
% Done:

100%

Affected Version:
Affected Architecture:

Description

I am using 2.1.3.

I am getting a syntax error when creating a floating firewall rule with a particular Diffserv Code Point. I want to match on 0x04 (lowdelay, ToS 0x10), but when I choose that option from the dropdown and save the rule, it gives me an error:

[ There were error(s) loading the rules: /tmp/rules.debug:169: syntax error - The line in question reads [169]: match inet proto tcp from any to any port 22 dscp 0x04 (lowdelay, ToS 0x10) flags S/SA queue (qRT,qACK) label USER_RULE]

Any ideas? I'm wondering if the (lowdelay, ToS 0x10) part shouldn't be in the generated rule, but don't know for sure, or what to do about it if that's the problem.

Also, note that a similar syntax error is produced when choosing these other two Diffserv Code Points:
0x01 (reliability, ToS 0x04)
0x02 (throughput, ToS 0x08)
I suspect that whatever the root problem is affects all three of these.

I hope I've explained the problem well enough, but if you need any other information, please let me know.

Thank you!

James Dietrich

Associated revisions

Revision e792ac36
Added by Renato Botelho about 4 years ago

Remove extra data after space and fix pf rule syntax. It should fix #3688

Revision 052dfa93
Added by Renato Botelho about 4 years ago

Remove extra data after space and fix pf rule syntax. It should fix #3688

History

#1 Updated by Renato Botelho about 4 years ago

  • Target version set to 2.2

#2 Updated by Renato Botelho about 4 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#4 Updated by James Dietrich almost 4 years ago

I updated to 2.1.4 a few days ago, and now I do not get this syntax any more.

Thank you!

James

#5 Updated by Renato Botelho almost 4 years ago

  • Status changed from Feedback to Resolved
  • Target version changed from 2.2 to 2.1.4

Also available in: Atom PDF