<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>tcpdump Tipps | SYN-FLUT.de</title>
	<atom:link href="https://www.syn-flut.de/en/thema/tcpdump/feed" rel="self" type="application/rss+xml" />
	<link>https://www.syn-flut.de/en/thema/tcpdump</link>
	<description>my Blog about Linux, Open Source, Cisco Network, UC and more...</description>
	<lastBuildDate>Tue, 30 Aug 2016 12:08:06 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.1</generator>

<image>
	<url>https://www.syn-flut.de/wp-content/uploads/2016/03/cropped-Favicon-1-32x32.png</url>
	<title>tcpdump Tipps | SYN-FLUT.de</title>
	<link>https://www.syn-flut.de/en/thema/tcpdump</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Traffic Capture on Cisco IOS</title>
		<link>https://www.syn-flut.de/en/traffic-capture-on-cisco-ios</link>
					<comments>https://www.syn-flut.de/en/traffic-capture-on-cisco-ios#respond</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Sat, 02 Apr 2016 19:31:45 +0000</pubDate>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Routing/Switching]]></category>
		<category><![CDATA[Router]]></category>
		<category><![CDATA[tcpdump]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://www.syn-flut.de/?p=155</guid>

					<description><![CDATA[<p>Here&#8217;s a quick how-to for a traffic capture on Cisco IOS routers. Interesting traffic at first, you have to create an access-list, which filters the traffic you want to capture. It is important to add entries for both &#8230; </p>
<div class="more-link-wrapper"><a href="https://www.syn-flut.de/en/traffic-capture-on-cisco-ios" class="more-link">Continue reading<span class="screen-reader-text"> "Traffic Capture on Cisco IOS"</span></a></div>
<p>Der Beitrag <a href="https://www.syn-flut.de/en/traffic-capture-on-cisco-ios">Traffic Capture on Cisco IOS</a> erschien zuerst auf <a href="https://www.syn-flut.de/en">SYN-FLUT.de</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Here&#8217;s a quick how-to for a traffic capture on Cisco IOS routers.<br />
<span id="more-155"></span></p>
<h2>Interesting traffic</h2>
<p>at first, you have to create an access-list, which filters the traffic you want to capture. It is important to add entries for both directions. In my example I want to capture every traffic which flows from and to the host 192.168.10.22</p>
<pre class="brush: cisco; title: ; notranslate">
conf t
access-list 144 permit ip host 192.168.10.22 any
access-list 144 permit ip any host 192.168.10.22
exit
</pre>
<h2>Creation of a Capture Buffer</h2>
<p>Now you have to create a Capture Buffer, which will save our captured packets. In my example its called <strong>C-BUFFER</strong> but you can name it whatever you want. In the next step, it will be linked to the previously-created access-list. In the example it has a size of 2 MB, current routers can save up to 10 MB. The packet size is defined with the command <strong>max-size</strong>. If you would use <strong>circular </strong>instead of <strong>linear</strong>, the buffer would get overwritten if it gets full.</p>
<pre class="brush: cisco; title: ; notranslate">
monitor capture buffer C-BUFFER size 2048 max-size 1518 linear
monitor capture buffer C-BUFFER filter access-list 144
</pre>
<h2>Creation of a Capture Point</h2>
<p>Now we have to create a Capture Point and link it with the previously-created Buffer. The keyword <strong>both</strong> means that we capture traffic in both directions. We have to differentiate between <strong>cef</strong> traffic and <strong>process-switched</strong> traffic. Nowadays, as good as every packet which flows through a router is <strong>cef</strong>-switched. (<a href="https://en.wikipedia.org/wiki/Cisco_Express_Forwarding" target="_blank">Cisco Express Forwarding</a>). This is why we use the <strong>cef</strong> keyword in the command. If you want to capture traffic, which is destined for the router, or fragmented packets, then you would have to use the <strong>process-switched</strong> command. This line is commented out in my example.</p>
<pre class="brush: cisco; title: ; notranslate">
monitor capture point ip cef C-POINT all both
!monitor capture point ip process-switched C-POINT both
monitor capture point associate C-POINT C-BUFFER
</pre>
<h2>Start of the capture</h2>
<p>with this command, the capture will be started. Now create the traffic you want to capture.</p>
<pre class="brush: cisco; title: ; notranslate">
monitor capture point start C-POINT
</pre>
<h2>Stop of the capture</h2>
<p>If the traffic is captured, you have to stop the running capture on the router. In the next step, the data is exported as <strong>pcap</strong>, so it can be viewed with for example Wireshark.</p>
<pre class="brush: cisco; title: ; notranslate">
monitor capture point stop C-POINT
monitor capture buffer C-BUFFER export tftp://1.2.3.4/filename.pcap
</pre>
<h2>Cleanup</h2>
<p>You have the traffic you want in the pcap? Time to clean up the router.</p>
<pre class="brush: cisco; title: ; notranslate">
!no monitor capture point ip process-switched C-POINT both
no monitor capture point ip cef C-POINT all both
no monitor capture buffer C-BUFFER
conf t
no access-list 144
exit
</pre>
<h2>Whole configuration</h2>
<p>for all who just quickly needs the commands as a reference:</p>
<pre class="brush: cisco; title: ; notranslate">
conf t
access-list 144 permit ip host 192.168.10.22 any
access-list 144 permit ip any host 192.168.10.22
exit
monitor capture buffer C-BUFFER&amp;amp;amp;nbsp;size 2048 max-size 1518 linear
monitor capture buffer C-BUFFER filter access-list 144
monitor capture point ip cef C-POINT all both
!monitor capture point ip process-switched C-POINT both
monitor capture point associate C-POINT C-BUFFER
monitor capture point start C-POINT
!---
! Traffic produzieren
!---
monitor capture point stop C-POINT
monitor capture buffer C-BUFFER export tftp://1.2.3.4/filename.pcap
!----
!no monitor capture point ip process-switched C-POINT both
no monitor capture point ip cef C-POINT all both
no monitor capture buffer C-BUFFER
conf t
no access-list 144
exit
</pre>
<p>Der Beitrag <a href="https://www.syn-flut.de/en/traffic-capture-on-cisco-ios">Traffic Capture on Cisco IOS</a> erschien zuerst auf <a href="https://www.syn-flut.de/en">SYN-FLUT.de</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.syn-flut.de/en/traffic-capture-on-cisco-ios/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
