<?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: Getting Syslog in through PA 500 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45417#M33386</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi...TWC-NPM was given IP &lt;STRONG&gt;197&lt;/STRONG&gt;.148.156.150, and the traffic log reported destination &lt;STRONG&gt;198&lt;/STRONG&gt;.148.156.150.&amp;nbsp; Could it be the router is pointing to the wrong IP for the syslog server?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 02 Jun 2012 20:47:49 GMT</pubDate>
    <dc:creator>rmonvon</dc:creator>
    <dc:date>2012-06-02T20:47:49Z</dc:date>
    <item>
      <title>Getting Syslog in through PA 500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45416#M33385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a router just outside my PAN 500, ver 4.0.5. I need to get syslog information in from it for my PCI requirements. Here is my setup:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following objects are defined:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INT-NPM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Syslog server, IP address 172.15.10.8&lt;/P&gt;&lt;P&gt;TWC-RTR&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Router, 197.148.156.124&lt;/P&gt;&lt;P&gt;TWC-NPM&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; NAT address for INT-NPM, 197.148.156.150&lt;/P&gt;&lt;P&gt;TWC-NAT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Internal NAT for TWC internet comm; 197.148.156.253&lt;/P&gt;&lt;P&gt;Services: Syslog: 514/TCP and Syslog-UDP: 514/UDP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following policies are defined:&lt;/P&gt;&lt;P&gt;NAT:&lt;/P&gt;&lt;P&gt;Internal to External, no dest int, Source INT-NPM, any dest, any service, IP: static-ip, Translated Address: TWC-NPM, BI-dir YES.&lt;/P&gt;&lt;P&gt;Security:&lt;/P&gt;&lt;P&gt;External to ANY, User ANY, HIP Profile ANY, Dest zone Internal, address WTC-NPM, Any application, both Syslog services, action ALLOW&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I get in the traffic log when I force a change that results in a syslog-able event, is this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Time, drop, frm External, to Internal, source 197.148.156.124, destination 197.148.156.150, to port 514, action deny.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea what I am doing wrong? I had it setup the same as my exchange server (different services) but it always seemed ot deny the traffic (falling down to my catch-all rule). I've tried teh destination as the external NAT address and teh internal address in the security rule: neither seems to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Message was edited by: &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:rhanna@lamadeleine.com"&gt;rhanna@lamadeleine.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jun 2012 18:01:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45416#M33385</guid>
      <dc:creator>u7483</dc:creator>
      <dc:date>2012-06-01T18:01:26Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Syslog in through PA 500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45417#M33386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi...TWC-NPM was given IP &lt;STRONG&gt;197&lt;/STRONG&gt;.148.156.150, and the traffic log reported destination &lt;STRONG&gt;198&lt;/STRONG&gt;.148.156.150.&amp;nbsp; Could it be the router is pointing to the wrong IP for the syslog server?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Jun 2012 20:47:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45417#M33386</guid>
      <dc:creator>rmonvon</dc:creator>
      <dc:date>2012-06-02T20:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Syslog in through PA 500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45418#M33387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunatyely that was me mis-typing the IP address here, not in the PA. Sorry.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Jun 2012 14:25:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45418#M33387</guid>
      <dc:creator>u7483</dc:creator>
      <dc:date>2012-06-08T14:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: Getting Syslog in through PA 500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45419#M33388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your NAT and security rules appear to be correct.&amp;nbsp; I recommend you contact Support and open a case.&amp;nbsp; Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Jun 2012 14:35:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/getting-syslog-in-through-pa-500/m-p/45419#M33388</guid>
      <dc:creator>rmonvon</dc:creator>
      <dc:date>2012-06-08T14:35:48Z</dc:date>
    </item>
  </channel>
</rss>

