You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
! $Id:$
! $Date:$
! $Revision:$
no ipv4 access-list INBOUND_INTERNET_V4
ipv4 access-list INBOUND_INTERNET_V4
remark $Id:$
remark accept-tcp-replies
remark Allow tcp replies to internal hosts.
permit tcp any 10.0.0.0 0.255.255.255 range 1024 65535 established
permit tcp any 172.16.0.0 0.15.255.255 range 1024 65535 established
permit tcp any 192.168.0.0 0.0.255.255 range 1024 65535 established
remark permit-offices
remark Allow Remote Offices
permit ipv4 any 200.1.0.0 0.0.31.255
permit ipv4 any 200.2.1.0 0.0.0.255
permit ipv4 any 200.5.1.0 0.0.0.255
remark permit-login-queue
remark Allow Login Queue Servers
permit tcp any 10.0.0.64/29 0.0.0.7 eq 80 log
permit tcp any 10.0.0.64/29 0.0.0.7 eq 443 log
remark default-permit
remark Allow what's left.
deny ipv4 any any
exit
Similar behavior also occurs when adding the logging:: option. As shown on permit-login-queue term. When using object-groups, the "log" keyword is not added.
I can open a different issue for the log but seems to be related.
thanks
The text was updated successfully, but these errors were encountered:
I would be really careful while using cisco object groups with capirca. not only options but icmp types are not supported and silently ignored I believe. also check what is the ip addresses you would get if you have multiple object groups in the same statement since we have another bug #121 in that area. also for IOS XE object group syntax not supported.
When using object-groups as part of the target:: ciscoxr parameters the output doesn't include the established keyword.
With object-group keyword
example .pol
Output
Without object-group keyword
Output
Similar behavior also occurs when adding the logging:: option. As shown on permit-login-queue term. When using object-groups, the "log" keyword is not added.
I can open a different issue for the log but seems to be related.
thanks
The text was updated successfully, but these errors were encountered: