<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WAN/LAN ping responding problem in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26152#M92600</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"&lt;SPAN style="color: #333333; background-color: #ffffff;"&gt;i dont need static routes becouse i dont have any other routers with other adresses in internal network." &amp;nbsp;??? can you clarify please ??? I'm lost now &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Sep 2018 13:23:40 GMT</pubDate>
    <dc:creator>Jerry</dc:creator>
    <dc:date>2018-09-18T13:23:40Z</dc:date>
    <item>
      <title>WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26147#M92595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;i have CP 4600 r77.30&lt;/P&gt;&lt;P&gt;i have server ip 10.10.10.10/24 and i want put it to wan (create node - NAT - static - WAN IP). Create policy. Now when i ping server on lan (10.10.10.10) its work fine. When i ping it on WAN&amp;nbsp;its not respond. After 10-15 sec its start responding on WAN ip but not respond on lan ip.If stop pinging on wan then lan ip after 10-15 sec start responding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ping LAN responding&lt;/P&gt;&lt;P&gt;ping WAN when lan is responding - not responding&lt;/P&gt;&lt;P&gt;stop pinging LAN, ping WAN, 10-15 sec WAN start responding&lt;/P&gt;&lt;P&gt;stop pinging WAN, ping LAN, 10-15 sec LAN start responding&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where is the problem ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sorry for my english.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2018 10:32:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26147#M92595</guid>
      <dc:creator>Adam_Majka</dc:creator>
      <dc:date>2018-09-12T10:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26148#M92596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Show us a&amp;nbsp;&lt;EM&gt;fw monitor&lt;/EM&gt; trace of these pings please.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2018 11:36:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26148#M92596</guid>
      <dc:creator>Danny</dc:creator>
      <dc:date>2018-09-12T11:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26149#M92597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;as Danny mentioned that would be the 1st step, 2nd one however would be to understand more about your topology, where is your WAN port and LAN port directly connected (hooked up / plugged into) ?&lt;/P&gt;&lt;P&gt;have you checked your MTU values on your interfaces by any chance?&lt;/P&gt;&lt;P&gt;what about your routes (static?)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2018 14:47:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26149#M92597</guid>
      <dc:creator>Jerry</dc:creator>
      <dc:date>2018-09-17T14:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26150#M92598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the NAT IP in the same range as the WAN interface?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wheb you type: &lt;EM&gt;fw ctl arp&lt;/EM&gt;&amp;nbsp;does the NAT IP show up with a mac address?&lt;/P&gt;&lt;P&gt;From where are you pinging the WAN IP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Sep 2018 21:19:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26150#M92598</guid>
      <dc:creator>Maarten_Sjouw</dc:creator>
      <dc:date>2018-09-17T21:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26151#M92599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thx for reply&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;eth 1 : WAN 1 67.59.219.82&amp;nbsp;&amp;nbsp;&amp;nbsp;255.255.255.248&lt;/P&gt;&lt;P&gt;eth2 : LAN (gateway) 172.12.1.87&amp;nbsp;&amp;nbsp;&amp;nbsp;255.255.248.0&lt;/P&gt;&lt;P&gt;eth3 : WAN 2 212.169.34.42&amp;nbsp;&amp;nbsp;&amp;nbsp;255.255.255.248&lt;/P&gt;&lt;P&gt;eth7 : DMZ 10.10.10.1&amp;nbsp;&amp;nbsp;&amp;nbsp;255.255.255.0&lt;/P&gt;&lt;P&gt;MTU 1500 for all interfaces&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i dont need static routes becouse i dont have any other routers with other adresses in internal network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;fw ctl arp&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;vdsl-67.59.219.87.an.pl (67.59.219.87) at 00-1c-7f-55-ce-cf interface 67.59.219.82&lt;BR /&gt;rev-212.169.34.45.an.pl (212.169.34.45) at 00-1c-7f-55-ce-d3 interface 212.169.34.42&lt;BR /&gt;(172.12.0.1) at 00-1c-7f-55-ce-d1 interface 172.12.1.87&lt;BR /&gt;WAN (67.59.219.83) at 00-1c-7f-55-ce-cf interface 67.59.219.82&lt;BR /&gt;vdsl-67.59.219.86.an.pl (67.59.219.86) at 00-1c-7f-55-ce-cf interface 67.59.219.82&lt;BR /&gt;rev-212.169.34.44.an.pl (212.169.34.44) at 00-1c-7f-55-ce-d3 interface 212.169.34.42&lt;BR /&gt;osticket.domain.local (172.12.1.206) at 00-1c-7f-55-ce-d1 interface 172.12.1.87&lt;BR /&gt;rev-212.169.34.43.an.pl (212.169.34.43) at 00-1c-7f-55-ce-d3 interface 212.169.34.42&lt;BR /&gt;vdsl-67.59.219.85.an.pl (67.59.219.85) at 00-1c-7f-55-ce-cf interface 67.59.219.82&lt;BR /&gt;rev-212.169.34.46.an.pl (212.169.34.46) at 00-1c-7f-55-ce-d3 interface 212.169.34.42&lt;BR /&gt;vdsl-67.59.219.84.an.pl (67.59.219.84) at 00-1c-7f-55-ce-cf interface 67.59.219.82&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CP&amp;gt; fw monitor -e "accept (dst=10.10.10.10 or dst=67.59.219.85);"&lt;BR /&gt; monitor: getting filter (from command line)&lt;BR /&gt; monitor: compiling&lt;BR /&gt;monitorfilter:&lt;BR /&gt;Compiled OK.&lt;BR /&gt; monitor: loading&lt;BR /&gt; monitor: monitoring (control-C to stop)&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25622&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5055&lt;BR /&gt;[vs_0][fw_0] eth2:I[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25622&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5055&lt;BR /&gt;[vs_0][fw_0] eth7:o[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25622&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5055&lt;BR /&gt;[vs_0][fw_0] eth7:O[60]: 10.10.10.1 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25622&lt;BR /&gt;ICMP: type=8 code=0 echo request id=11777 seq=5055&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25629&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5056&lt;BR /&gt;[vs_0][fw_0] eth2:I[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25629&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5056&lt;BR /&gt;[vs_0][fw_0] eth7:o[60]: 172.12.7.60 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25629&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5056&lt;BR /&gt;[vs_0][fw_0] eth7:O[60]: 10.10.10.1 -&amp;gt; 10.10.10.10 (ICMP) len=60 id=25629&lt;BR /&gt;ICMP: type=8 code=0 echo request id=11777 seq=5056&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 67.59.219.85 (ICMP) len=60 id=25637&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5057&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 67.59.219.85 (ICMP) len=60 id=25661&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5058&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 67.59.219.85 (ICMP) len=60 id=25722&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5059&lt;BR /&gt;[vs_0][fw_1] eth1:i[60]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=60 id=25933&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 .S.... seq=ab88c547 ack=00000000&lt;BR /&gt;[vs_0][fw_1] eth1:I[60]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=60 id=25933&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 .S.... seq=ab88c547 ack=00000000&lt;BR /&gt;[vs_0][fw_1] eth7:o[60]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=60 id=25933&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 .S.... seq=ab88c547 ack=00000000&lt;BR /&gt;[vs_0][fw_1] eth7:O[60]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=60 id=25933&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 .S.... seq=ab88c547 ack=00000000&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25934&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25934&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25934&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25934&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth1:i[67]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=67 id=25935&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth1:I[67]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=67 id=25935&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth7:o[67]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=67 id=25935&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth7:O[67]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=67 id=25935&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c548 ack=249f57c8&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25936&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25936&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25936&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25936&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth1:i[700]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=700 id=25937&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth1:I[700]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=700 id=25937&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth7:o[700]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=700 id=25937&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth7:O[700]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=700 id=25937&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c557 ack=249f57ef&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25938&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25938&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25938&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25938&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth1:i[324]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=324 id=25939&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth1:I[324]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=324 id=25939&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth7:o[324]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=324 id=25939&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth7:O[324]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=324 id=25939&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c7df ack=249f5c27&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25940&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25940&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25940&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25940&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:i[68]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=68 id=25941&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:I[68]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=68 id=25941&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:o[68]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=68 id=25941&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:O[68]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=68 id=25941&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ef ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:i[104]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=104 id=25942&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ff ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:I[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25942&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ff ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:o[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25942&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ff ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth7:O[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25942&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c8ff ack=249f5f77&lt;BR /&gt;[vs_0][fw_1] eth1:i[120]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=120 id=25943&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c933 ack=249f5fab&lt;BR /&gt;[vs_0][fw_1] eth1:I[120]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=120 id=25943&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c933 ack=249f5fab&lt;BR /&gt;[vs_0][fw_1] eth7:o[120]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=120 id=25943&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c933 ack=249f5fab&lt;BR /&gt;[vs_0][fw_1] eth7:O[120]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=120 id=25943&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c933 ack=249f5fab&lt;BR /&gt;[vs_0][fw_1] eth1:i[152]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=152 id=25944&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c977 ack=249f5fef&lt;BR /&gt;[vs_0][fw_1] eth1:I[152]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=152 id=25944&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c977 ack=249f5fef&lt;BR /&gt;[vs_0][fw_1] eth7:o[152]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=152 id=25944&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c977 ack=249f5fef&lt;BR /&gt;[vs_0][fw_1] eth7:O[152]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=152 id=25944&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c977 ack=249f5fef&lt;BR /&gt;[vs_0][fw_0] eth2:i[60]: 172.12.7.60 -&amp;gt; 67.59.219.85 (ICMP) len=60 id=25754&lt;BR /&gt;ICMP: type=8 code=0 echo request id=1 seq=5060&lt;BR /&gt;[vs_0][fw_1] eth1:i[136]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=136 id=25945&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c9db ack=249f6033&lt;BR /&gt;[vs_0][fw_1] eth1:I[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25945&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c9db ack=249f6033&lt;BR /&gt;[vs_0][fw_1] eth7:o[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25945&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c9db ack=249f6033&lt;BR /&gt;[vs_0][fw_1] eth7:O[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25945&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88c9db ack=249f6033&lt;BR /&gt;[vs_0][fw_1] eth1:i[136]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=136 id=25946&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca2f ack=249f6077&lt;BR /&gt;[vs_0][fw_1] eth1:I[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25946&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca2f ack=249f6077&lt;BR /&gt;[vs_0][fw_1] eth7:o[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25946&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca2f ack=249f6077&lt;BR /&gt;[vs_0][fw_1] eth7:O[136]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=136 id=25946&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca2f ack=249f6077&lt;BR /&gt;[vs_0][fw_1] eth1:i[104]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=104 id=25947&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca83 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth1:I[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25947&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca83 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth7:o[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25947&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca83 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth7:O[104]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=104 id=25947&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ...PA. seq=ab88ca83 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25948&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 F...A. seq=ab88cab7 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25948&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 F...A. seq=ab88cab7 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25948&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 F...A. seq=ab88cab7 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25948&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 F...A. seq=ab88cab7 ack=249f60bb&lt;BR /&gt;[vs_0][fw_1] eth1:i[52]: 116.31.116.44 -&amp;gt; 67.59.219.85 (TCP) len=52 id=25949&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88cab8 ack=249f60bc&lt;BR /&gt;[vs_0][fw_1] eth1:I[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25949&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88cab8 ack=249f60bc&lt;BR /&gt;[vs_0][fw_1] eth7:o[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25949&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88cab8 ack=249f60bc&lt;BR /&gt;[vs_0][fw_1] eth7:O[52]: 116.31.116.44 -&amp;gt; 10.10.10.10 (TCP) len=52 id=25949&lt;BR /&gt;TCP: 51092 -&amp;gt; 22 ....A. seq=ab88cab8 ack=249f60bc&lt;BR /&gt; monitor: caught sig 2&lt;BR /&gt; monitor: unloading&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 12:08:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26151#M92599</guid>
      <dc:creator>Adam_Majka</dc:creator>
      <dc:date>2018-09-18T12:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26152#M92600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"&lt;SPAN style="color: #333333; background-color: #ffffff;"&gt;i dont need static routes becouse i dont have any other routers with other adresses in internal network." &amp;nbsp;??? can you clarify please ??? I'm lost now &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 13:23:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26152#M92600</guid>
      <dc:creator>Jerry</dc:creator>
      <dc:date>2018-09-18T13:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26153#M92601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i mean only default routes&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dest - default | next hope - normal | rank - 60 | gateways - eth1, eth3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 13:28:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26153#M92601</guid>
      <dc:creator>Adam_Majka</dc:creator>
      <dc:date>2018-09-18T13:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26154#M92602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Keep in mind that when you do a ping from the network the host is connected to, you will always get the untranslated packet back.&lt;/P&gt;&lt;P&gt;What do I mean by that?&lt;/P&gt;&lt;P&gt;You have a NAT setup for a host with IP 10.10.10.10 and you ping it from an other host with 10.10.10.11 --&amp;gt; works fine.&lt;/P&gt;&lt;P&gt;Now you ping the NAT address, the packet will go to the FW and will be returned to the same network but still with the same source, the return traffic will never go back to the FW as the source is now in the same network and the ping is not recognized as it still has the real IP's not the NAT IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your FW Monitor shows SSH working just fine by the way.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 14:02:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26154#M92602</guid>
      <dc:creator>Maarten_Sjouw</dc:creator>
      <dc:date>2018-09-18T14:02:34Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26155#M92603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;show us one thing Adam:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- show configuration static-route (clish)&lt;/P&gt;&lt;P&gt;- show configuration interface (clish) - hide real IP's.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 08:06:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26155#M92603</guid>
      <dc:creator>Jerry</dc:creator>
      <dc:date>2018-09-19T08:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26156#M92604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you have two manual NAT rules created on top of your NAT policy for:&lt;/P&gt;&lt;P&gt;LAN---DMZ---Any; Original, Original, Original&lt;/P&gt;&lt;P&gt;DMZ---LAN---Any; Original, Original, Original&lt;/P&gt;&lt;P&gt;?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 11:43:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26156#M92604</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-09-19T11:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26157#M92605</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no i don't&lt;/P&gt;&lt;P&gt;there are automatic NAT rules only.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 12:38:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26157#M92605</guid>
      <dc:creator>Adam_Majka</dc:creator>
      <dc:date>2018-09-19T12:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: WAN/LAN ping responding problem</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26158#M92606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well then, I suggest for you to add those and see if it'll change the behavior to your satisfaction.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 16:05:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/WAN-LAN-ping-responding-problem/m-p/26158#M92606</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-09-19T16:05:49Z</dc:date>
    </item>
  </channel>
</rss>

