<?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: VSX Virtual Router Issue in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11452#M1748</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I faced the same issue in my lab, I have two VS both external interface is connected with a virtual router, I able to reach to the virtual router but not getting the internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The virtual router is getting internet, I try to do with netting on VS with virtual&amp;nbsp;router IP but policy failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is any document related to this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone help me to understand it?&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="color: #333333; background-color: #ffffff;"&gt;Well, it particular cases VSX entities are using non-routable IP addresses that just cannot be returned to the original source.&lt;/SPAN&gt;"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Jan 2019 14:54:33 GMT</pubDate>
    <dc:creator>Happy__</dc:creator>
    <dc:date>2019-01-09T14:54:33Z</dc:date>
    <item>
      <title>VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11447#M1743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have an issue regarding VSX and the implementation of ClusterXL combined with a virtual router. I've created a lab setup (see attachment) and did some testing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internet connectivity on the EDGE router is verified:&lt;/P&gt;&lt;P&gt;1: I can ping 8.8.8.8 and google.com from my EDGE router&lt;/P&gt;&lt;P&gt;2: When I connect my client directly to my EDGE router i can also ping 8.8.8.8 and google.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Connectivity from the client:&lt;/P&gt;&lt;P&gt;Ping from&amp;nbsp;Client to 192.168.20.3 (Virtual System) is successful&lt;/P&gt;&lt;P&gt;Ping from&amp;nbsp;&lt;SPAN&gt;Client&lt;/SPAN&gt; to 192.168.1.2 (Virtual Router) is successful&lt;/P&gt;&lt;P&gt;Ping from&amp;nbsp;&lt;SPAN&gt;Client&lt;/SPAN&gt; to 192.168.1.1 (EDGE Router) is not successful&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping from Client to&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;8.8.8.8 and google.com is not successful (obviously)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Connectivity from the virtual router (login to corresponding Virtual System ID of the router)&lt;/P&gt;&lt;P&gt;Ping from Virtual Router to 192.168.1.1 (EDGE Router) is successful&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping from Virtual Router to&amp;nbsp;8.8.8.8 and google.com is successful&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping from Virtual Router to 192.168.10.3 (Virtual System) is successful&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping from Virtual Router to 192.168.20.4 (Client) is successful&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It looks like the Virtual Router can connect to every part of the network but from the client I'm not able to get past the Virtual Router.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does anyone know what I'm missing here?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2018 13:58:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11447#M1743</guid>
      <dc:creator>Pim_Dimmedal</dc:creator>
      <dc:date>2018-10-30T13:58:49Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11448#M1744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are missing the NAT for VS IP address &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; It is most probably pinging 8.8.8.8 with a funny IP address which is not routed back. Run fw monitor to prove&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2018 16:04:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11448#M1744</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2018-10-30T16:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11449#M1745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will run fw monitor tonight, but I'm using NAT on my EDGE router so I don't see the need to NAT on the VS as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2018 16:07:59 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11449#M1745</guid>
      <dc:creator>Pim_Dimmedal</dc:creator>
      <dc:date>2018-10-30T16:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11450#M1746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it particular cases VSX entities are using non-routable IP addresses that just cannot be returned to the original source. Start there, see where it fails, and then, if that was not the case, we can move further&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2018 16:17:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11450#M1746</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2018-10-30T16:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11451#M1747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've found the issue. It seemed something was wrong with the route back from the EDGE to the Virtual Router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your suggestion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2018 17:00:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11451#M1747</guid>
      <dc:creator>Pim_Dimmedal</dc:creator>
      <dc:date>2018-10-30T17:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11452#M1748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I faced the same issue in my lab, I have two VS both external interface is connected with a virtual router, I able to reach to the virtual router but not getting the internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The virtual router is getting internet, I try to do with netting on VS with virtual&amp;nbsp;router IP but policy failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is any document related to this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone help me to understand it?&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="color: #333333; background-color: #ffffff;"&gt;Well, it particular cases VSX entities are using non-routable IP addresses that just cannot be returned to the original source.&lt;/SPAN&gt;"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jan 2019 14:54:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11452#M1748</guid>
      <dc:creator>Happy__</dc:creator>
      <dc:date>2019-01-09T14:54:33Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11453#M1749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for the late reply. Have you defined a route on the virtual router to both virtual systems, and a default route on both virtual systems to the virtual router?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2019 19:28:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11453#M1749</guid>
      <dc:creator>Pim_Dimmedal</dc:creator>
      <dc:date>2019-02-12T19:28:19Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Virtual Router Issue</title>
      <link>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11454#M1750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I defined the default route is a virtual router for both VS and also defined routes on VR for reverse.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Feb 2019 19:34:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/VSX-Virtual-Router-Issue/m-p/11454#M1750</guid>
      <dc:creator>Happy__</dc:creator>
      <dc:date>2019-02-12T19:34:36Z</dc:date>
    </item>
  </channel>
</rss>

