Skip to content
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

Aclcheck.py thinks IP does not include TCP #22

Open
GoogleCodeExporter opened this issue Jun 30, 2015 · 2 comments
Open

Aclcheck.py thinks IP does not include TCP #22

GoogleCodeExporter opened this issue Jun 30, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. create term using "protocol:: ip:

term block-stuff {
  source-address:: MY_NETWORKS
  protocol:: ip
  logging:: true
  action:: deny
}

2.

Use ./aclcheck_cmdline.py to test the ACL with --proto ip. It works.
IP address 1.2.3.4 is in MY_NETWORKS.

./aclcheck_cmdline.py -p policies/toSERV03-WCM-IFZ.pol -s 1.2.3.4 -d 5.6.7.8 
--dport 80 --proto ip
  filter: toSERV03-WCM-IFZ
          term: block-stuff
                deny


3.

Use ./aclcheck_cmdline.py to test the ACL with --proto tcp. It *should* work 
just like the case above, since it is supposed to block all IP packets; but it 
does not. It rolls over the next term.

./aclcheck_cmdline.py -p policies/toSERV03-WCM-IFZ.pol -s 1.2.3.4 -d 5.6.7.8 
--dport 80 --proto tcp
  filter: toSERV03-WCM-IFZ
          term: default-deny
                deny


What version of the product are you using? On what operating system?

r145 with minor modifications on linux RHEL5.

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 23 Sep 2011 at 10:34

@GoogleCodeExporter
Copy link
Author

I'll be taking a look at this shortly.  
Thanks for reporting this.

Original comment by watson on 29 Sep 2011 at 3:00

  • Changed state: Accepted
  • Added labels: Priority-Low
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

I'll be taking a look at this shortly.  
Thanks for reporting this.

Original comment by watson on 29 Sep 2011 at 3:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant