<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nmap on Evan Hoffman</title><link>https://evan.wtf/tags/nmap/</link><description>Recent content in Nmap on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 27 Jan 2010 13:00:30 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/nmap/index.xml" rel="self" type="application/rss+xml"/><item><title>Running MRTG cfgmaker across your entire subnet?</title><link>https://evan.wtf/2010/01/27/running-mrtg-cfgmaker-across-your-entire-subnet/</link><pubDate>Wed, 27 Jan 2010 13:00:30 +0000</pubDate><guid>https://evan.wtf/2010/01/27/running-mrtg-cfgmaker-across-your-entire-subnet/</guid><description>&lt;p&gt;I realized recently that I had a bunch of newly-provisioned VMs that weren&amp;rsquo;t being monitored by MRTG (one of the tools we use to monitor network usage and other fun stats). Rather than manually run cfgmaker against all the new machines, I decided to script my way out of this.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Step 1: Build a list of hosts to monitor&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;For this I used an nmap ping test to generate a list of &amp;ldquo;up&amp;rdquo; hosts:&lt;/p&gt;</description></item></channel></rss>