<?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 different initial sequence no. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571299#M601155</link>
    <description>&lt;P&gt;an asa housing a business application server sends out given syslogs quite often.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;419002: Duplicate TCP SYN from LOCAL:10.1.1.75/43415 to MILZONE:10.2.90.26/443 with different initial sequence number&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;this asa is on version 7.0(6) , cisco says it is common in these rel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there anything that ought to be inspected in view of this message. or to identify why it is throwing these messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 18:53:39 GMT</pubDate>
    <dc:creator>suthomas1</dc:creator>
    <dc:date>2019-03-11T18:53:39Z</dc:date>
    <item>
      <title>different initial sequence no.</title>
      <link>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571299#M601155</link>
      <description>&lt;P&gt;an asa housing a business application server sends out given syslogs quite often.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;419002: Duplicate TCP SYN from LOCAL:10.1.1.75/43415 to MILZONE:10.2.90.26/443 with different initial sequence number&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;this asa is on version 7.0(6) , cisco says it is common in these rel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there anything that ought to be inspected in view of this message. or to identify why it is throwing these messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:53:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571299#M601155</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2019-03-11T18:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: different initial sequence no.</title>
      <link>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571300#M601156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The explanation for this log message is that a duplicate TCP SYN was received during the three-way-handshake that has a different initial sequence number than the SYN that opened the embryonic connection. This could indicate that SYNs are being spoofed. Someone might be spoofing IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Namit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Oct 2010 03:42:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571300#M601156</guid>
      <dc:creator>Namit Agarwal</dc:creator>
      <dc:date>2010-10-13T03:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: different initial sequence no.</title>
      <link>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571301#M601157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if that is so, this LOCAL:10.1.1.75 ip belongs to interface of primary firewall before requests reach this server.&lt;/P&gt;&lt;P&gt;how should spoofing be checked if so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Oct 2010 03:45:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/different-initial-sequence-no/m-p/1571301#M601157</guid>
      <dc:creator>suthomas1</dc:creator>
      <dc:date>2010-10-13T03:45:09Z</dc:date>
    </item>
  </channel>
</rss>

