Tuesday, June 15, 2021

NAT network inside IPSec Site-Site

I am trying to troubleshoot my IPSec Many to One NAT Tunnel I have setup.

I am able to ping across it and browse to the http page of a server however as soon as I try to browse to http://10.21.8.54/subsite I get "Connection Reset" and seeing missing packets in Wireshark.

I am wondering if this is a routing issue or DNS because I have 2 firewalls. Unfortunately, I had to have Firewall 1 running the IPSec tunnel then behind it put Firewall 2. On Firewall 2 I have WAN rules to allow in all traffic from the LAN IP of this 10.21.8.54. I have run powershell connection tests to 10.21.8.54 on port 80 and everything passes I do not know how I can connection test 10.21.8.54/subsite though.

Any advice appreciated I can post some packet captures from Firewall 1 and 2 eth1 interfaces if it would help:

firewall 1: 17:36:57.649522 IP 192.168.1.38.58674 > 10.21.8.54.80: Flags [P.], seq 1:328, ack 1, win 1025, length 327: HTTP: GET /pss/resourcesIndex.txt.jsp?clientOsName=Windows%2010&clientIs64=true&clientJarType=PS%20Client.jar&clientJVMIs64=true&clientDefaultJVMVersion=1.8.0_282&remoteHostMachineName=HC1 HTTP/1.1 17:36:57.740355 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], ack 328, win 512, length 0 17:36:57.773959 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:36:57.773984 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1383:2765, ack 328, win 512, length 1382: HTTP 17:36:57.774087 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 2765:4147, ack 328, win 512, length 1382: HTTP 17:36:57.774252 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 4147:5529, ack 328, win 512, length 1382: HTTP 17:36:58.072966 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:36:58.691589 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:36:59.887819 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:37:02.294050 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:37:07.110614 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [.], seq 1:1383, ack 328, win 512, length 1382: HTTP: HTTP/1.1 200 17:37:16.712159 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [R.], seq 1383, ack 328, win 0, length 0 17:37:16.713221 IP 192.168.1.38.58674 > 10.21.8.54.80: Flags [.], ack 1, win 1025, length 0 17:37:16.738666 IP 10.21.8.54.80 > 192.168.1.38.58674: Flags [R], seq 560975640, win 0, length 0

firewall 2: 14:36:57.645196 IP 192.168.120.16.58674 > 10.21.8.54.80: Flags [P.], seq 1:328, ack 1, win 1025, length 327: HTTP: GET /pss/resourcesIndex.txt.jsp?clientOsName=Windows%2010&clientIs64=true&clientJarType=PS%20Client.jar&clientJVMIs64=true&clientDefaultJVMVersion=1.8.0_282&remoteHostMachineName=HC1 HTTP/1.1 14:36:57.743479 IP 10.21.8.54.80 > 192.168.120.16.58674: Flags [.], ack 328, win 512, length 0 14:37:16.715280 IP 10.21.8.54.80 > 192.168.120.16.58674: Flags [R.], seq 1383, ack 328, win 0, length 0 14:37:16.715821 IP 192.168.120.16.58674 > 10.21.8.54.80: Flags [.], ack 1, win 1025, length 0 14:37:16.741756 IP 10.21.8.54.80 > 192.168.120.16.58674: Flags [R], seq 560975640, win 0, length 0



No comments:

Post a Comment