New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger ACL parser can't parse `fragment-offset` with byte-ranges in Juniper ACLs #47

jathanism opened this Issue Oct 10, 2012 · 0 comments


None yet
1 participant

jathanism commented Oct 10, 2012

Trigger can definitely parse fragment-offset in Juniper ACLs but it looks like we never actually account for a fragment- offset range.

So it can parse this:

fragment-offset 0;

But not this:

fragment-offset 6-8191;

When parsing an ACL with this it results in the following error:

Cannot parse /data/firewalls/ missing semicolon on line 625
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment