-- Exhibit -

-- Exhibit --
Refer to the exhibit.
Users receive an error when attempting to connect to the website https://website.com. The website has a DNS record of 195.56.67.90. The upstream ISP has confirmed that there is nothing wrong with the routing between the user and the LTM device.
The following tcpdump outputs have been captured:
External Vlan, filtered on IP 168.210.232.5
00:25:07.598519 IP 168.210.232.5.33159 > 195.56.67.90.https: S 1920647964:1920647964(0) win 8192
<mss 1450,nop,nop,sackOK>
00:25:07.598537 IP 195.56.67.90.https > 168.210.232.5.33159: S 2690691360:2690691360(0) ack
1920647965 win 4350 <mss 1460,sackOK,eol>
00:25:07.598851 IP 168.210.232.5.33160 > 195.56.67.90.https: S 2763858764:2763858764(0) win 8192
<mss 1450,nop,nop,sackOK>
00:25:07.598858 IP 195.56.67.90.https > 168.210.232.5.33160: S 1905576176:1905576176(0) ack
2763858765 win 4350 <mss 1460,sackOK,eol>
Internal Vlan, filtered on IP 168.210.232.5
00:31:46.171124 IP 168.210.232.5.33202 > 192.168.100.20.http: S 2389057240:2389057240(0) win 4380
<mss 1460,nop,wscale 0,sackOK,eol>
What is the problem?
Recent Comments (The most recent comments are at the top.)
As we can see the destinated backend node on the subnet 192.168.100.0/24 has the default gateway of 192.168.100.1, and the default gateway ip is hosted by the network firewall. Thus, when the node responds back to the request, it goes to the firewall, and since firewall does not have any connection – it looks the state of the connection. The Network Firewall simply drops the connection.