<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>dacaprice.com</title>
	
	<link>http://www.dacaprice.com</link>
	<description>from fitness to technology. mostly technology. sometimes fitness.</description>
	<lastBuildDate>Fri, 20 Jan 2012 15:29:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/dacaprice" /><feedburner:info uri="dacaprice" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>dacaprice</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Rotating files with tcpdump</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/UWRF7y_Mg9o/</link>
		<comments>http://www.dacaprice.com/2012/01/20/rotating-files-with-tcpdump/#comments</comments>
		<pubDate>Fri, 20 Jan 2012 15:29:51 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=883</guid>
		<description><![CDATA[tcpdump -s 0 port 80 -C 10 -w /tmp/capture.pcap The above command captures complete packets (-s 0) and writes them to /tmp/capture.pcap.  The -C 10 tells tcpdump to rotate the .pcap files out when they reach 10MB in size.  So capture.pcap would be the original, followed by capture.pcap1, capture.pcap2, etc. One important note:  tcpdump drops [...]]]></description>
			<content:encoded><![CDATA[<pre>tcpdump -s 0 port 80 -C 10 -w /tmp/capture.pcap</pre>
<p>The above command captures complete packets (-s 0) and writes them to /tmp/capture.pcap.  The -C 10 tells tcpdump to rotate the .pcap files out when they reach 10MB in size.  So capture.pcap would be the original, followed by capture.pcap1, capture.pcap2, etc.</p>
<p>One important note:  tcpdump drops permissions when you use the -C, so make sure you write to a directory that is world-writable.</p>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/UWRF7y_Mg9o" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2012/01/20/rotating-files-with-tcpdump/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2012/01/20/rotating-files-with-tcpdump/</feedburner:origLink></item>
		<item>
		<title>Cisco router ACL helper perl script</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/82zTYurcfKk/</link>
		<comments>http://www.dacaprice.com/2011/09/01/cisco-router-acl-helper-perl-script/#comments</comments>
		<pubDate>Thu, 01 Sep 2011 22:29:47 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[perl]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=871</guid>
		<description><![CDATA[I am not a skilled programmer/scripter.  Here's a Perl script I wrote that takes the inbound rules for an access list on a Cisco router and spits out the corresponding rules for the outbound list.  It's still a work-in-progess. UPDATE 09/07/11: slightly modified regular expression to better match different ACL syntax. #!/usr/bin/perl -w # cisco_router_aclgen.pl [...]]]></description>
			<content:encoded><![CDATA[<p>I am not a skilled programmer/scripter.  Here's a Perl script I wrote that takes the inbound rules for an access list on a Cisco router and spits out the corresponding rules for the outbound list.  It's still a work-in-progess.</p>
<p>UPDATE 09/07/11: slightly modified regular expression to better match different ACL syntax.</p>
<pre>#!/usr/bin/perl -w
# cisco_router_aclgen.pl
# needs to handle resolvable ports (ntp instead of 123, dns 53, ssh 22, etc);

@inbound = ();
@outbound = ();
@invalid = ();

system "clear";   # clear the terminal screen

print "\n\n\t\tEnter your inbound ACL rules. Type end when finished or ^c to quit.\n";    # present user with prompt
while (&lt;STDIN&gt;) {   # loops through user input
  $inbound = $_;
  last if /^end$|^END$/;
     if ( $inbound =~ m/(no\ permit|permit)(\ ip|\ icmp|\ tcp|\ udp)(\ any|(\ host|\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})(\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))(\ any|(\ host|\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})(\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?(\ eq\ \d{1,5}|\ range\ \d{1,5}\ \d{1,5}|\ any)(|\ log)$/ ) {
     $prefix = "$1$2";
     $src = "$3";
     $dst = "$6";
     #$ports = "$9";
     $ports = "$9";
     $outbound = "$prefix$dst$ports$src\n";
     print "1=$1, 2=$2, 3=$3, 4=$4, 5=$5, 6=$6, 7=$7, 8=$8, 9=$9, 10=$10, 11=$11, 12=$12, 13=$13\n";   # left in for debugging
     push @inbound, "$inbound";
     push @outbound, "$outbound";
       }  elsif ( $inbound =~ m/(no\ permit|permit)(\ ip|\ icmp|\ tcp|\ udp)(\ any|(\ host|\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})(\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))?(\ eq\ \d{1,5}|\ range\ \d{1,5}\ \d{1,5}|\ any)(\ any|(\ host|\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})(\ \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}))(|\ log)$/ ) {
     $prefix = "$1$2";
     $src = "$3";
     $ports = "$6";
     $dst = "$7";
     $outbound = "$prefix$dst$src$ports\n";
     print "1=$1, 2=$2, 3=$3, 4=$4, 5=$5, 6=$6, 7=$7, 8=$8, 9=$9, 10=$10, 11=$11, 12=$12, 13=$13\n";   # left in for debugging
     push @inbound, "$inbound";
     push @outbound, "$outbound";
       }  elsif ( $inbound =~ m/^\!\n$|remark.*/ )  {
          push @inbound, "$inbound";
          push @outbound, "$inbound";
          }
       else {
       push @invalid, "$inbound";
       }
    }
system "clear";   # clear the terminal screen
print "\n\tWhat is the name of the INBOUND access list?\n\n";
   $acl_in_name = &lt;&gt;;
print "\n\tWhat is the name of the OUTBOUND access list?\n\n";
   $acl_out_name = &lt;&gt;;
system "clear";   # clear the terminal screen
print "#" x 100;
print "\n\nconfig t \nip access-list extended $acl_in_name";
    for $inbound (@inbound) {
      print "$inbound";
    }
print "no deny ip any any log\ndeny ip any any log\n\!\n\nip access-list extended $acl_out_name";
    for $outbound (@outbound) {
      print "$outbound";
    }
print "no deny ip any any log\ndeny ip any any log\nend\n\n";
print "#" x 100;
    if ( @invalid ) {
      print "\n\nThe following lines were not included in the access list because they do not follow normal ACL syntax:\n\n";
        for $invalid (@invalid) {
        print "\t$invalid";
        }
    }
print "\n" x 5;</pre>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/82zTYurcfKk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/09/01/cisco-router-acl-helper-perl-script/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/09/01/cisco-router-acl-helper-perl-script/</feedburner:origLink></item>
		<item>
		<title>Create a 100Mb file in Linux</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/AL3GLOIoeIw/</link>
		<comments>http://www.dacaprice.com/2011/08/16/create-a-100mb-file-in-linux/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 02:41:18 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=864</guid>
		<description><![CDATA[I recently needed to create a 100 Mb file to do some testing.  It didn't matter what was in it, I just needed a file of that specific size. I created it with the following command: dd if=/dev/random of=filename bs=1024 count=102400 The options are as follows: if = the source of the input of = [...]]]></description>
			<content:encoded><![CDATA[<p>I recently needed to create a 100 Mb file to do some testing.  It didn't matter what was in it, I just needed a file of that specific size.</p>
<p>I created it with the following command:</p>
<div title="Click to select this command">
<pre>dd if=/dev/random of=filename bs=1024 count=102400</pre>
<p>The options are as follows:</p>
<p>if = the source of the input</p>
<p>of = output file name</p>
<p>bs = in this case this sets the block size</p>
<p>count = the number of blocks to copy in the file</p>
<p>Multiply the number of blocks (count) times the size (bs) to calculate the size of the file (in bytes).</p>
</div>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/AL3GLOIoeIw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/08/16/create-a-100mb-file-in-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/08/16/create-a-100mb-file-in-linux/</feedburner:origLink></item>
		<item>
		<title>Basic DNS troubleshooting with dig</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/eJgNes1sCP8/</link>
		<comments>http://www.dacaprice.com/2011/08/09/basic-dns-troubleshooting-with-dig/#comments</comments>
		<pubDate>Wed, 10 Aug 2011 02:20:39 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=853</guid>
		<description><![CDATA[I don't usually end up troubleshooting DNS issues, but one thing led to another recently and I ended up elbows deep in DNS troubles.  I spent a good portion of my day on telcons with one party who actually administers the DNS servers for this client, and Akamai.  I did walk away with a better understanding of how Akamai works and basic DNS querying using the dig command in Linux. 

The following shows the DNS equivalent of a traceroute.  Notice that is starts "tracing" the name from right to left, starting with the DNS root servers, then the .com, and so on.]]></description>
			<content:encoded><![CDATA[<p>I don't usually end up troubleshooting DNS issues, but one thing led to another recently and I ended up elbows deep in DNS troubles.  I spent a good portion of my day on telcons with one party who actually administers the DNS servers for this client, and <a href="http://en.wikipedia.org/wiki/Akamai_Technologies" target="_blank">Akamai</a>.  I did walk away with a better understanding of how Akamai works and basic DNS querying using the <a href="http://linux.die.net/man/1/dig" target="_blank">dig</a> command in Linux.</p>
<p>The following shows the DNS equivalent of a traceroute.  Notice that is starts "tracing" the name from right to left, starting with the <a href="http://en.wikipedia.org/wiki/Root_name_server" target="_blank">DNS root servers</a>, then the .com, and so on.</p>
<pre>[dacaprice@linux ~]$ dig dacaprice.com +trace

; &lt;&lt;&gt;&gt; DiG 9.7.4b1-RedHat-9.7.4-0.3.b1.fc14 &lt;&lt;&gt;&gt; dacaprice.com +trace
;; global options: +cmd
.            518400    IN    NS    a.root-servers.net.
.            518400    IN    NS    b.root-servers.net.
.            518400    IN    NS    c.root-servers.net.
.            518400    IN    NS    d.root-servers.net.
.            518400    IN    NS    e.root-servers.net.
.            518400    IN    NS    f.root-servers.net.
.            518400    IN    NS    g.root-servers.net.
.            518400    IN    NS    h.root-servers.net.
.            518400    IN    NS    i.root-servers.net.
.            518400    IN    NS    j.root-servers.net.
.            518400    IN    NS    k.root-servers.net.
.            518400    IN    NS    l.root-servers.net.
.            518400    IN    NS    m.root-servers.net.
;; Received 228 bytes from 208.67.220.220#53(208.67.220.220) in 273 ms

com.            172800    IN    NS    k.gtld-servers.net.
com.            172800    IN    NS    i.gtld-servers.net.
com.            172800    IN    NS    j.gtld-servers.net.
com.            172800    IN    NS    b.gtld-servers.net.
com.            172800    IN    NS    l.gtld-servers.net.
com.            172800    IN    NS    h.gtld-servers.net.
com.            172800    IN    NS    e.gtld-servers.net.
com.            172800    IN    NS    m.gtld-servers.net.
com.            172800    IN    NS    c.gtld-servers.net.
com.            172800    IN    NS    d.gtld-servers.net.
com.            172800    IN    NS    g.gtld-servers.net.
com.            172800    IN    NS    a.gtld-servers.net.
com.            172800    IN    NS    f.gtld-servers.net.
;; Received 491 bytes from 192.112.36.4#53(192.112.36.4) in 386 ms

dacaprice.com.        172800    IN    NS    ns1.comphouse.com.
dacaprice.com.        172800    IN    NS    ns2.comphouse.com.
;; Received 109 bytes from 192.41.162.30#53(192.41.162.30) in 70 ms

dacaprice.com.        14400    IN    A    72.32.185.230
dacaprice.com.        86400    IN    NS    ns2.comphouse.com.
dacaprice.com.        86400    IN    NS    ns1.comphouse.com.
;; Received 125 bytes from 72.32.185.230#53(72.32.185.230) in 50 ms</pre>
<p>The next section illustrates how to query a specific DNS server.  In this case I queried ns2.comphouse.com (an authority for dacaprice.com).  The output shows the authoritative nameservers for dacaprice.com, the A record, mapping the name, dacaprice.com, to the IP address of the webserver and various other query-related statistics.</p>
<pre>[dacaprice@linux ~]$ dig @ns2.comphouse.com dacaprice.com

; &lt;&lt;&gt;&gt; DiG 9.7.4b1-RedHat-9.7.4-0.3.b1.fc14 &lt;&lt;&gt;&gt; @ns2.comphouse.com dacaprice.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 42212
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;dacaprice.com.            IN    A

;; ANSWER SECTION:
dacaprice.com.        14400    IN    A    72.32.185.230

;; AUTHORITY SECTION:
dacaprice.com.        86400    IN    NS    ns2.comphouse.com.
dacaprice.com.        86400    IN    NS    ns1.comphouse.com.

;; ADDITIONAL SECTION:
ns1.comphouse.com.    14400    IN    A    72.32.185.230
ns2.comphouse.com.    14400    IN    A    67.192.225.138

;; Query time: 52 msec
;; SERVER: 67.192.225.138#53(67.192.225.138)
;; WHEN: Tue Aug  9 22:07:10 2011
;; MSG SIZE  rcvd: 125
</pre>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/eJgNes1sCP8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/08/09/basic-dns-troubleshooting-with-dig/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/08/09/basic-dns-troubleshooting-with-dig/</feedburner:origLink></item>
		<item>
		<title>Check CPU architecture</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/Xd7l-lc4xTE/</link>
		<comments>http://www.dacaprice.com/2011/07/26/check_cpu_architectur/#comments</comments>
		<pubDate>Tue, 26 Jul 2011 12:01:16 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=848</guid>
		<description><![CDATA[dmidecode is a linux tool for dumping a computer's DMI table contents in a human-readable format.  To verify processor architecture information type the following command as root: [root@linux]# dmidecode --type processor Processor can be substituted for other options such as: bios, system, baseboard, chassis, memory, cache, connector, or slot.  In the past, I've also used [...]]]></description>
			<content:encoded><![CDATA[<p><em>dmidecode</em> is a linux tool for dumping a computer's DMI table contents in a human-readable format.  To verify processor architecture information type the following command as root:</p>
<pre>[root@linux]# dmidecode --type processor</pre>
<p><em>Processor</em> can be substituted for other options such as: bios, system, baseboard, chassis, memory, cache, connector, or slot.  In the past, I've also used dmidecode (with the chassis option) to snag the serial number off of a remote machine to call in for a warranty repair.</p>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/Xd7l-lc4xTE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/07/26/check_cpu_architectur/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/07/26/check_cpu_architectur/</feedburner:origLink></item>
		<item>
		<title>Boot Cisco router from rommon</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/QLaKHnESUis/</link>
		<comments>http://www.dacaprice.com/2011/07/20/boot-cisco-router-from-rommon/#comments</comments>
		<pubDate>Wed, 20 Jul 2011 09:40:53 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=811</guid>
		<description><![CDATA[I work with some legacy Cisco routers that will occasionally boot into rommon after a power outage or scheduled reboot.  It's almost as if the router can't locate the flash memory to load the correct IOS.  Luckily I have out-of-band console access so I can tell it where to find the IOS.bin: rommon 5 &#62; [...]]]></description>
			<content:encoded><![CDATA[<p>I work with some legacy Cisco routers that will occasionally boot into rommon after a power outage or scheduled reboot.  It's almost as if the router can't locate the flash memory to load the correct IOS.  Luckily I have out-of-band console access so I can tell it where to find the IOS.bin:</p>
<pre>rommon 5 &gt; boot flash:IOS_file.bin</pre>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/QLaKHnESUis" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/07/20/boot-cisco-router-from-rommon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/07/20/boot-cisco-router-from-rommon/</feedburner:origLink></item>
		<item>
		<title>dump packets with tcpdump</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/jVA7kQAvalc/</link>
		<comments>http://www.dacaprice.com/2011/05/24/dump-packets-with-tcpdump/#comments</comments>
		<pubDate>Tue, 24 May 2011 17:55:41 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=805</guid>
		<description><![CDATA[I always forget the parameters for this and have to look them up in the man page, so enough of that: tcpdump -nnXSs 0 host hostname (or IP) "-nn" makes it not lookup hostnames in DNS and service names (in /etc/services) for respectively faster and cleaner output. "-X" makes it print each packet in hex [...]]]></description>
			<content:encoded><![CDATA[<p>I always forget the parameters for this and have to look them up in the man page, so enough of that:</p>
<pre> tcpdump -nnXSs 0 host <em>hostname (or IP)</em></pre>
<ul>
<li>"-nn" makes it not lookup hostnames in DNS and service names (in /etc/services) for respectively faster and cleaner output.</li>
<li>"-X" makes it print each packet in hex and ascii; that's really the useful bit for tracking headers and such</li>
<li>"-S" print absolute rather than relative TCP sequence numbers - If I  remember right this is so you can compare tcpdump outputs from multiple  users doing this at once</li>
<li>"-s 0" by default tcpdump will only capture the beginning of each packet, using 0 here will make it capture the full packets.</li>
</ul>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/jVA7kQAvalc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/05/24/dump-packets-with-tcpdump/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/05/24/dump-packets-with-tcpdump/</feedburner:origLink></item>
		<item>
		<title>Cisco IOS Keyboard Shortcuts</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/Hs1z6WOBUGw/</link>
		<comments>http://www.dacaprice.com/2011/05/20/cisco-ios-keyboard-shortcuts/#comments</comments>
		<pubDate>Fri, 20 May 2011 13:44:32 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=802</guid>
		<description><![CDATA[Below the complete list of the IOS shortcuts: Ctrl+T: Swap the current character with the one before it Ctrl+K: Erase all characters from the current cursor position to the end of the line Ctrl+X: Erase all characters from the current cursor position to the beginning of the line Ctrl+L: Reprint the line Ctrl+C: Exit configuration [...]]]></description>
			<content:encoded><![CDATA[<p>Below the complete list of the IOS shortcuts:</p>
<p><strong>Ctrl+T</strong>: Swap the current character with the one before it<br />
<strong>Ctrl+K</strong>: Erase all characters from the current cursor position to the end of the line<br />
<strong>Ctrl+X</strong>: Erase all characters from the current cursor position to the beginning of the line<strong><br />
Ctrl+L</strong>: Reprint the line<br />
<strong>Ctrl+C</strong>: Exit configuration mode<br />
<strong>Ctrl+A</strong>: Moves the cursor to the beginning of the current line<br />
<strong>Ctrl+E</strong>: Moves the cursor to the end of the current line<br />
<strong>Ctrl+F</strong>: Moves forward one character<br />
<strong>Ctrl+B</strong>: Moves backwards one character<br />
<strong>Ctrl+R</strong>: Redisplays a line (starts a new line, with the same command shown)<br />
<strong>Ctrl+U</strong>: Erases a line<br />
<strong>Ctrl+W</strong>: Erases a word<br />
<strong>Ctrl+Z</strong>: Exits configuration mode, returning you to privileged EXEC mode<br />
<strong>Ctrl+P (or up arrow)</strong>: Displays the last command entered<br />
<strong>Ctrl+N (or down arrow)</strong>: Displays previous commands entered<br />
<strong>Tab</strong>: Completes a partial command<br />
<strong>Esc, F</strong>: Moves forward one word<br />
<strong>Esc, B</strong>: Moves backwards one word</p>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/Hs1z6WOBUGw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/05/20/cisco-ios-keyboard-shortcuts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/05/20/cisco-ios-keyboard-shortcuts/</feedburner:origLink></item>
		<item>
		<title>The Alteration Operator</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/iTfEEG_Itbk/</link>
		<comments>http://www.dacaprice.com/2011/04/19/the-alteration-operator/#comments</comments>
		<pubDate>Tue, 19 Apr 2011 14:53:27 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=799</guid>
		<description><![CDATA[Using egrep, the following will match all lines from the 9th, 10th, 11th, and 12th hours of Sunday April 10th in the log file eventdump.txt: $ egrep Sun\ Apr\ 10\ \('09&#124;10&#124;11&#124;12'\)\: eventdump.txt (I always forget to escape the parenthesis.)]]></description>
			<content:encoded><![CDATA[<p>Using egrep, the following will match all lines from the 9th, 10th, 11th, and 12th hours of Sunday April 10th in the log file eventdump.txt:</p>
<pre>$ egrep Sun\ Apr\ 10\ \('09|10|11|12'\)\: eventdump.txt</pre>
<p>(I always forget to escape the parenthesis.)</p>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/iTfEEG_Itbk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/04/19/the-alteration-operator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/04/19/the-alteration-operator/</feedburner:origLink></item>
		<item>
		<title>Full packet capture with tcpdump</title>
		<link>http://feedproxy.google.com/~r/dacaprice/~3/lhhfSa2acCs/</link>
		<comments>http://www.dacaprice.com/2011/04/11/full-packet-capture-with-tcpdump/#comments</comments>
		<pubDate>Mon, 11 Apr 2011 16:53:39 +0000</pubDate>
		<dc:creator>dacaprice</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://www.dacaprice.com/?p=794</guid>
		<description><![CDATA[[root@linux1 root]# tcpdump -s 0 -w capture.pcap]]></description>
			<content:encoded><![CDATA[<pre>[root@linux1 root]# tcpdump -s 0 -w capture.pcap</pre>
<img src="http://feeds.feedburner.com/~r/dacaprice/~4/lhhfSa2acCs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.dacaprice.com/2011/04/11/full-packet-capture-with-tcpdump/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dacaprice.com/2011/04/11/full-packet-capture-with-tcpdump/</feedburner:origLink></item>
	</channel>
</rss>

