<?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: Inter Vsys Routing in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/inter-vsys-routing/m-p/508956#M105925</link>
    <description>&lt;P&gt;you also need to create "external" type zones on each of the vsys and create security rules that allow packets to flow to and from the external zones&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;have you looked into service routes as that may be a lot easier&lt;/P&gt;</description>
    <pubDate>Thu, 14 Jul 2022 12:02:16 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2022-07-14T12:02:16Z</dc:date>
    <item>
      <title>Inter Vsys Routing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/inter-vsys-routing/m-p/508569#M105889</link>
      <description>&lt;P&gt;Can someone give me some advice please. In the attached diagram is a scenario I have where I need to get traffic logs from Virtual Firewall B across to Virtual Firewall A an up to the SIEM at the x.x.x.x address. I have made the virtual systems visible to each and added a route to x.x.x.x on virtual router B to go via virtual router A to get to x.x.x.x.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After adding a log forwarding action on the rules to send syslogs to x.x.x.x I'm seeing no traffic on either firewall destined for x.x.x.x. When using the route test command on the CLI to check the route all thats coming back is that it will use the default route to the internet rather than the route I configured. Can someone point out where I'm going wrong and/or how I would check for traffic to x.x.x.x please.&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
      <pubDate>Tue, 12 Jul 2022 16:00:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/inter-vsys-routing/m-p/508569#M105889</guid>
      <dc:creator>DaveErrington</dc:creator>
      <dc:date>2022-07-12T16:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: Inter Vsys Routing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/inter-vsys-routing/m-p/508956#M105925</link>
      <description>&lt;P&gt;you also need to create "external" type zones on each of the vsys and create security rules that allow packets to flow to and from the external zones&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;have you looked into service routes as that may be a lot easier&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 12:02:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/inter-vsys-routing/m-p/508956#M105925</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2022-07-14T12:02:16Z</dc:date>
    </item>
  </channel>
</rss>

