<?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 TCP Reset not working in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459899#M100157</link>
    <description>&lt;P&gt;I have my man-port on vlan 2 this is our MGT vlan we do not use vlan 1, tcpreset is not work. Below is the step I did to set it up&lt;/P&gt;&lt;P&gt;1 vlan 1 is up but no ip address on this due to vlan 2 is MGT IP&lt;/P&gt;&lt;P&gt;2 I have the man-port on vlan 2&lt;/P&gt;&lt;P&gt;intrusion-detection module 9 management-port access-vlan 2&lt;/P&gt;&lt;P&gt;3 I ran the tcpdump and noting came back go a pars error.&lt;/P&gt;&lt;P&gt;can anyone shed light on my problems I'm not sure I have everything config right.&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;&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 09:42:54 GMT</pubDate>
    <dc:creator>jlwomeld</dc:creator>
    <dc:date>2019-03-10T09:42:54Z</dc:date>
    <item>
      <title>TCP Reset not working</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459899#M100157</link>
      <description>&lt;P&gt;I have my man-port on vlan 2 this is our MGT vlan we do not use vlan 1, tcpreset is not work. Below is the step I did to set it up&lt;/P&gt;&lt;P&gt;1 vlan 1 is up but no ip address on this due to vlan 2 is MGT IP&lt;/P&gt;&lt;P&gt;2 I have the man-port on vlan 2&lt;/P&gt;&lt;P&gt;intrusion-detection module 9 management-port access-vlan 2&lt;/P&gt;&lt;P&gt;3 I ran the tcpdump and noting came back go a pars error.&lt;/P&gt;&lt;P&gt;can anyone shed light on my problems I'm not sure I have everything config right.&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;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:42:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459899#M100157</guid>
      <dc:creator>jlwomeld</dc:creator>
      <dc:date>2019-03-10T09:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset not working</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459900#M100183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure what you are asking.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sounds like you may be confusing the management port with TCP Reset event action for signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TCP Reset packets as event actions for signatures will not be sent out of the management port.  They are sent out a TCP Reset port.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TCP Reset port is not user configurable or even viewable in Native IOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The configuration you need to worry about is not the management-port but instead the data-ports of the IDSM-2.  The data-ports need to be properly configured to monitor the traffic you want to execute the TCP Resets on,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2005 13:58:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459900#M100183</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2005-10-27T13:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Reset not working</title>
      <link>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459901#M100213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I ran the following command on my sensor and I am getting no data back&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[root@CARL122IDSMONS sbin]# ./tcpdump -i eth1 src host 144.xxx.xxx.xxx(i removed the IP's)&lt;/P&gt;&lt;P&gt;tcpdump: WARNING: eth1: no IPv4 address assigned&lt;/P&gt;&lt;P&gt;tcpdump: listening on eth1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;does this mean my TCP reset is not working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2005 16:56:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-reset-not-working/m-p/459901#M100213</guid>
      <dc:creator>jlwomeld</dc:creator>
      <dc:date>2005-10-27T16:56:57Z</dc:date>
    </item>
  </channel>
</rss>

