ASA Vpn peer L2L connection

anand kumar · ‎05-22-2017

Hi All,

Can we check with below capture there is no issue from ASA side.

87: 19:43:11.918363 802.1Q vlan#161 P0 10.160.21.212.49219 > 10.143.227.2.389: SWE 3625561743:3625561743(0) win 8192 <mss 1460,nop,wscale 8,nop,nop,sackOK>
88: 19:43:11.963664 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49219: R 1780451825:1780451825(0) ack 3625561744 win 8192
89: 19:43:12.472006 802.1Q vlan#161 P0 10.160.21.212.49219 > 10.143.227.2.389: S 3625561743:3625561743(0) win 8192 <mss 1460,nop,wscale 8,nop,nop,sackOK>
90: 19:43:12.516315 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49219: R 2485435093:2485435093(0) ack 3625561744 win 8192
93: 19:43:13.018889 802.1Q vlan#161 P0 10.160.21.212.49219 > 10.143.227.2.389: S 3625561743:3625561743(0) win 8192 <mss 1460,nop,nop,sackOK>
94: 19:43:13.063244 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49219: R 670494809:670494809(0) ack 3625561744 win 8192
111: 19:43:29.796437 802.1Q vlan#161 P0 10.160.21.212.49220 > 10.143.227.2.389: SWE 2954279120:2954279120(0) win 8192 <mss 1460,nop,wscale 8,nop,nop,sackOK>
112: 19:43:29.840837 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49220: R 2240365577:2240365577(0) ack 2954279121 win 8192
113: 19:43:30.347485 802.1Q vlan#161 P0 10.160.21.212.49220 > 10.143.227.2.389: S 2954279120:2954279120(0) win 8192 <mss 1460,nop,wscale 8,nop,nop,sackOK>
114: 19:43:30.391840 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49220: R 3381956147:3381956147(0) ack 2954279121 win 8192
115: 19:43:30.894362 802.1Q vlan#161 P0 10.160.21.212.49220 > 10.143.227.2.389: S 2954279120:2954279120(0) win 8192 <mss 1460,nop,nop,sackOK>
116: 19:43:30.938717 802.1Q vlan#161 P0 10.143.227.2.389 > 10.160.21.212.49220: R 1783798289:1783798289(0) ack 2954279121 win 8192
116 packets shown

JP Miranda Z · ‎05-22-2017

Hi anand kumar,

We definitely need more information about what you are trying to find out, if you only want i quick analysis of the capture i can tell you a Reset from 10.143.227.2 on por 389 (LDAP) is happening, now please explain a little bit more your concern so we can help you.

Hope this info helps!!

Rate if helps you!!

-JP-