TCP Intercept - ACL with log keyword

From: gladston@br.ibm.com
Date: Mon Jul 25 2005 - 14:23:20 GMT-3

• Next message: milo_az@yahoo.com: "Ignore Test"
• Previous message: buesink@fma.nl: "VPN mtu problem"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

TCP Intercep with log keyword on access-list does not work on 12.2T.
(C2600-J1S3-M, Version 12.2(15)T5)

Have you seen any restriction to use log with ACL on Intercept?
Otherwise it must be a bug.

access-list 125 permit tcp any host 148.5.22.100 eq 23 log-input
do sh access-list 125
Extended IP access list 125
    10 permit tcp any host 148.5.22.100 eq www log-input
    20 permit tcp any host 148.5.22.100 eq telnet log-input
Rack2R2(config)#no access-list 125
Rack2R2(config)#access-list 125 permit tcp any host 148.5.22.100 eq 23
Rack2R2(config)#
Jul 25 14:18:50: INTERCEPT: new connection (148.5.235.5:11177 SYN -> 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT(*): (148.5.235.5:11177 <- ACK+SYN 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT: 1st half of connection is established (148.5.235.5:11177 ACK -> 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT(*): (148.5.235.5:11177 SYN -> 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT: 2nd half of connection established (148.5.235.5:11177 <- ACK+SYN 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT(*): (148.5.235.5:11177 ACK -> 148.5.22.100:23)
Jul 25 14:18:50: INTERCEPT(*): (148.5.235.5:11177 <- WINDOW 148.5.22.100:23)
Rack2R2(config)#
Jul 25 14:18:59: INTERCEPT: ESTAB timing out (148.5.235.5:11177 <-> 148.5.22.100:23)
Rack2R2(config)#

• Next message: milo_az@yahoo.com: "Ignore Test"
• Previous message: buesink@fma.nl: "VPN mtu problem"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:31 GMT-3