<?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>Michael Earls</title>
	<atom:link href="http://www.michaelearls.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelearls.com</link>
	<description>On my site you find variation of things. Personal writings, PHP code, and projects that I am working on.</description>
	<lastBuildDate>Tue, 27 Nov 2012 04:00:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Import WordPress Security Patch</title>
		<link>http://www.michaelearls.com/2010/12/30/import-wordpress-security-patch/</link>
		<comments>http://www.michaelearls.com/2010/12/30/import-wordpress-security-patch/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 21:38:11 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[wordpress]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vulnerability]]></category>
		<category><![CDATA[xss attack]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=21</guid>
		<description><![CDATA[It is very important that all WordPress users update their installations to 3.0.4 as quickly as possible.  This newest edition of WordPress fixes a security bug in the WordPress KSES library which is in charge of performing HTML sanitization within the script. This cross-site scripting vulnerability should be taken very seriously. A cross-site scripting vulnerability [...]]]></description>
				<content:encoded><![CDATA[<p>It is very important that all WordPress users update their installations to 3.0.4 as quickly as possible.  This newest edition of WordPress fixes a security bug in the WordPress KSES library which is in charge of performing HTML sanitization within the script.</p>
<p>This cross-site scripting vulnerability should be taken very seriously.</p>
<p>A cross-site scripting vulnerability (otherwise known as a XSS attack) could be used to steal sensitive information (like login details) from people who visit your website.  They often do this by injecting a client-side script into your website.</p>
<p>You have two options when it comes to updating WordPress.  You can download the latest version from WordPress’s website and do a manual update or better yet – log into your WordPress administration section and do the update from within WordPress.</p>
<p>Updates during the holiday break are never fun, but this is one security issue you should fix as quickly as possible.<br />
-<br />
Michael Earls</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/12/30/import-wordpress-security-patch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to use the Public NTP (Network Time Protocol) Server</title>
		<link>http://www.michaelearls.com/2010/12/30/how-to-use-the-public-ntp-network-time-protocol-server/</link>
		<comments>http://www.michaelearls.com/2010/12/30/how-to-use-the-public-ntp-network-time-protocol-server/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 21:28:51 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[hp]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[ntp]]></category>
		<category><![CDATA[routers]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[synchroize]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=19</guid>
		<description><![CDATA[In this post we will discuss how to configure your local server to use the public NTP (Network time Protocol) Server to synchronize the clocks on your local computer or network device. Why is NTP Important? In a commercial environment, accurate time stamps are essential to everything from maintaining and troubleshooting equipment and forensic analysis [...]]]></description>
				<content:encoded><![CDATA[<p>In this post we will discuss how to configure your local server to use      the public NTP (Network time Protocol) Server to synchronize the  clocks on     your local computer or network device.</p>
<h2>Why is NTP Important?</h2>
<p>In a commercial environment, accurate time stamps are essential to  everything     from maintaining and troubleshooting equipment and  forensic analysis of     distributed attacks, to resolving disputes  among parties contesting a     commercially valuable time-sensitive  transaction. In a programming     environment, time stamps are usually  used to determine what bits of code     need to be rebuilt as part of a  dependency checking process as they relate     to other bits of code and  the time stamps on them, and without good time     stamps your entire  development process can be brought to a complete standstill.     Within  law enforcement, they are essential for correlation of distributed      communication events, forensic analysis, and potential evidentiary use  in     criminal proceedings. In essence, all debugging, security, audit,  and     authentication is founded on the basis of event correlation  (knowing     exactly what happened in what order, and on which side),  and that depends     on good time synchronization.</p>
<p>Another good explanation for this issue comes from <a href="http://www.oreillynet.com/cs/catalog/view/au/802" target="_top">Thomas     Akin</a>, in chapter 10 of his book <a href="http://www.oreilly.com/catalog/hardcisco/chapter/ch10.html" target="_top">Hardening Cisco Routers</a>:</p>
<p><em>Time is inherently important to the function of routers and      networks. It provides the only frame of reference between all devices on      the network. This makes synchronized time extremely important.  Without     synchronized time, accurately correlating information  between devices     becomes difficult, if not impossible. When it comes  to security, if you cannot     successfully compare logs between each of  your routers and all your network     servers, you will find it very  hard to develop a reliable picture of an     incident. Finally, even if  you are able to put the pieces together,     unsynchronized times,  especially between log files, may give an attacker     with a good  attorney enough wiggle room to escape prosecution.</em></p>
<p>Additional information on this subject can be found at <a href="http://www.net.berkeley.edu/time/" target="_top">UC     Berkeley</a>, <a href="http://uwadmnweb.uwyo.edu/InfoTech/Support/data/time.htm" target="_top">University of Wyoming</a>, in <a href="http://www.spirit.com/Network/net0701.html" target="_top">Rik     Farrow’s <em>Network Defense</em> columns for <strong><em>Network Magazine</em></strong> </a>, and in the <a href="http://www.tldp.org/LDP/sag/html/ntp.html" target="_top">Linux System Administrators Guide</a> at the Linux     Documentation Project.</p>
<p>Depending on the operating system NTP can very on the installation  guide, please reference your OS type in order to find the correct  distribution to install.</p>
<p><strong>Current NTP Version</strong>:<br />
<a href="http://support.ntp.org/bin/view/Main/SoftwareDownloads" target="_blank">http://support.ntp.org/bin/view/Main/SoftwareDownloads</a></p>
<p><strong>NTP Ports For Windows:</strong><br />
<a href="http://support.ntp.org/bin/view/Main/ExternalTimeRelatedLinks" target="_blank">http://support.ntp.org/bin/view/Main/ExternalTimeRelatedLinks</a><br />
<strong>Edit ntp.conf file, an add the following     lines</strong><br />
server pool.ntp.org maxpoll 12<br />
server pool.ntp.org maxpoll 12<br />
server pool.ntp.org maxpoll 12</p>
<p>Please check out <a href="http://www.pool.ntp.org/">http://www.pool.ntp.org</a> for a list of different time zone servers.</p>
<p><strong>How to verify that your server is     synchronized. </strong><br />
Issue the following command <em>ntpq     -p</em> or <em>ntpq     -pn</em> (DNS lookup off)</p>
<p>vermeer:~$ ntpq -p<br />
remote refid st t when poll reach delay offset jitter<br />
=========================================================<br />
+daffy.test1.org 193.5.216.14 2 u 68 1024 377 158.995 51.220 50.287<br />
*navobs1.o.net 130.149.17.8 2 u 191 1024 176 79.245 3.589 27.454<br />
-ntp.vermeer.org 131.188.3.222 3 u 766 1024 377 22.302 -2.928 0.508</p>
<p>vermeer:~$ ntpq -pn<br />
remote refid st t when poll reach delay offset jitter<br />
=========================================================<br />
+205.142.198.4 193.5.216.14 2 u 68 1024 377 158.995 51.220 50.287<br />
*198.30.92.2 130.149.17.8 2 u 191 1024 176 79.245 3.589 27.454<br />
-64.44.160.38 131.188.3.222 3 u 766 1024 377 22.302 -2.928 0.508</p>
<p><strong>How to verify that your clients are     synchronized.</strong><br />
Issue the following command <em>ntpdc     -c monlist</em> or <em>ntpdc     -nc monlist</em> ( DNS lookup off ):<br />
ntpq -p<br />
remote address          port     local address      count m ver drop       last   first<br />
=========================================================<br />
127.0.0.1                  40583     127.0.0.1                   53273 7 2      0      0     15483660</p>
<p>router1.vermeer.org   123     10.1.20.10                 93542 3 3      0      4     15483164<br />
router2.vermeer.org   123     10.1.30.10                 68744 3 3      0      5     15483060<br />
router3.vermeer.org   123     10.1.40.10                 56228 3 3      0      5     15483127</p>
<p>vermeer:~$ ntpq -p<br />
remote address          port     local address      count m ver drop       last   first<br />
=========================================================<br />
127.0.0.1                  40583     127.0.0.1                  53273 7 2      0      0     15483660<br />
10.253.40.38                 123 10.1.20.10               93542 3 3            4     15483164<br />
10.11.15.4                    123     10.1.20.10                68744 3 3      0      5     15483060<br />
10.10.80.16                  123     10.1.20.10                56228 3 3      0      5     15483127</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/12/30/how-to-use-the-public-ntp-network-time-protocol-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Graphing Cisco Systems (NBAR) Network-based application recognition with MRTG</title>
		<link>http://www.michaelearls.com/2010/12/30/graphing-cisco-systems-nbar-network-based-application-recognition-with-mrtg/</link>
		<comments>http://www.michaelearls.com/2010/12/30/graphing-cisco-systems-nbar-network-based-application-recognition-with-mrtg/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 21:23:35 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[networking]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=17</guid>
		<description><![CDATA[Synopsis: This documentation assumes that you have a version of Cisco IOS that supports the following MIB ciscoNbarProtocolDiscoveryMIB (1.3.6.1.4.1.9.9.244). This documentation assumes that (MRTG) Multi Router Traffic Grapher is installed and working. This documentation assumes that you have SNMP installed and working. This documentation assumes that you have used custom mrtg.cfg files. What is NBAR? [...]]]></description>
				<content:encoded><![CDATA[<p><strong>Synopsis:</strong><br />
This documentation assumes that you have a version of Cisco IOS that  supports the following MIB ciscoNbarProtocolDiscoveryMIB  (1.3.6.1.4.1.9.9.244). This documentation assumes that (MRTG) Multi  Router Traffic Grapher is installed and working. This documentation  assumes that you have SNMP installed and  working. This documentation  assumes that you have used custom mrtg.cfg files.</p>
<p><strong>What is NBAR?</strong><br />
Network Based Application Recognition is an intelligent classification  engine that recognizes applications that are static (which use fixed TCP  or UDP port numbers), and stateful (which dynamically assign TCP or UDP  port numbers).</p>
<p>The NBAR Protocol Discovery Management Information Base (MIB) expands  the capabilities of NBAR Protocol Discovery by providing the following  new Protocol Discovery functionalities through SNMP:</p>
<p><strong>What is MRTG?</strong><br />
MRTG consists of a Perl script which uses SNMP to read the traffic  counters of your routers and a fast C program which logs the traffic  data and creates beautiful graphs representing the traffic on the  monitored network connection. These graphs are embedded into webpages  which can be viewed from any modern Web-browser.</p>
<p>In addition to a detailed daily view, MRTG also creates visual  representations of the traffic seen during the last seven days, the last  five weeks and the last twelve months. This is possible because MRTG  keeps a log of all the data it has pulled from the router. This log is  automatically consolidated so that it does not grow over time, but still  contains all the relevant data for all the traffic seen over the last  two years. This is all performed in an efficient manner. Therefore you  can monitor 200 or more network links from any halfway decent UNIX box.</p>
<p>MRTG is not limited to monitoring traffic, though. It is possible to  monitor any SNMP variable you choose. You can even use an external  program to gather the data which should be monitored via MRTG. People  are using MRTG, to monitor things such as System Load, Login Sessions,  Modem availability and more. MRTG even allows you to accumulate two or  more data sources into a single graph.</p>
<p><strong>Enable NBAR in IOS:</strong></p>
<div>
!<br />
router#<br />
Interface FastEthernet 1/0<br />
Router(config-if)#ip nbar protocol-discovery<br />
!</div>
<p><strong>Test for Supported MIB:</strong></p>
<div>
snmpwalk -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.1 = INTEGER: 1<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.2 = INTEGER: 2<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.3 = INTEGER: 2<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.1.4 = INTEGER: 2<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.1 = Timeticks: (1537) 0:00:15.37<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.2 = Timeticks: (0) 0:00:00.00<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.3 = Timeticks: (0) 0:00:00.00<br />
iso.3.6.1.4.1.9.9.244.1.1.1.1.2.4 = Timeticks: (0) 0:00:00.00<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1 = STRING: &#8220;ftp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.2 = STRING: &#8220;http&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.3 = STRING: &#8220;egp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.4 = STRING: &#8220;gre&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.5 = STRING: &#8220;icmp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.6 = STRING: &#8220;eigrp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.7 = STRING: &#8220;ipinip&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.8 = STRING: &#8220;ipsec&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.9 = STRING: &#8220;bgp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.10 = STRING: &#8220;cuseeme&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.11 = STRING: &#8220;dhcp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.12 = STRING: &#8220;dns&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.13 = STRING: &#8220;finger&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.14 = STRING: &#8220;gopher&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.15 = STRING: &#8220;secure-http&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.16 = STRING: &#8220;imap&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.17 = STRING: &#8220;secure-imap&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.18 = STRING: &#8220;irc&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.19 = STRING: &#8220;secure-irc&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.20 = STRING: &#8220;kerberos&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.21 = STRING: &#8220;l2tp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.22 = STRING: &#8220;ldap&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.23 = STRING: &#8220;secure-ldap&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.24 = STRING: &#8220;sqlserver&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.25 = STRING: &#8220;netbios&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.26 = STRING: &#8220;nfs&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.27 = STRING: &#8220;nntp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.28 = STRING: &#8220;secure-nntp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.29 = STRING: &#8220;notes&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.30 = STRING: &#8220;ntp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.31 = STRING: &#8220;pcanywhere&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.32 = STRING: &#8220;pop3&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.33 = STRING: &#8220;secure-pop3&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.34 = STRING: &#8220;pptp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.35 = STRING: &#8220;rip&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.36 = STRING: &#8220;rsvp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.37 = STRING: &#8220;smtp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.38 = STRING: &#8220;snmp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.39 = STRING: &#8220;socks&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.40 = STRING: &#8220;ssh&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.41 = STRING: &#8220;syslog&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.42 = STRING: &#8220;telnet&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.43 = STRING: &#8220;secure-telnet&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.44 = STRING: &#8220;secure-ftp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.45 = STRING: &#8220;xwindows&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.46 = STRING: &#8220;printer&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.47 = STRING: &#8220;novadigm&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.48 = STRING: &#8220;tftp&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.49 = STRING: &#8220;exchange&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.50 = STRING: &#8220;vdolive&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.51 = STRING: &#8220;sqlnet&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.52 = STRING: &#8220;rcmd&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.53 = STRING: &#8220;netshow&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.54 = STRING: &#8220;sunrpc&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.55 = STRING: &#8220;streamwork&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.56 = STRING: &#8220;citrix&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.57 = STRING: &#8220;napster&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.58 = STRING: &#8220;fasttrack&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.59 = STRING: &#8220;gnutella&#8221;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.60 = STRING: &#8220;kazaa2&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.61 = STRING: &#8220;custom-01&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.62 = STRING: &#8220;custom-02&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.63 = STRING: &#8220;custom-03&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.64 = STRING: &#8220;custom-04&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.65 = STRING: &#8220;custom-05&#8243;<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.66 = STRING: &#8220;custom-06&#8243;</div>
<p><strong>Not Supported MIB in IOS</strong></p>
<div>
snmpwalk -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244<br />
Cannot find module (IP-MIB): At line 0 in (none)<br />
Cannot find module (IF-MIB): At line 0 in (none)<br />
Cannot find module (TCP-MIB): At line 0 in (none)<br />
Cannot find module (UDP-MIB): At line 0 in (none)<br />
Cannot find module (SNMPv2-MIB): At line 0 in (none)<br />
Cannot find module (SNMPv2-SMI): At line 0 in (none)<br />
Cannot find module (UCD-SNMP-MIB): At line 0 in (none)<br />
Cannot find module (UCD-DEMO-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-TARGET-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-VIEW-BASED-ACM-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-COMMUNITY-MIB): At line 0 in (none)<br />
Cannot find module (UCD-DLMOD-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-FRAMEWORK-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-MPD-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-USER-BASED-SM-MIB): At line 0 in (none)<br />
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)<br />
Cannot find module (SNMPv2-TM): At line 0 in (none)<br />
.iso.3.6.1.2.1.1.3.6.1.4.1.9.9.244 = No Such Instance currently exists</div>
<p><strong>Examples from the following output:</strong></p>
<div>
snmpget -c COMMUNITY -v2c IPADDRESS 1.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.interface-number.protocol<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1 – FastEthernet 1/0<br />
iso.3.6.1.4.1.9.9.244.1.2.1.1.2.1.1 – FTP Protocol Number</div>
<p>The nbar-internet.cfg file assumes that you are monitoring FastEthernet  1/0. Change this to refelect the interface you are monitoring.<br />
Change public@isp1 to the correct community string and ip address.</p>
<p><strong>Create New Directory:</strong><br />
Create the following directory under mrtg web files.</p>
<div>
nbar-internet</div>
<p><strong>Files Created:</strong><br />
The above configuration will create the following files under nbar-internet directory.</p>
<div>
fasttrack.log<br />
ftp.log<br />
gnutella.log<br />
h323.log<br />
http.log<br />
https.log<br />
kazaa2.log<br />
napster.log<br />
nntp.log<br />
pop3.log<br />
rstp.log<br />
smtp.log<br />
streamworks.log<br />
vdolive.log</div>
<p><strong>MRTG CFG FILE:</strong> (nbar-internet.cfg)<br />
<a href="http://vermeer.org/download.php?file=nbar-internet.cfg">Download nbar-internet.cfg</a></p>
<div>
### Global Config Options<br />
Options[_]: growright,bits<br />
WithPeak[_]: ymw<br />
Xsize[_]: 600<br />
Ysize[_]: 200<br />
Ytics[_]: 10</p>
<p>##<br />
## FTP Traffic Analysis<br />
##<br />
Target[nbar-internet-ftp]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.1&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.1:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.1&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.1:public@isp1:<br />
SetEnv[nbar-internet-ftp]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-ftp]: nbar-internet<br />
MaxBytes[nbar-internet-ftp]: 1000000<br />
Title[nbar-internet-ftp]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-ftp]:</p>
<p>##<br />
## HTTP Traffic Analysis<br />
##<br />
Target[nbar-internet-http]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.2&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.2:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.2&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.2:public@isp1:<br />
SetEnv[nbar-internet-http]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-http]: nbar-internet<br />
MaxBytes[nbar-internet-http]: 1000000<br />
Title[nbar-internet-http]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-http]:</p>
<p>##<br />
## HTTPs Traffic Analysis<br />
##<br />
Target[nbar-internet-https]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.15&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.15:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.15&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.15:public@isp1:<br />
SetEnv[nbar-internet-https]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-https]: nbar-internet<br />
MaxBytes[nbar-internet-https]: 1000000<br />
Title[nbar-internet-https]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-https]:</p>
<p>##<br />
## smtp Traffic Analysis<br />
##<br />
Target[nbar-internet-smtp]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.37&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.37:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.37&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.37:public@isp1:<br />
SetEnv[nbar-internet-smtp]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-smtp]: nbar-internet<br />
MaxBytes[nbar-internet-smtp]: 1000000<br />
Title[nbar-internet-smtp]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-smtp]:</p>
<p>##<br />
## NNTP Traffic Analysis<br />
##<br />
Target[nbar-internet-nntp]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.27&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.27:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.27&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.27:public@isp1:<br />
SetEnv[nbar-internet-nntp]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-nntp]: nbar-internet<br />
MaxBytes[nbar-internet-nntp]: 1000000<br />
Title[nbar-internet-nntp]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-nntp]:</p>
<p>##<br />
## vdolive Traffic Analysis<br />
##<br />
Target[nbar-internet-vdolive]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.50&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.50:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.50&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.50:public@isp1:<br />
SetEnv[nbar-internet-vdolive]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-vdolive]: nbar-internet<br />
MaxBytes[nbar-internet-vdolive]: 1000000<br />
Title[nbar-internet-vdolive]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-vdolive]:</p>
<p>##<br />
## streamworks Traffic Analysis<br />
##<br />
Target[nbar-internet-streamworks]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.55&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.55:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.55&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.55:public@isp1:<br />
SetEnv[nbar-internet-streamworks]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-streamworks]: nbar-internet<br />
MaxBytes[nbar-internet-streamworks]: 1000000<br />
Title[nbar-internet-streamworks]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-streamworks]:</p>
<p>##<br />
## napster Traffic Analysis<br />
##<br />
Target[nbar-internet-napster]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.57&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.57:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.57&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.57:public@isp1:<br />
SetEnv[nbar-internet-napster]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-napster]: nbar-internet<br />
MaxBytes[nbar-internet-napster]: 1000000<br />
Title[nbar-internet-napster]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-napster]:</p>
<p>##<br />
## fasttrack Traffic Analysis<br />
##<br />
Target[nbar-internet-fasttrack]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.58&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.58:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.58&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.58:public@isp1:<br />
SetEnv[nbar-internet-fasttrack]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-fasttrack]: nbar-internet<br />
MaxBytes[nbar-internet-fasttrack]: 1000000<br />
Title[nbar-internet-fasttrack]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-fasttrack]:</p>
<p>##<br />
## gnutella Traffic Analysis<br />
##<br />
Target[nbar-internet-gnutella]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.59&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.59:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.59&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.59:public@isp1:<br />
SetEnv[nbar-internet-gnutella]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-gnutella]: nbar-internet<br />
MaxBytes[nbar-internet-gnutella]: 1000000<br />
Title[nbar-internet-gnutella]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-gnutella]:</p>
<p>##<br />
## kazaa2 Traffic Analysis<br />
##<br />
Target[nbar-internet-kazaa2]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.60&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.60:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.60&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.60:public@isp1:<br />
SetEnv[nbar-internet-kazaa2]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-kazaa2]: nbar-internet<br />
MaxBytes[nbar-internet-kazaa2]: 1000000<br />
Title[nbar-internet-kazaa2]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-kazaa2]:</p>
<p>##<br />
## H323 Traffic Analysis<br />
##<br />
Target[nbar-internet-h323]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.75&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.75:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.75&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.75:public@isp1:<br />
SetEnv[nbar-internet-h323]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-h323]: nbar-internet<br />
MaxBytes[nbar-internet-h323]: 1000000<br />
Title[nbar-internet-h323]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-h323]:</p>
<p>##<br />
## rstp Traffic Analysis<br />
##<br />
Target[nbar-internet-rstp]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.71&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.71:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.71&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.71:public@isp1:<br />
SetEnv[nbar-internet-rstp]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-rstp]: nbar-internet<br />
MaxBytes[nbar-internet-rstp]: 1000000<br />
Title[nbar-internet-rstp]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-rstp]:</p>
<p>##<br />
## pop3 Traffic Analysis<br />
##<br />
Target[nbar-internet-pop3]:<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.32&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.32:public@isp1 +<br />
1.3.6.1.4.1.9.9.244.1.2.1.1.5.1.32&amp;1.3.6.1.4.1.9.9.244.1.2.1.1.6.1.32:public@isp1:<br />
SetEnv[nbar-internet-pop3]: MRTG_INT_IP=&#8221;" MRTG_INT_DESCR=&#8221;"<br />
Directory[nbar-internet-pop3]: nbar-internet<br />
MaxBytes[nbar-internet-pop3]: 1000000<br />
Title[nbar-internet-pop3]: Cisco Nbar Protocol Analysis<br />
PageTop[nbar-internet-pop3]:</p></div>
<p><img src="http://vermeer.org/images/nbar-internet-ftp_monthly.gif" alt="" width="400" height="150" /></p>
<p><img src="http://vermeer.org/images/nbar-internet-https_hourly.gif" alt="" width="400" height="150" /></p>
<p><img src="http://vermeer.org/images/nbar-internet-kazaa2_weekly.gif" alt="" width="400" height="150" /></p>
<p><img src="http://vermeer.org/images/nbar-internet-smtp_weekly.gif" alt="" width="400" height="150" /></p>
<p><strong>Additional References:</strong><br />
Cisco IOS images that support CISCO-NBAR-PROTOCOL-DISCOVERY-MIB MIB.<br />
<a href="http://www.cisco.com/pcgi-bin/Support/Mibbrowser/mibinfo.pl?mn=CISCO-NBAR-PROTOCOL-DISCOVERY-MIB&amp;vi=true" target="_blank">[...]</a></p>
<p>Network-Based Application Recognition and Distributed Network-Based Application Recognition:<br />
<a href="http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/dtnbarad.pdf" target="_blank">[...]</a></p>
<p>Network-Based Application Recognition Protocol Discovery Management Information Base:<br />
<a href="http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftpdmib.pdf" target="_blank">[...]</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/12/30/graphing-cisco-systems-nbar-network-based-application-recognition-with-mrtg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Donate to my favorite projects</title>
		<link>http://www.michaelearls.com/2010/12/30/donate-to-my-favorite-projects/</link>
		<comments>http://www.michaelearls.com/2010/12/30/donate-to-my-favorite-projects/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 21:17:06 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[donate]]></category>
		<category><![CDATA[filezilla]]></category>
		<category><![CDATA[pdfcreator]]></category>
		<category><![CDATA[projects]]></category>
		<category><![CDATA[winscp]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=14</guid>
		<description><![CDATA[I felt its important to donate to my favorite projects that I use in my everyday life and I continually promote to friends, co-works, and family. To name a few of the projects I donated to today: winscp &#8211; www.winscp.net pdfCreator &#8211; www.pdfforge.org/products/pdfcreator fileZilla &#8211; filezilla.sourceforge.net I also want to thank everyone who has donated [...]]]></description>
				<content:encoded><![CDATA[<p>I felt its important to donate to my favorite projects that I use  in my everyday life and I continually promote to friends, co-works, and  family. To name a few of the projects I donated to today:</p>
<p>winscp &#8211; www.winscp.net<br />
pdfCreator &#8211; www.pdfforge.org/products/pdfcreator<br />
fileZilla &#8211; filezilla.sourceforge.net</p>
<p>I also want to thank everyone who has donated to my project phpIP  Management http://www.phpip.net/contributers.php, this has really given  me the chance to spend the extra hours a night to make my project  better.</p>
<p>Thanks again,</p>
<p>-<br />
Michael Earls</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/12/30/donate-to-my-favorite-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Presented at the Ohio Information Security Forum</title>
		<link>http://www.michaelearls.com/2010/12/30/presented-at-the-ohio-information-security-forum/</link>
		<comments>http://www.michaelearls.com/2010/12/30/presented-at-the-ohio-information-security-forum/#comments</comments>
		<pubDate>Thu, 30 Dec 2010 20:46:56 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Cache Poisoning using DNS]]></category>
		<category><![CDATA[computing environments]]></category>
		<category><![CDATA[Denial of Service Attack]]></category>
		<category><![CDATA[DNS Design Best Practice]]></category>
		<category><![CDATA[DNS Hijacking]]></category>
		<category><![CDATA[DNS Reconnaissance]]></category>
		<category><![CDATA[engineering]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[Man in the Middle Attacks]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[Ohio Information Security Forum]]></category>
		<category><![CDATA[OISF]]></category>
		<category><![CDATA[Query Flooding DNS]]></category>
		<category><![CDATA[system administration]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=5</guid>
		<description><![CDATA[The Ohio Information Security Forum is a group of enthusiasts and professionals involved in information security, networking, system administration, engineering, and other computing environments. I was asked to present on the following topic to the group on April 12th, 2007.  My presentation will be posted online and also with OISF (www.ohioinfosec.org). This presentation covered topics [...]]]></description>
				<content:encoded><![CDATA[<p>The Ohio Information Security Forum is a group of enthusiasts and  professionals involved in information security, networking, system  administration, engineering, and other computing environments.  I was  asked to present on the following topic to the group on April 12th,  2007.   My presentation will be posted online and also with OISF  (www.ohioinfosec.org).</p>
<p>This presentation covered topics related to DNS with regards to design, attacks, and security including:</p>
<p>• DNS Reconnaissance<br />
• Cache Poisoning using DNS<br />
• Denial of Service Attack (Query Flooding DNS)<br />
• Man in the Middle Attacks (DNS Hijacking)<br />
• DNS Design Best Practice</p>
<p>-<br />
Michael Earls</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/12/30/presented-at-the-ohio-information-security-forum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Presentation on DNS</title>
		<link>http://www.michaelearls.com/2010/04/30/presentation-on-dns/</link>
		<comments>http://www.michaelearls.com/2010/04/30/presentation-on-dns/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 21:08:26 +0000</pubDate>
		<dc:creator>michael earls</dc:creator>
				<category><![CDATA[Presentations]]></category>
		<category><![CDATA[Cache Poisoning using DNS]]></category>
		<category><![CDATA[computing environments]]></category>
		<category><![CDATA[Denial of Service Attack]]></category>
		<category><![CDATA[DNS Design Best Practice]]></category>
		<category><![CDATA[DNS Hijacking]]></category>
		<category><![CDATA[DNS Reconnaissance]]></category>
		<category><![CDATA[donate]]></category>
		<category><![CDATA[engineering]]></category>
		<category><![CDATA[filezilla]]></category>
		<category><![CDATA[information security]]></category>

		<guid isPermaLink="false">http://www.michaelearls.com/?p=8</guid>
		<description><![CDATA[]]></description>
				<content:encoded><![CDATA[<object width="400" height="328"><param name="movie" value="http://static.slideshare.net/swf/ssplayer2.swf?doc=dnsprotocoldesignattacksandsecurity2-101230145427-phpapp01"/><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slideshare.net/swf/ssplayer2.swf?doc=dnsprotocoldesignattacksandsecurity2-101230145427-phpapp01"  type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="400" height="328"></embed></object>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelearls.com/2010/04/30/presentation-on-dns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
