<?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 Pix syslog question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-syslog-question/m-p/82149#M687945</link>
    <description>&lt;P&gt;I'm in the process of moving the configuration and&lt;/P&gt;&lt;P&gt;external services for my pix firewalls. An issue I'm&lt;/P&gt;&lt;P&gt;tring to fix is the syslog coming from the pix firewall.Right now my pix is using the default of UDP syslog to a Unix syslog deamon. This has been working fine however, I'd like to migrate the syslog on the pix to use the TCP protocol instead of the UPD protocol as is the case now. My pix is running a current enough version to support this option. I guess the bottom line question is will the syslog-ng package compiled and installed on my Solaris box provide this TCP based syslog functionallity? If so, this will prevent me from having to replace my Solaris system with an NT box running the Cisco TCP syslog service. Any information appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 05:51:33 GMT</pubDate>
    <dc:creator>jbigrow</dc:creator>
    <dc:date>2020-02-21T05:51:33Z</dc:date>
    <item>
      <title>Pix syslog question</title>
      <link>https://community.cisco.com/t5/network-security/pix-syslog-question/m-p/82149#M687945</link>
      <description>&lt;P&gt;I'm in the process of moving the configuration and&lt;/P&gt;&lt;P&gt;external services for my pix firewalls. An issue I'm&lt;/P&gt;&lt;P&gt;tring to fix is the syslog coming from the pix firewall.Right now my pix is using the default of UDP syslog to a Unix syslog deamon. This has been working fine however, I'd like to migrate the syslog on the pix to use the TCP protocol instead of the UPD protocol as is the case now. My pix is running a current enough version to support this option. I guess the bottom line question is will the syslog-ng package compiled and installed on my Solaris box provide this TCP based syslog functionallity? If so, this will prevent me from having to replace my Solaris system with an NT box running the Cisco TCP syslog service. Any information appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 05:51:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-syslog-question/m-p/82149#M687945</guid>
      <dc:creator>jbigrow</dc:creator>
      <dc:date>2020-02-21T05:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Pix syslog question</title>
      <link>https://community.cisco.com/t5/network-security/pix-syslog-question/m-p/82150#M687969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would imagine that your unix host would be able to handle that without a problem...should just be a matter of modifying your services file and inetd.conf files.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Oct 2001 14:28:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-syslog-question/m-p/82150#M687969</guid>
      <dc:creator>awilliamson</dc:creator>
      <dc:date>2001-10-09T14:28:27Z</dc:date>
    </item>
  </channel>
</rss>

