<?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>aviflax.com &#187; Software</title>
	<atom:link href="http://aviflax.com/post/tag/software/feed/" rel="self" type="application/rss+xml" />
	<link>http://aviflax.com</link>
	<description></description>
	<lastBuildDate>Wed, 23 May 2012 20:04:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Review: Clojure Programming by Chas Emerick, Brian Carper, and Cristophe Grand</title>
		<link>http://aviflax.com/post/review-clojure-programming-by-chas-emerick-brian-carper-and-cristophe-grand/</link>
		<comments>http://aviflax.com/post/review-clojure-programming-by-chas-emerick-brian-carper-and-cristophe-grand/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 00:15:02 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[clojure]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=1877</guid>
		<description><![CDATA[This book provides a clear and comprehensive introduction to Clojure and Lisp.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.clojurebook.com/">Clojure Programming</a> is a clear, comprehensive, and effective guide to <a href="http://clojure.org">Clojure</a>.</p>
<p>Before reading this book, I was proficient with Java, JavaScript, Python, and a few other languages — all primarily object-oriented and <a href="http://en.wikipedia.org/wiki/ALGOL">ALGOL</a>-derived. Lisp and <a href="http://en.wikipedia.org/wiki/Functional_programming">functional programming</a> (FP) seemed alien and bizarre. But after hearing that people were getting real work done using FP with <a href="http://www.scala-lang.org/">Scala</a> and Clojure, and hearing <a href="http://twitter.com/richhickey">Rich Hickey</a>, the creator of Clojure, <a href="http://www.infoq.com/presentations/Simple-Made-Easy">speak</a> at <a href="https://thestrangeloop.com/">Strange Loop</a> 2011, I was inspired to get over my apprehension and learn functional programming and Clojure.</p>
<p>I decided it would be unwise to try to learn FP and Clojure at the same time, so I first wrote <a href="https://github.com/aviflax/rollups">a program</a> using FP in languages with which I was already familiar: CoffeeScript and Scala. It didn’t take long for me to build an appreciation for the paradigm.</p>
<p>Once I felt that I had a decent understanding of FP, I asked on Twitter whether anyone could recommend a book, and got a very enthusiastic recommendation from <a href="http://corfield.org/">Sean Corfield</a> for this one. It was available under O’Reilly’s pre-release program, so I was able to buy and read pre-release PDFs of the book.</p>
<p>The bottom line is that this book gave me a solid understanding of Clojure and enabled me to learn the language and gradually start using it. The concepts are presented in a thoughtful sequence and it’s made clear how each element of the language relates to the others.</p>
<p>The writing, examples, and organization are all excellent. And the book gets extra points for going beyond just explaining the language and how to use it, by being extra-comprehensive and covering how to really use the full Clojure ecosystem to build really useful software.</p>
<p>This is worth highlighting: if the book had been comprised of only chapter 1, “Down the Rabbit Hole”, and the first 2 parts, “Functional Programming and Concurrency” and “Building Abstractions”, it would have been an excellent book which I’d be recommending wholeheartedly. The inclusion of the subsequent parts, “Tools, Platform, and Projects”, “Practicums”, and “Miscellanea” make the book an invaluable resource and a fantastic value.</p>
<p>Ultimately, the book succeeds in conveying not only Clojure the language, but also the Clojure way, best practices, and key resources.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/review-clojure-programming-by-chas-emerick-brian-carper-and-cristophe-grand/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Are you a hammer carpenter?</title>
		<link>http://aviflax.com/post/are-you-a-hammer-carpenter/</link>
		<comments>http://aviflax.com/post/are-you-a-hammer-carpenter/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 06:35:02 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://aviflax.com/post/are-you-a-hammer-carpenter/</guid>
		<description><![CDATA[Fantastic post on programming languages and frameworks: A programming language is a tool. Each one fits it&#8217;s own problem-set. Calling oneself a &#8220;C Programmer&#8221; is like saying you&#8217;re a &#8220;Hammer Carpenter&#8221; who just uses a hammer. via Alexis Sellier.]]></description>
			<content:encoded><![CDATA[<p>Fantastic <a href="https://bbs.archlinux.org/viewtopic.php?pid=147321#p147321">post</a> on programming languages and frameworks:</p>
<blockquote cite="https://bbs.archlinux.org/viewtopic.php?pid=147321#p147321"><p>A programming language is a tool.  Each one fits it&#8217;s own problem-set.  Calling oneself a &#8220;C Programmer&#8221; is like saying you&#8217;re a &#8220;Hammer Carpenter&#8221; who just uses a hammer.</p></blockquote>
<p><a href="https://twitter.com/cloudhead/status/28723281460">via</a> Alexis Sellier.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/are-you-a-hammer-carpenter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Learning Java Web Development in 2010</title>
		<link>http://aviflax.com/post/learning-java-web-development-in-2010/</link>
		<comments>http://aviflax.com/post/learning-java-web-development-in-2010/#comments</comments>
		<pubDate>Thu, 24 Dec 2009 17:29:09 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=788</guid>
		<description><![CDATA[I just noticed this question by mrblah at Stack Overflow: I want to learn, at least at a basic level, how to build java web applications (coming from a .net background). Meaning, I would like to be able to build, deploy a simple cms type application from the ground up. What exactly do I need [...]]]></description>
			<content:encoded><![CDATA[<p>I just noticed <a href="http://stackoverflow.com/questions/1958808/java-web-development-what-skills-do-i-need">this question</a> by <a href="http://stackoverflow.com/users/68183/mrblah">mrblah</a> at Stack Overflow:</p>
<blockquote><p>
I want to learn, at least at a basic level, how to build java web applications (coming from a .net background).</p>
<p>Meaning, I would like to be able to build, deploy a simple cms type application from the ground up.</p>
<p>What exactly do I need to learn?</p>
<p>Tomcat seems to be a good web server for Java.</p>
<p>What options are there for the web? I know there is hibernate for an ORM.</p>
<p>Does java have MVC? what about JSP? can MVC and JSP be together? beans?</p>
<p>Maybe a book that covers all of these?
</p></blockquote>
<p>And <a href="http://stackoverflow.com/questions/1958808/java-web-development-what-skills-do-i-need/1959016#1959016">an answer</a> popped into my head:</p>
<blockquote>
<p>I consider most of the traditional Java web development options to be pretty heavy-weight, and there some good alternatives:</p>
<ul>
<li>
<p><a href="http://www.playframework.org/" rel="nofollow">Play</a> is an MVC framework which is focused on being lightweight, straightforward, and enabling rapid development — while sticking with pure Java, as opposed to a more dynamic JVM-based language. It&#8217;s fairly new but already impressive, and a good community has built up around it quickly.</p>
</li>
<li>
<p><a href="http://www.grails.org/" rel="nofollow">Grails</a> is an MVC framework, inspired by Ruby on Rails, which is written in, and uses, <a href="http://groovy.codehaus.org/" rel="nofollow">Groovy</a>, a Java-based scripting language. Grails is mature, robust, and widely respected, with a strong community. Groovy is basically a superset of Java, with better syntax and some great features such as closures, so learning it is a great way to learn Java.</p>
</li>
<li>
<p>If you need/want to build RESTful web sites/services/applications, <a href="http://restlet.org" rel="nofollow">Restlet</a> is a fantastic framework — I&#8217;m a big fan. It&#8217;s simple, straightforward, and yet flexible. Great community too.</p>
</li>
<li>
<p><a href="http://code.google.com/appengine/" rel="nofollow">Google&#8217;s App Engine</a> is an interesting option as well. It&#8217;s hosted, which may or may not be of interest, but it has a fairly simple API, and a good SDK.</p>
</li>
</ul>
<p>I&#8217;m sure there are others, but these are the ones I can think of off the top of my head.</p>
<p>Good luck, and have fun!</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/learning-java-web-development-in-2010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Dialog on Processes &amp; Threads</title>
		<link>http://aviflax.com/post/a-dialog-on-processes-threads/</link>
		<comments>http://aviflax.com/post/a-dialog-on-processes-threads/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 03:53:10 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[concurrency]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[processes]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[threads]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=679</guid>
		<description><![CDATA[I learned a lot from Ryan Tomayko's recent essay "I like Unicorn because it's Unix", and after I read it I had some questions rolling around my head which I couldn't quiet. So I wrote him an email. He was kind enough to respond quickly and at length, illuminating a subject I'd been fuzzy on for years. In fact, I thought his responses were edifying to the degree that they should be published. So after securing his permission, I'm reproducing our dialog here.]]></description>
			<content:encoded><![CDATA[<p>Cross-posted from <a href="http://blog.arc90.com/2009/10/26/a-dialog-on-processes-threads/">the Arc90 blog</a>.</p>
<p>I&#8217;ve been a fan of <a href="http://tomayko.com/">Ryan Tomayko</a> ever since I stumbled across his <a href="http://tomayko.com/writings/rest-to-my-wife">How I Explained REST to My Wife</a> in 2005. (That piece was so good that I actually performed it live during a <a href="http://arc90.com">company</a> lunch in early 2006, with the inimitable <a href="http://arc90.com/people/kamni-khan/">Kamni Khan</a>.) He&#8217;s had a special place in my feed reader since before the Avi Flax release of <a href="http://en.wikipedia.org/wiki/FeedLounge">FeedLounge</a> (yes, that actually happened). So as soon as his most recent essay, <a href="http://tomayko.com/writings/unicorn-is-unix">I like Unicorn because it&#8217;s Unix</a>, appeared in <a href="http://en.wikipedia.org/wiki/Google_Reader">my current feed reader</a>, as usual I read it immediately, and as usual I learned something.</p>
<p>The essay&#8217;s main points are that core Unix concepts such as <code>fork()</code>, <code>accept()</code>, <code>select()</code>, and Unix sockets had lamentably been ignored or neglected by proponents of Ruby and Python; that <a href="http://unicorn.bogomips.org/">Unicorn</a> is <q cite="http://tomayko.com/writings/unicorn-is-unix">undoubtedly one of the best, most densely packed examples of Unix programming in Ruby I&#8217;ve come across</q>; and that Ruby (and Python) developers should learn more about these paradigms, and consider using them where appropriate.</p>
<p>While I learned much from the essay, and enjoyed reading it and following the &#8220;* is Unix&#8221; meme it sparked, after I read it I had some questions rolling around my head which I couldn&#8217;t quiet. So, since comments are currently disabled on Ryan&#8217;s site, I wrote him an email. He was kind enough to respond quickly and at length, illuminating a subject I&#8217;d been fuzzy on for years. In fact, I thought his responses were edifying to the degree that they should be published. So after securing his permission, I&#8217;m reproducing our dialog here.</p>
<p><span id="more-679"></span>
<p>If you haven&#8217;t read it yet, I suggest reading <a href="http://tomayko.com/writings/unicorn-is-unix">I like Unicorn because it&#8217;s Unix</a> before proceeding.</p>
<p>I wrote Ryan:</p>
<blockquote><p>Hi Ryan, thanks for your recent piece on Unicorn and Unix. Enjoyed it, and learned… well, I learned that there&#8217;s even more important stuff I don&#8217;t know. (It&#8217;s funny sometimes being a software developer/architect and not having a CS background.)</p>
<p>Anyway, you definitely got me interested in learning more about the Unix programming and concurrency models, thank you for that.</p>
<p>One thing that has me a little confused: I got the impression that a lot of the difference between the Unix and Java/Windows approaches boils down to processes versus threads. Is that right? Is it an oversimplification?</p>
<p>(The process vs. threads thing seems related to the discussions going on about how to write concurrent programs; specifically the debates about shared data vs. message passing. Isn&#8217;t IPC essentially message passing?)</p>
<p>If that&#8217;s right, then what about Apache? Wasn&#8217;t the point of 2.x that it moved to a thread-based model over the process-based model of 1.x? And if so, then… what&#8217;s up with that? I&#8217;d think there were a ton of very smart, very unixy people involved in that effort; they must have had some good reasons for the switch, right? Or, more likely, I&#8217;m missing something.</p>
<p>Thanks!<br />
Avi
</p></blockquote>
<p>And he responded, that night:</p>
<blockquote>
<p><em>On Wed, Oct 7, 2009 at 7:44 AM, Avi Flax <avif@arc90.com> wrote:</em></p>
<p><em>&gt; Hi Ryan, thanks for your recent piece on Unicorn and Unix. Enjoyed it, and  learned… well, I learned that there&#8217;s even more important stuff I don&#8217;t  know. (It&#8217;s funny sometimes being a software developer/architect and not  having a CS background.)</em></p>
<p>Tell me about it. I don&#8217;t have a high school diploma :)</p>
<p><em>&gt; Anyway, you definitely got me interested in learning more about the Unix  programming and concurrency models, thank you for that.  One thing that has me a little confused: I got the impression that a lot of  the difference between the Unix and Java/Windows approaches boils down to  processes versus threads. Is that right? Is it an oversimplification?</em></p>
<p>I think that&#8217;s about right. There&#8217;s a lot of other important differences but, now that I think about it, they all seem to stem from the basic model of concurrency. Java/Windows people pretty much have to use threads because their processes are handicapped. Unix has good processes, so Unix people can use either processes or threads.</p>
<p>Now, the Unicorn piece was talking specifically about threads in Ruby. Native threads are a lot more powerful than Ruby threads. I always choose processes over threads (even native threads) when I can get away with it, but native threads are useful, whereas Ruby threads really aren&#8217;t.</p>
<p><em>&gt; (The process vs. threads thing seems related to the discussions going on  about how to write concurrent programs; specifically the debates about  shared data vs. message passing. Isn&#8217;t IPC essentially message passing?)</em></p>
<p>That&#8217;s precisely what it is. &#8220;Message passing&#8221; usually implies a specific kind of object encoding and message dispatch, though, whereas IPC is a bit more general. You have to build up messages and dispatch on top of simple binary streams between processes, which is what most message passing systems do but IPC usually implies you build that part yourself.</p>
<p>It&#8217;s good to think of Unix IPC as message passing, conceptually.</p>
<p><em>&gt; If that&#8217;s right, then what about Apache? Wasn&#8217;t the point of 2.x that it  moved to a thread-based model over the process-based model of 1.x? And if  so, then… what&#8217;s up with that? I&#8217;d think there were a ton of very smart,  very unixy people involved in that effort; they must have had some good  reasons for the switch, right? Or, more likely, I&#8217;m missing something.</em></p>
<p>Process-per-connection &#8212; the model used by unicorn and the echo server example and apache&#8217;s preforking mpm (I think) &#8212; falls down at a certain level of high concurrency. There&#8217;s too much overhead in processes to solve C10K (http://www.kegel.com/c10k.html) problems. At that point, you basically have to use native threads or async/events. This doesn&#8217;t mean process-per-connection isn&#8217;t the right solution for a wide range of problems. Further, the basic technique of forking and sharing a socket between processes underlies async/event solutions &#8212; it&#8217;s just that each process can handle more than one connection in parallel (without threads). High concurrency servers that use fork(2), a shared socket, and async IO include nginx, memcached, lighttpd, and HAProxy. High concurrency servers that use threads include Apache, Varnish, and Squid. All are stable and production proven.</p>
<p>Here&#8217;s what I&#8217;m personally trying to forward in all of this: people confuse the idea that threads can always be applied with the idea that threads are always *right*. Just because a general solution exists (threads) doesn&#8217;t mean a more specific technique that uses processes isn&#8217;t the better solution. I really like process-per-connection where I can get away with it (and Unicorn is a perfect example of where you can get away with it) because it&#8217;s so amazingly simple; much simpler than threaded code and definitely much simpler than async/events. I like processes + async IO for highly concurrent systems because you just can&#8217;t beat it performance-wise and I personally enjoy working with event-based code. But threads? I can&#8217;t think of a problem I like solving with them, even though they can be used to solve a wide range of them.</p>
<p>Thanks,<br/><br />
Ryan</p>
</blockquote>
<p>As you can see, Ryan was extremely generous with his time in responding to my email. Thanks Ryan! I learned a lot from this exchange, and I really appreciate it. Congratulations on <a href="http://github.com/blog/529-ryan-tomayko-is-a-githubber">your new position at GitHub</a>, it&#8217;s clearly a perfect match.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/a-dialog-on-processes-threads/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use a DVCS to Track Anything Instantly</title>
		<link>http://aviflax.com/post/use-a-dvcs-to-track-anything-instantly/</link>
		<comments>http://aviflax.com/post/use-a-dvcs-to-track-anything-instantly/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 16:08:29 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[dvcs]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[vcs]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=589</guid>
		<description><![CDATA[I recently stumbled across the essay In brief praise of DVCSs by Aristotle Pagaltzis, and it was a revelation for me. I&#8217;d been wanting to try a DVCS for a while, but hadn&#8217;t really gotten around to it — the perceived benefit hadn&#8217;t justified the perceived effort. But when Aristotle pointed out that Subversion makes [...]]]></description>
			<content:encoded><![CDATA[<p>I recently stumbled across the essay <a href="http://plasmasturm.org/log/523/">In brief praise of  <abbr title="Distributed Version Control System">DVCSs</abbr></a> by <a href="http://plasmasturm.org/about/">Aristotle Pagaltzis</a>, and it was a revelation for me. I&#8217;d been wanting to try a <abbr title="Distributed Version Control System">DVCS</abbr> for a while, but hadn&#8217;t really gotten around to it — the perceived benefit hadn&#8217;t justified the perceived effort. But when Aristotle pointed out that <q cite="http://plasmasturm.org/log/523/"><em>Subversion makes the mental overhead of creating a repository very much greater than any <abbr title="Distributed Version Control System">DVCS</abbr>,</em></q> something clicked. I saw an immediate benefit I&#8217;d gain from even simplistic usage of a DVCS, and so I immediately gave it a try.</p>
<p>I had a text file that I wanted to explicitly track versions of — I use Time Machine for incremental backup, which is great, but doesn&#8217;t always give me precise enough control of the snapshots, and I don&#8217;t always have the snapshots available. Once I read Aristotle&#8217;s essay, it only took me a few minutes to download and install <a href="http://mercurial.selenic.com/">Mercurial</a>, and then I started tracking my file with three simple commands: <code>hg init; hg add *; hg commit -m "initial"</code>. Quick, easy, and effective. From that point on, my folder was also a repository, and I could track specific revisions of my files by simply typing <code>hg commit -m "update"</code> at any point.</p>
<p>What I think is the killer realization here is that <em>it is now super easy to make any folder into a repository, and instantly start tracking versions of its contents.</em> I&#8217;ve used Subversion to make local repositories, and track local files in the past — and it really is many more steps, and much more work. It&#8217;s also messier, because the repository and the working copy must be separate entities — you have to think about where the repository should live, as opposed to the actual stuff, the working copy. With a DVSC, no such dichotomy exists. The repository and the actual stuff are one and the same. You can move them, zip them, email them — as long as the metadata directory is preserved (for example, <code>.hg</code> or <code>.git</code>), the folder remains a repository.</p>
<p>I&#8217;m thankful to Aristotle for helping me get past the initial barrier to entry, and start actually using a DVCS. I&#8217;m looking forward to learning more about them, and using them even more going forward.</p>
<p>(Bonus tip: on OS X, some applications save their data using a special type of file called a &#8220;package&#8221;, which is actually a directory with a special flag. One example is <a href="http://www.omnigroup.com/applications/omnigraffle/">OmniGraffle</a>, which I use frequently. Because these &#8220;files&#8221; are actually directories, they can be easily made into self-versioning files with their own self-contained repositories. Just navigate to the directory and run the commands above! From that point on, the file will be a repository and can track its own versions. Pretty useful!)</p>
<p>(I can&#8217;t explain exactly why I decided to try Mercurial first, before <a href="http://git-scm.com/">Git</a> or <a href="http://bazaar-vcs.org/">Bazaar</a>. I&#8217;ve read many comparisons of them, and something about those comparisons just made me want to try it. I&#8217;m not sure exactly how, but I had built up the impression that Mercurial was somehow simpler, cleaner, more elegant, and more approachable than Git or Bazaar. I don&#8217;t know if that&#8217;s actually true, but the impression was enough that that&#8217;s where I started.)</p>
<p>(Aristotle&#8217;s mention of &#8220;mental overhead&#8221; as a decisive factor in using one system over another is something <a href="http://aviflax.com/post/phrase-ive-been-using-frequen/">I&#8217;ve been thinking about lately as well</a>, although I&#8217;ve used the more unwieldy &#8220;cognitive overhead.&#8221;)</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/use-a-dvcs-to-track-anything-instantly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Chrome OS: Worth a Try</title>
		<link>http://aviflax.com/post/google-chrome-os-worth-a-try/</link>
		<comments>http://aviflax.com/post/google-chrome-os-worth-a-try/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 03:22:20 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[computing]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[open]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[os]]></category>
		<category><![CDATA[oss]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[source]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=530</guid>
		<description><![CDATA[Google just announced its long-rumored computer operating system, Chrome OS. There&#8217;s not much real insight or analysis I can add to the insanity that the tech web just melted down into. But I can throw my 2¢ into the churn. I&#8217;m excited. I like the ideas and the philosophy behind it. But more importantly, I [...]]]></description>
			<content:encoded><![CDATA[<p>Google <a href="http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html">just announced</a> its long-rumored computer operating system, Chrome OS. There&#8217;s not much real insight or analysis I can add to the insanity that the tech web just melted down into. But I can throw my 2¢ into the churn. I&#8217;m excited. I like the ideas and the philosophy behind it. But more importantly, I see this as a very positive development for a few simple reasons: competition, innovation, and choice. Google is innovating in the &#8220;basic computer&#8221; space, which is leading to increased choice and increased competition, which will lead to yet more innovation, leading to yet more choice and competition. It&#8217;s a vicious, virtuous, vital, beautiful cycle, and it has only positive implications for the future of everyday computing.</p>
<p>I&#8217;m looking forward to Chrome OS. It promises to be radically faster and simpler than all of the currently popular operating systems. I&#8217;m hoping it actually delivers on that promise, I think it&#8217;ll be good for computing!</p>
<p>OK, I was going to end the post there, but my (business) partner Tim just informed that I <em>do</em> have some insight and analysis I can throw into the ring. He asked me: if Google&#8217;s vision of the future of computing <em>is</em> the web, and they already have their own browser, why would they build their own OS? Aren&#8217;t browsers the gateway to the web? Here&#8217;s how I replied:<br />
<span id="more-530"></span><br />
The key to understanding this is in the name of the browser and the OS: &#8220;Chrome.&#8221; In computing, &#8220;chrome&#8221; is &#8220;the borders and widgets that frame the content part of a window&#8221; (<a href="http://en.wikipedia.org/wiki/Chrome">Wikipedia</a>) — in other words, it&#8217;s the stuff <em>around</em> the stuff that <em>really</em> matters — the &#8220;content&#8221; — the document, messages,  information, movie, pictures, etc that you&#8217;re reading, writing, watching, editing, or otherwise interacting with. It&#8217;s become a common wisdom in user interface design that chrome must be minimized, to the point where it&#8217;s invisible, if possible. (I suspect <a href="http://www.edwardtufte.com/">Edward Tufte</a> has been one of the supporters of that philosophy, but I don&#8217;t have any sources handy.)</p>
<p>With that understanding, Google&#8217;s philosophy seems clear to me. By naming their browser, and now their OS, after the stuff that <em>doesn&#8217;t really matter</em>, they&#8217;re revealing their thinking about what <em>does</em> really matter: the web. So this new OS is about delivering the experience of the web unshackled by the complexity that the modern operating system is weighed down by.</p>
<p>I apologize, but to continue I need to take a moment to talk about what the term &#8220;operating system&#8221; means. There have always been different definitions of the term. To many, it&#8217;s all the stuff that&#8217;s included with your average copy of Windows, OS X, or a Linux distribution: a file manager, notepad, calculator, control panel, web browser, email program, etc, etc, etc. But technically, those are all actually just applications which are bundled along with the OS; the OS itself is the code which manages the hardware, and provides an abstract interface to those applications, so they themselves don&#8217;t need to worry about the vagaries of hardware. But since the term OS has fractured over time, a new term arose to describe that core part of an OS: it&#8217;s called the kernel. A modern kernel, along with integrated extensions and drivers, handles important things like hardware resource allocation, memory management, power management, networking, and all the other low-level tasks which are kinda boring but also critical to an effective computing experience.</p>
<p>Sundar Pichai, Google&#8217;s VP of Product Management and Linus Upson, its Engineering Director, wrote in their announcement: &#8220;The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel.&#8221; This sounds innocuous enough, but it&#8217;s really a radical challenge to all the mainstream operating systems available today. Windows, OS X, and the mainstream Linux distributions all have a kind of a kitchen sink approach; they include a kernel, and a windowing system, but they all also include much, much, much more — complex file systems, file managers, outmoded and ineffective security models, thousands of device drivers for devices most people never use, and hundreds and hundreds of bundled applications — they&#8217;re trying to be all things for all people. Chrome OS is a challenge to that entire model, and if Google manages to pull it off, it may be an end to there being a single dominant model for how end-user &#8220;desktop&#8221; computers work. (By &#8220;desktop&#8221; I mean any and all descendants of the typewriter-based terminal model, centered around a keyboard, including laptops.)</p>
<p>Essentially, the philosophy behind Chrome OS is for it to contain only the bare minimum of systems necessary to boot up the hardware, connect it to the network, and load up the web. Just about everything else just won&#8217;t be there. Sure, that won&#8217;t work for some people — but my guess is that it <em>will</em> work for a whole bunch more. And by radically simplifying the software stack, that stack can be radically faster, more reliable, and more secure. Sounds worth a try to me.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/google-chrome-os-worth-a-try/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Another Google Calendar Suggestion</title>
		<link>http://aviflax.com/post/another-google-calendar-suggestion/</link>
		<comments>http://aviflax.com/post/another-google-calendar-suggestion/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 17:24:39 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[calendar]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://aviflax.com/post/another-google-calendar-suggestion/</guid>
		<description><![CDATA[Just sent this one as well: When I change an event, I should be able to enter a note to specifically explain the change itself, which would be included in the update notification email. Right now, we put notes in the Description field, but it&#8217;s confusing.]]></description>
			<content:encoded><![CDATA[<p>Just sent this one as well:</p>
<blockquote><p>When I change an event, I should be able to enter a note to specifically explain the change itself, which would be included in the update notification email. Right now, we put notes in the Description field, but it&#8217;s confusing.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/another-google-calendar-suggestion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Suggestion for Google Calendar</title>
		<link>http://aviflax.com/post/suggestion-for-google-calendar/</link>
		<comments>http://aviflax.com/post/suggestion-for-google-calendar/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 17:22:48 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://aviflax.com/post/suggestion-for-google-calendar/</guid>
		<description><![CDATA[Just sent this suggestion to the Google Calendar team: At my org, we always try to allow Guests to modify the event. That way we can more collaboratively adjust our shared schedules. But we frequently forget to check it. It&#8217;d be very helpful for us if there was a setting to make that option checked [...]]]></description>
			<content:encoded><![CDATA[<p>Just sent this suggestion to the Google Calendar team:</p>
<blockquote><p>At my org, we always try to allow Guests to modify the event. That way we can more collaboratively adjust our shared schedules. But we frequently forget to check it. It&#8217;d be very helpful for us if there was a setting to make that option checked by default for new events.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/suggestion-for-google-calendar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Keynote &#8217;09 Connection Lines and Move Actions</title>
		<link>http://aviflax.com/post/keynote-09-connection-lines-and-move-actions/</link>
		<comments>http://aviflax.com/post/keynote-09-connection-lines-and-move-actions/#comments</comments>
		<pubDate>Fri, 16 Jan 2009 19:02:33 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[keynote]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=497</guid>
		<description><![CDATA[I just posted this to the Keynote team via Apple&#8217;s Keynote Feedback page: Dear Keynote Team: Thanks so much for all the great enhancements in Keynote &#8217;09! One of the new features that I&#8217;m most excited about is the new Connection Lines feature. This is great! I really like making diagrams in Keynote, the ability [...]]]></description>
			<content:encoded><![CDATA[<p>I just posted this to the Keynote team via Apple&#8217;s <a href="http://www.apple.com/feedback/keynote.html">Keynote Feedback page</a>:</p>
<blockquote><p>
Dear Keynote Team:</p>
<p>Thanks so much for all the great enhancements in Keynote &#8217;09!</p>
<p>One of the new features that I&#8217;m most excited about is the new Connection Lines feature. This is great! I really like making diagrams in Keynote, the ability to build in one element at a time, focus on it, and then bring in the next one, can really help people connect to the ideas I&#8217;m trying to convey.</p>
<p>There&#8217;s one aspect of Connection Lines that I think could be improved: when an object they&#8217;re connected to moves because of a Move Action, the line doesn&#8217;t move along with it. Ideally, it really should.</p>
<p>Thanks!
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/keynote-09-connection-lines-and-move-actions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Preferred Approach to Music Downloads</title>
		<link>http://aviflax.com/post/my-preferred-approach-to-music-downloads/</link>
		<comments>http://aviflax.com/post/my-preferred-approach-to-music-downloads/#comments</comments>
		<pubDate>Mon, 15 Sep 2008 15:08:26 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[digital]]></category>
		<category><![CDATA[iTunes]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[open]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[oss]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[source]]></category>
		<category><![CDATA[tool]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=464</guid>
		<description><![CDATA[I interact directly with the act via their own website. I download (middling-quality) MP3 tracks for free and listen to the music for a few days or weeks. If I like the music enough to want to have it in my library, I go to the act&#8217;s website to buy it. If not, I delete [...]]]></description>
			<content:encoded><![CDATA[<ol>
<li>I interact directly with the act via their own website.</li>
<li>I download (middling-quality) MP3 tracks for free and listen to the music for a few days or weeks.</li>
<li>If I like the music enough to want to have it in my library, I go to the act&#8217;s website to buy it. If not, I delete the MP3 tracks.</li>
<li>I specify the price I&#8217;m willing to pay.</li>
<li>I download a zip file containing 320 KBps <a href="http://flac.sourceforge.net/">FLAC</a> tracks and JPEG art files.</li>
<li>I use <a href="http://sbooth.org/Max/">Max</a> to convert the FLAC tracks to <a href="http://en.wikipedia.org/wiki/Apple_Lossless">Apple Lossless</a> tracks.</li>
<li>I import the tracks into my iTunes library, add the art, and enter the metadata for each track.</li>
</ol>
<p><s>Seeing as Max is Open Source, I see an opportunity here for some software to automate all this. Imagine dragging that downloaded zip file onto &#8220;MaxiTunes&#8221;, having it pop up a simple interface for entering metadata, and then it takes care of converting the tracks, adding the metadata, importing them into iTunes, and moving the original files to the trash. I&#8217;d be willing to contribute funds to a developer willing to give this a try.</s></p>
<p><strong>Update:</strong> It turns out that I underestimated Max. Apparently if a FLAC file contains metadata, it&#8217;ll be preserved during the conversion. And if not, Max has built-in metadata editing. It can also automatically add converted tracks to iTunes, and even to a specific playlist. Impressive! I like Max a lot &#8211; it&#8217;s fast, effective, reliable, free, and Free. My only real quibble would be that the UI is a little confusing. Just a little though.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/my-preferred-approach-to-music-downloads/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CouchDB Tech Talk @ Arc90</title>
		<link>http://aviflax.com/post/couchdb-tech-talk-arc90/</link>
		<comments>http://aviflax.com/post/couchdb-tech-talk-arc90/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 23:19:14 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[arc]]></category>
		<category><![CDATA[arc90]]></category>
		<category><![CDATA[event]]></category>
		<category><![CDATA[events]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[talk]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=461</guid>
		<description><![CDATA[RSVP here]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mobaganda.com/couchdbarc90">RSVP here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/couchdb-tech-talk-arc90/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FUD from Technology Review?</title>
		<link>http://aviflax.com/post/fud-from-technology-review/</link>
		<comments>http://aviflax.com/post/fud-from-technology-review/#comments</comments>
		<pubDate>Tue, 20 May 2008 14:06:28 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[oss]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://aviflax.com/?p=452</guid>
		<description><![CDATA[Just posted a comment in response to Alarming Open-Source Security Holes at MIT&#8217;s Technology Review: Your headline is misleading &#8211; I hope it&#8217;s an innocent mistake, as opposed to an intentional attempt to spread FUD about Open Source software. The crucial nuance that&#8217;s missing, both from the headline and the article, is that bugs such [...]]]></description>
			<content:encoded><![CDATA[<p>Just posted <a href="http://www.technologyreview.com/Infotech/20801/page1/#comment-203051">a comment</a> in response to <a href="http://www.technologyreview.com/Infotech/20801/">Alarming Open-Source Security Holes</a> at MIT&#8217;s Technology Review:</p>
<blockquote><p>Your headline is misleading &#8211; I hope it&#8217;s an innocent mistake, as opposed to an intentional attempt to spread FUD about Open Source software. The crucial nuance that&#8217;s missing, both from the headline and the article, is that bugs such as this are <strong>just</strong> as likely to occur in closed-source software as in open-source &#8212; but with open-source software, they&#8217;re <em>far</em> more likely to be discovered, sooner, precisely because the code is available for anyone to peruse!</p>
<p>I expect more from Technology Review. Please consider adding a note or correction to this effect.</p></blockquote>
<p><del datetime="2008-05-20T16:43:03+00:00">I&#8217;m not actually surprised or anything; TR has always had a corporate feel to it &#8211; it&#8217;s generally about MITers or ex-MITers making money, as opposed to pure excitement about technology.</del></p>
<p><em>Edit:</em> Struck out the last paragraph; after Jason Pontin&#8217;s comment below, I realized that my impressions of TR are almost certainly out of date. BTW, he also responded to <a href="http://www.technologyreview.com/Infotech/20801/page1/#comment-203051">my comment</a>; check out the discussion there.</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/fud-from-technology-review/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Bonjour and Extremely Large LANs</title>
		<link>http://aviflax.com/post/bonjour-and-extremely-large-lans/</link>
		<comments>http://aviflax.com/post/bonjour-and-extremely-large-lans/#comments</comments>
		<pubDate>Sun, 09 Mar 2008 20:26:39 +0000</pubDate>
		<dc:creator>Avi</dc:creator>
				<category><![CDATA[none]]></category>
		<category><![CDATA[bonjour]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[os]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[x]]></category>

		<guid isPermaLink="false">http://aviflax.com/post/bonjour-and-extremely-large-lans/</guid>
		<description><![CDATA[Elina and I occasionally eat at Cafe Nana at the Columbia Hillel. When we&#8217;re there, I frequently connect my MacBook to Columbia&#8217;s freely available wifi network. The network works well, and I definitelt appreciate it. However, whenever I connect to the network, I notice my MenuMeters Network monitor showing a persistent high level of throughput, [...]]]></description>
			<content:encoded><![CDATA[<p>Elina and I occasionally eat at <a href="http://www.cafenana.com/">Cafe Nana</a> at the <a href="http://www.hillel.columbia.edu/">Columbia Hillel</a>. When we&#8217;re there, I frequently connect my MacBook to Columbia&#8217;s freely available wifi network. The network works well, and I definitelt appreciate it.</p>
<p>However, whenever I connect to the network, I notice my <a href="http://www.ragingmenace.com/software/menumeters/">MenuMeters</a> Network monitor showing a persistent high level of throughput, ranging from 15 to 35 KBps. This is odd, given that I have no programs running. So I pop open <a href="http://www.obdev.at/products/littlesnitch/index.html">Little Snitch</a>&#8216;s Network Monitor &#8211; an excellent tool &#8211; to see what&#8217;s going on. Looks like mDNSResponder&#8217;s going a little nuts, talking to hundreds of addresses in quick succession.</p>
<p>Here&#8217;s a screenshot:</p>
<p><img src="http://aviflax.com/wp-content/uploads/2008/03/little-snitch-network-monitor-mdnsresponder-traffic-columbia.png" alt="Little Snitch Network Monitor mDNSResponder Traffic Columbia.png" border="0" width="310" height="368" /></p>
<p>At the same time, I start getting a lot of Little Snitch traffic prompts for nmbd, for various ports, like this:</p>
<p><img src="http://aviflax.com/wp-content/uploads/2008/03/little-snitch-network-monitor-nmbd-prompt-at-columbia.png" alt="Little Snitch Network Monitor nmbd prompt at Columbia.png" border="0" width="556" height="361" /></p>
<p>Here&#8217;s a snapshot of Little Snitch&#8217;s connection history for mDNSResponder:</p>
<div style="height: 20em; overflow: scroll;">
<pre>
Connection report for process: mDNSResponder (/usr/sbin/mDNSResponder)
Total: 132.4kB sent, 10.1MB received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.3kB received
	dyn-160-39-251-87.dyn.columbia.edu (160.39.251.87), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.4kB received
	dyn-160-39-252-75.dyn.columbia.edu (160.39.252.75), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.9kB received
	dyn-wireless-245-241.dyn.columbia.edu (160.39.245.241), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 106.1kB received
	dyn-160-39-251-219.dyn.columbia.edu (160.39.251.219), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-250-228.dyn.columbia.edu (160.39.250.228), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.6kB received
	dyn-160-39-242-239.dyn.columbia.edu (160.39.242.239), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 290.5kB received
	dyn-wireless-244-69.dyn.columbia.edu (160.39.244.69), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 330.2kB received
	dyn-160-39-252-155.dyn.columbia.edu (160.39.252.155), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 192 Bytes received
	dyn-160-39-251-215.dyn.columbia.edu (160.39.251.215), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 73.8kB received
	dyn-wireless-246-190.dyn.columbia.edu (160.39.246.190), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 148.5kB received
	dyn-160-39-252-103.dyn.columbia.edu (160.39.252.103), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 50.4kB received
	dyn-160-39-254-126.dyn.columbia.edu (160.39.254.126), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-251-224.dyn.columbia.edu (160.39.251.224), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 153.7kB received
	dyn-160-39-247-178.dyn.columbia.edu (160.39.247.178), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 74.5kB received
	dyn-160-39-253-192.dyn.columbia.edu (160.39.253.192), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 221.0kB received
	dyn-160-39-241-192.dyn.columbia.edu (160.39.241.192), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 87.9kB received
	dyn-160-39-250-130.dyn.columbia.edu (160.39.250.130), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 211.1kB received
	dyn-160-39-253-57.dyn.columbia.edu (160.39.253.57), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 64.1kB received
	dyn-wireless-246-17.dyn.columbia.edu (160.39.246.17), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 150.3kB received
	dyn-160-39-243-121.dyn.columbia.edu (160.39.243.121), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 186.2kB received
	dyn-160-39-250-198.dyn.columbia.edu (160.39.250.198), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 40.9kB received
	dyn-160-39-242-241.dyn.columbia.edu (160.39.242.241), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 27.4kB received
	dyn-160-39-254-231.dyn.columbia.edu (160.39.254.231), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 71.2kB received
	dyn-160-39-253-24.dyn.columbia.edu (160.39.253.24), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 79.6kB received
	dyn-160-39-252-251.dyn.columbia.edu (160.39.252.251), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 31.9kB received
	dyn-160-39-255-101.dyn.columbia.edu (160.39.255.101), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.3kB received
	dyn-160-39-255-176.dyn.columbia.edu (160.39.255.176), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 131.3kB received
	dyn-wireless-245-201.dyn.columbia.edu (160.39.245.201), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 29.4kB received
	dyn-160-39-251-157.dyn.columbia.edu (160.39.251.157), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 82.6kB received
	dyn-wireless-245-171.dyn.columbia.edu (160.39.245.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.9kB received
	dyn-160-39-242-16.dyn.columbia.edu (160.39.242.16), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 36.0kB received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.4kB received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.3kB received
	dyn-wireless-245-39.dyn.columbia.edu (160.39.245.39), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.7kB received
	dyn-160-39-251-193.dyn.columbia.edu (160.39.251.193), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 38.9kB received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 110.4kB received
	dyn-160-39-252-34.dyn.columbia.edu (160.39.252.34), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 75.0kB received
	dyn-160-39-255-123.dyn.columbia.edu (160.39.255.123), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.5kB received
	dyn-wireless-245-142.dyn.columbia.edu (160.39.245.142), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.5kB received
	dyn-160-39-253-134.dyn.columbia.edu (160.39.253.134), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 35.8kB received
	dyn-160-39-243-62.dyn.columbia.edu (160.39.243.62), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 26.2kB received
	dyn-wireless-246-110.dyn.columbia.edu (160.39.246.110), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 62.4kB received
	dyn-160-39-255-72.dyn.columbia.edu (160.39.255.72), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 458 Bytes received
	dyn-wireless-245-23.dyn.columbia.edu (160.39.245.23), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 37.3kB received
	dyn-160-39-255-157.dyn.columbia.edu (160.39.255.157), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 82.1kB received
	dyn-wireless-244-171.dyn.columbia.edu (160.39.244.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 69.9kB received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 106.3kB received
	224.0.0.251 (224.0.0.251), Port 5353 (mdns), Protocol 17 (UDP), 106.3kB sent, 0 Bytes received
	dyn-160-39-252-109.dyn.columbia.edu (160.39.252.109), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 29.8kB received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 32.0kB received
	dyn-160-39-242-87.dyn.columbia.edu (160.39.242.87), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.7kB received
	dyn-wireless-244-237.dyn.columbia.edu (160.39.244.237), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 79.7kB received
	dyn-160-39-250-143.dyn.columbia.edu (160.39.250.143), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.9kB received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.8kB received
	dyn-160-39-252-253.dyn.columbia.edu (160.39.252.253), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.3kB received
	dyn-160-39-251-58.dyn.columbia.edu (160.39.251.58), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 27.0kB received
	dyn-160-39-241-51.dyn.columbia.edu (160.39.241.51), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 25.3kB received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 64.9kB received
	dyn-160-39-241-63.dyn.columbia.edu (160.39.241.63), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 12.0kB received
	dyn-160-39-242-74.dyn.columbia.edu (160.39.242.74), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 38.2kB received
	dyn-160-39-247-175.dyn.columbia.edu (160.39.247.175), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-160-39-252-145.dyn.columbia.edu (160.39.252.145), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 41.7kB received
	dyn-160-39-242-150.dyn.columbia.edu (160.39.242.150), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 34.2kB received
	dyn-160-39-241-84.dyn.columbia.edu (160.39.241.84), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 104.3kB received
	dyn-wireless-245-224.dyn.columbia.edu (160.39.245.224), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-242-240.dyn.columbia.edu (160.39.242.240), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-251-133.dyn.columbia.edu (160.39.251.133), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.1kB received
	dyn-wireless-244-32.dyn.columbia.edu (160.39.244.32), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 26.1kB received
	dyn-160-39-241-250.dyn.columbia.edu (160.39.241.250), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 33.9kB received
	dyn-wireless-245-204.dyn.columbia.edu (160.39.245.204), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 33.2kB received
	dyn-wireless-245-93.dyn.columbia.edu (160.39.245.93), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 26.1kB received
	dyn-160-39-251-197.dyn.columbia.edu (160.39.251.197), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 26.9kB received
	dyn-wireless-246-12.dyn.columbia.edu (160.39.246.12), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.6kB received
	dyn-wireless-244-31.dyn.columbia.edu (160.39.244.31), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 113.4kB received
	dyn-160-39-255-107.dyn.columbia.edu (160.39.255.107), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.8kB received
	dyn-wireless-245-100.dyn.columbia.edu (160.39.245.100), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 21.6kB received
	dyn-160-39-255-113.dyn.columbia.edu (160.39.255.113), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 52.9kB received
	dyn-160-39-250-211.dyn.columbia.edu (160.39.250.211), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.9kB received
	dyn-160-39-250-194.dyn.columbia.edu (160.39.250.194), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 75.2kB received
	dyn-160-39-252-163.dyn.columbia.edu (160.39.252.163), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 72.6kB received
	dyn-wireless-245-121.dyn.columbia.edu (160.39.245.121), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 31.7kB received
	dyn-160-39-253-174.dyn.columbia.edu (160.39.253.174), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 30.6kB received
	dyn-160-39-251-235.dyn.columbia.edu (160.39.251.235), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 42.9kB received
	dyn-160-39-242-170.dyn.columbia.edu (160.39.242.170), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-242-83.dyn.columbia.edu (160.39.242.83), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 146.3kB received
	dyn-160-39-252-204.dyn.columbia.edu (160.39.252.204), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 80.7kB received
	dyn-160-39-241-249.dyn.columbia.edu (160.39.241.249), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 105.0kB received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.6kB received
	dyn-wireless-246-244.dyn.columbia.edu (160.39.246.244), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 15.7kB received
	dyn-wireless-246-140.dyn.columbia.edu (160.39.246.140), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.7kB received
	dyn-160-39-243-171.dyn.columbia.edu (160.39.243.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.5kB received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 27.2kB received
	dyn-160-39-241-217.dyn.columbia.edu (160.39.241.217), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 60.5kB received
	dyn-wireless-245-111.dyn.columbia.edu (160.39.245.111), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 20.8kB received
	dyn-160-39-250-138.dyn.columbia.edu (160.39.250.138), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 77.3kB received
	dyn-160-39-252-107.dyn.columbia.edu (160.39.252.107), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 60.9kB received
	dyn-160-39-242-36.dyn.columbia.edu (160.39.242.36), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 118.2kB received
	dyn-160-39-254-128.dyn.columbia.edu (160.39.254.128), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 78.3kB received
	dyn-wireless-244-167.dyn.columbia.edu (160.39.244.167), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76.2kB received
	dyn-160-39-241-80.dyn.columbia.edu (160.39.241.80), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 182.5kB received
	dyn-160-39-242-91.dyn.columbia.edu (160.39.242.91), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.0kB received
	dyn-wireless-244-152.dyn.columbia.edu (160.39.244.152), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 31.7kB received
	dyn-160-39-255-20.dyn.columbia.edu (160.39.255.20), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 39.5kB received
	dyn-160-39-242-251.dyn.columbia.edu (160.39.242.251), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.8kB received
	dyn-wireless-246-214.dyn.columbia.edu (160.39.246.214), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 80.5kB received
	dyn-160-39-247-28.dyn.columbia.edu (160.39.247.28), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 27.0kB received
	dyn-160-39-253-202.dyn.columbia.edu (160.39.253.202), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 28.3kB received
	dyn-160-39-247-219.dyn.columbia.edu (160.39.247.219), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 30.7kB received
	dyn-160-39-253-90.dyn.columbia.edu (160.39.253.90), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 84.0kB received
	dyn-160-39-253-176.dyn.columbia.edu (160.39.253.176), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.2kB received
	dyn-wireless-245-178.dyn.columbia.edu (160.39.245.178), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 21.2kB received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 37.2kB received
	dyn-wireless-244-10.dyn.columbia.edu (160.39.244.10), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-wireless-244-16.dyn.columbia.edu (160.39.244.16), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 124.1kB received
	dyn-wireless-244-67.dyn.columbia.edu (160.39.244.67), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 51.8kB received
	dyn-wireless-245-164.dyn.columbia.edu (160.39.245.164), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 33.7kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 26.3kB received
	dyn-160-39-253-89.dyn.columbia.edu (160.39.253.89), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-252-194.dyn.columbia.edu (160.39.252.194), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.0kB received
	dyn-160-39-242-107.dyn.columbia.edu (160.39.242.107), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76.7kB received
	dyn-160-39-241-120.dyn.columbia.edu (160.39.241.120), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 74.0kB received
	dyn-160-39-251-194.dyn.columbia.edu (160.39.251.194), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 488 Bytes received
	dyn-wireless-246-242.dyn.columbia.edu (160.39.246.242), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 139.4kB received
	dyn-160-39-253-46.dyn.columbia.edu (160.39.253.46), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 77.0kB received
	dyn-160-39-241-245.dyn.columbia.edu (160.39.241.245), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-250-48.dyn.columbia.edu (160.39.250.48), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 21.1kB received
	dyn-160-39-250-141.dyn.columbia.edu (160.39.250.141), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.0kB received
	dyn-160-39-243-87.dyn.columbia.edu (160.39.243.87), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 117.5kB received
	dyn-160-39-250-112.dyn.columbia.edu (160.39.250.112), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.6kB received
	dyn-wireless-245-227.dyn.columbia.edu (160.39.245.227), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 123.8kB received
	dyn-wireless-246-224.dyn.columbia.edu (160.39.246.224), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.1kB received
	dyn-160-39-251-187.dyn.columbia.edu (160.39.251.187), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 126.9kB received
	dyn-160-39-252-51.dyn.columbia.edu (160.39.252.51), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.1kB received
	dyn-wireless-245-78.dyn.columbia.edu (160.39.245.78), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 21.7kB received
	dyn-160-39-243-65.dyn.columbia.edu (160.39.243.65), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.1kB received
	dyn-160-39-243-240.dyn.columbia.edu (160.39.243.240), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 38.4kB received
	dyn-160-39-255-44.dyn.columbia.edu (160.39.255.44), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.2kB received
	dyn-wireless-244-180.dyn.columbia.edu (160.39.244.180), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-241-48.dyn.columbia.edu (160.39.241.48), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.2kB received
	dyn-160-39-242-230.dyn.columbia.edu (160.39.242.230), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.8kB received
	ff02::fb (ff02::fb), Port 5353 (mdns), Protocol 17 (UDP), 22.2kB sent, 0 Bytes received
	dyn-wireless-244-110.dyn.columbia.edu (160.39.244.110), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.0kB received
	dyn-160-39-241-237.dyn.columbia.edu (160.39.241.237), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.7kB received
	dyn-wireless-245-136.dyn.columbia.edu (160.39.245.136), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-wireless-246-116.dyn.columbia.edu (160.39.246.116), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.1kB received
	dyn-160-39-255-199.dyn.columbia.edu (160.39.255.199), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-247-133.dyn.columbia.edu (160.39.247.133), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-wireless-246-32.dyn.columbia.edu (160.39.246.32), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 75 Bytes received
	dyn-160-39-250-126.dyn.columbia.edu (160.39.250.126), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-251-237.dyn.columbia.edu (160.39.251.237), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.5kB received
	dyn-160-39-242-152.dyn.columbia.edu (160.39.242.152), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 35.1kB received
	dyn-160-39-251-98.dyn.columbia.edu (160.39.251.98), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.7kB received
	dyn-160-39-241-225.dyn.columbia.edu (160.39.241.225), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.5kB received
	dyn-wireless-244-136.dyn.columbia.edu (160.39.244.136), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.0kB received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 33.3kB received
	dyn-160-39-250-199.dyn.columbia.edu (160.39.250.199), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.5kB received
	dyn-wireless-244-98.dyn.columbia.edu (160.39.244.98), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 30.2kB received
	dyn-160-39-241-124.dyn.columbia.edu (160.39.241.124), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-242-166.dyn.columbia.edu (160.39.242.166), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 18.5kB received
	dyn-160-39-252-114.dyn.columbia.edu (160.39.252.114), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 28.8kB received
	dyn-160-39-254-104.dyn.columbia.edu (160.39.254.104), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.2kB received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.3kB received
	dyn-wireless-245-185.dyn.columbia.edu (160.39.245.185), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 16.9kB received
	dyn-160-39-247-239.dyn.columbia.edu (160.39.247.239), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.5kB received
	dyn-160-39-252-213.dyn.columbia.edu (160.39.252.213), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.5kB received
	dyn-wireless-244-36.dyn.columbia.edu (160.39.244.36), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 170 Bytes received
	dyn-160-39-242-69.dyn.columbia.edu (160.39.242.69), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 29.7kB received
	dyn-160-39-254-173.dyn.columbia.edu (160.39.254.173), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 92.7kB received
	dyn-160-39-247-117.dyn.columbia.edu (160.39.247.117), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.7kB received
	dyn-wireless-244-248.dyn.columbia.edu (160.39.244.248), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 22.0kB received
	dyn-wireless-246-171.dyn.columbia.edu (160.39.246.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.9kB received
	dyn-160-39-241-130.dyn.columbia.edu (160.39.241.130), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.1kB received
	dyn-160-39-242-207.dyn.columbia.edu (160.39.242.207), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 73.7kB received
	dyn-160-39-253-190.dyn.columbia.edu (160.39.253.190), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-242-12.dyn.columbia.edu (160.39.242.12), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 17.5kB received
	dyn-160-39-247-35.dyn.columbia.edu (160.39.247.35), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.5kB received
	dyn-160-39-255-146.dyn.columbia.edu (160.39.255.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-251-19.dyn.columbia.edu (160.39.251.19), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.7kB received
	dyn-160-39-251-118.dyn.columbia.edu (160.39.251.118), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76.1kB received
	dyn-160-39-250-190.dyn.columbia.edu (160.39.250.190), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76.2kB received
	dyn-160-39-247-226.dyn.columbia.edu (160.39.247.226), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.5kB received
	dyn-160-39-252-21.dyn.columbia.edu (160.39.252.21), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 20.8kB received
	dyn-160-39-241-70.dyn.columbia.edu (160.39.241.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 67.7kB received
	dyn-160-39-255-141.dyn.columbia.edu (160.39.255.141), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-254-31.dyn.columbia.edu (160.39.254.31), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-255-206.dyn.columbia.edu (160.39.255.206), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 147.5kB received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.8kB received
	dyn-160-39-254-125.dyn.columbia.edu (160.39.254.125), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	dyn-160-39-252-88.dyn.columbia.edu (160.39.252.88), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.3kB received
	dyn-160-39-254-105.dyn.columbia.edu (160.39.254.105), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-241-117.dyn.columbia.edu (160.39.241.117), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 19.1kB received
	dyn-160-39-247-77.dyn.columbia.edu (160.39.247.77), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 474 Bytes received
	dyn-160-39-255-51.dyn.columbia.edu (160.39.255.51), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 18.5kB received
	dyn-160-39-254-113.dyn.columbia.edu (160.39.254.113), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.0kB received
	dyn-wireless-245-83.dyn.columbia.edu (160.39.245.83), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 16.1kB received
	capture-39-244-145.net.columbia.edu (10.39.244.145), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.4kB received
	dyn-160-39-250-78.dyn.columbia.edu (160.39.250.78), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-255-223.dyn.columbia.edu (160.39.255.223), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-254-10.dyn.columbia.edu (160.39.254.10), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 160 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-247-247.dyn.columbia.edu (160.39.247.247), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 17.1kB received
	dyn-wireless-245-127.dyn.columbia.edu (160.39.245.127), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 160 Bytes received
	dyn-160-39-242-21.dyn.columbia.edu (160.39.242.21), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 101 Bytes received
	dyn-160-39-253-246.dyn.columbia.edu (160.39.253.246), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.3kB received
	dyn-wireless-246-147.dyn.columbia.edu (160.39.246.147), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.2kB received
	dyn-160-39-254-217.dyn.columbia.edu (160.39.254.217), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 101 Bytes received
	dyn-160-39-242-108.dyn.columbia.edu (160.39.242.108), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 19.5kB received
	dyn-160-39-254-71.dyn.columbia.edu (160.39.254.71), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 60 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 25.5kB received
	dyn-160-39-251-114.dyn.columbia.edu (160.39.251.114), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 101 Bytes received
	dyn-wireless-244-97.dyn.columbia.edu (160.39.244.97), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 65.2kB received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.4kB received
	dyn-wireless-244-221.dyn.columbia.edu (160.39.244.221), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-247-56.dyn.columbia.edu (160.39.247.56), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-253-183.dyn.columbia.edu (160.39.253.183), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.6kB received
	dyn-160-39-255-33.dyn.columbia.edu (160.39.255.33), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 89 Bytes received
	dyn-160-39-241-199.dyn.columbia.edu (160.39.241.199), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 101 Bytes received
	dyn-160-39-250-18.dyn.columbia.edu (160.39.250.18), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.8kB received
	dyn-160-39-251-41.dyn.columbia.edu (160.39.251.41), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-wireless-245-119.dyn.columbia.edu (160.39.245.119), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 87 Bytes received
	dyn-160-39-255-76.dyn.columbia.edu (160.39.255.76), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-247-183.dyn.columbia.edu (160.39.247.183), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 28.7kB received
	dyn-wireless-245-212.dyn.columbia.edu (160.39.245.212), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.2kB received
	dyn-160-39-252-222.dyn.columbia.edu (160.39.252.222), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.7kB received
	dyn-160-39-247-222.dyn.columbia.edu (160.39.247.222), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.6kB received
	dyn-160-39-243-188.dyn.columbia.edu (160.39.243.188), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-wireless-246-248.dyn.columbia.edu (160.39.246.248), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.9kB received
	dyn-160-39-251-31.dyn.columbia.edu (160.39.251.31), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 42.7kB received
	dyn-160-39-253-59.dyn.columbia.edu (160.39.253.59), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-wireless-246-56.dyn.columbia.edu (160.39.246.56), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.8kB received
	dyn-160-39-255-27.dyn.columbia.edu (160.39.255.27), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.0kB received
	dyn-wireless-244-70.dyn.columbia.edu (160.39.244.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.2kB received
	dyn-160-39-251-171.dyn.columbia.edu (160.39.251.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.2kB received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 462 Bytes received
	dyn-wireless-245-243.dyn.columbia.edu (160.39.245.243), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-253-129.dyn.columbia.edu (160.39.253.129), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.4kB received
	dyn-wireless-246-217.dyn.columbia.edu (160.39.246.217), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.3kB received
	dyn-wireless-244-174.dyn.columbia.edu (160.39.244.174), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-241-64.dyn.columbia.edu (160.39.241.64), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 323 Bytes received
	dyn-160-39-242-70.dyn.columbia.edu (160.39.242.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-243-95.dyn.columbia.edu (160.39.243.95), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 11.9kB received
	dyn-160-39-253-142.dyn.columbia.edu (160.39.253.142), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.3kB received
	dyn-wireless-246-197.dyn.columbia.edu (160.39.246.197), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 115 Bytes received
	dyn-160-39-253-38.dyn.columbia.edu (160.39.253.38), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 41 Bytes received
	dyn-160-39-250-145.dyn.columbia.edu (160.39.250.145), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 73 Bytes received
	dyn-160-39-250-38.dyn.columbia.edu (160.39.250.38), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.0kB received
	dyn-160-39-255-247.dyn.columbia.edu (160.39.255.247), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.5kB received
	dyn-160-39-252-121.dyn.columbia.edu (160.39.252.121), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.9kB received
	dyn-160-39-254-152.dyn.columbia.edu (160.39.254.152), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 29.4kB received
	dyn-160-39-252-164.dyn.columbia.edu (160.39.252.164), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-241-177.dyn.columbia.edu (160.39.241.177), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.7kB received
	dyn-160-39-252-69.dyn.columbia.edu (160.39.252.69), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-247-125.dyn.columbia.edu (160.39.247.125), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.0kB received
	dyn-160-39-252-181.dyn.columbia.edu (160.39.252.181), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.6kB received
	dyn-160-39-250-238.dyn.columbia.edu (160.39.250.238), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.2kB received
	dyn-160-39-242-249.dyn.columbia.edu (160.39.242.249), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.2kB received
	dyn-160-39-255-21.dyn.columbia.edu (160.39.255.21), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.2kB received
	dyn-wireless-244-135.dyn.columbia.edu (160.39.244.135), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.6kB received
	dyn-wireless-246-102.dyn.columbia.edu (160.39.246.102), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-252-144.dyn.columbia.edu (160.39.252.144), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 473 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 24.2kB received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.1kB received
	dyn-160-39-251-115.dyn.columbia.edu (160.39.251.115), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-247-92.dyn.columbia.edu (160.39.247.92), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-255-91.dyn.columbia.edu (160.39.255.91), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 20.8kB received
	dyn-160-39-243-229.dyn.columbia.edu (160.39.243.229), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 101 Bytes received
	dyn-160-39-252-192.dyn.columbia.edu (160.39.252.192), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.8kB received
	dyn-160-39-243-233.dyn.columbia.edu (160.39.243.233), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.9kB received
	dyn-160-39-253-79.dyn.columbia.edu (160.39.253.79), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.4kB received
	dyn-160-39-250-66.dyn.columbia.edu (160.39.250.66), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 23.7kB received
	dyn-160-39-252-59.dyn.columbia.edu (160.39.252.59), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 12.2kB received
	dyn-160-39-241-45.dyn.columbia.edu (160.39.241.45), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.7kB received
	dyn-160-39-243-241.dyn.columbia.edu (160.39.243.241), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.1kB received
	dyn-160-39-242-65.dyn.columbia.edu (160.39.242.65), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.5kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.7kB received
	dyn-160-39-247-144.dyn.columbia.edu (160.39.247.144), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	169.254.56.174 (169.254.56.174), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-wireless-245-148.dyn.columbia.edu (160.39.245.148), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.9kB received
	dyn-160-39-254-212.dyn.columbia.edu (160.39.254.212), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.1kB received
	dyn-160-39-243-184.dyn.columbia.edu (160.39.243.184), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 108 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 20.7kB received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.9kB received
	dyn-wireless-246-168.dyn.columbia.edu (160.39.246.168), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.6kB received
	dyn-160-39-241-67.dyn.columbia.edu (160.39.241.67), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 22.8kB received
	Macintosh-001CB308F1EB.local (169.254.211.40), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-251-34.dyn.columbia.edu (160.39.251.34), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.3kB received
	dyn-160-39-254-202.dyn.columbia.edu (160.39.254.202), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 179 Bytes received
	dyn-160-39-255-171.dyn.columbia.edu (160.39.255.171), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 95 Bytes received
	dyn-160-39-255-119.dyn.columbia.edu (160.39.255.119), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.8kB received
	dyn-wireless-244-232.dyn.columbia.edu (160.39.244.232), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.8kB received
	dyn-160-39-255-175.dyn.columbia.edu (160.39.255.175), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 428 Bytes received
	dyn-160-39-241-194.dyn.columbia.edu (160.39.241.194), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.3kB received
	dyn-wireless-246-35.dyn.columbia.edu (160.39.246.35), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 12.3kB received
	dyn-wireless-246-200.dyn.columbia.edu (160.39.246.200), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-247-218.dyn.columbia.edu (160.39.247.218), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 318 Bytes received
	iPhone-3.local (169.254.219.52), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 166 Bytes received
	dyn-wireless-246-85.dyn.columbia.edu (160.39.246.85), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-255-94.dyn.columbia.edu (160.39.255.94), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.0kB received
	dyn-160-39-241-173.dyn.columbia.edu (160.39.241.173), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 481 Bytes received
	169.254.32.110 (169.254.32.110), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 214 Bytes received
	dyn-wireless-245-105.dyn.columbia.edu (160.39.245.105), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.9kB received
	dyn-wireless-246-161.dyn.columbia.edu (160.39.246.161), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	Macintosh-001B63DB2922.local (169.254.138.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 360 Bytes received
	dyn-160-39-253-252.dyn.columbia.edu (160.39.253.252), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.7kB received
	dyn-160-39-250-64.dyn.columbia.edu (160.39.250.64), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.9kB received
	dyn-160-39-252-43.dyn.columbia.edu (160.39.252.43), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.4kB received
	dyn-160-39-242-73.dyn.columbia.edu (160.39.242.73), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.3kB received
	dyn-160-39-251-223.dyn.columbia.edu (160.39.251.223), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.2kB received
	dyn-160-39-250-20.dyn.columbia.edu (160.39.250.20), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-241-246.dyn.columbia.edu (160.39.241.246), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.0kB received
	Macintosh-001CB3072D0A.local (169.254.143.140), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 258 Bytes received
	dyn-160-39-252-218.dyn.columbia.edu (160.39.252.218), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 130 Bytes received
	dyn-160-39-254-185.dyn.columbia.edu (160.39.254.185), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.0kB received
	169.254.207.93 (169.254.207.93), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-160-39-252-148.dyn.columbia.edu (160.39.252.148), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.1kB received
	dyn-160-39-247-228.dyn.columbia.edu (160.39.247.228), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	169.254.207.93 (169.254.207.93), Port 49786 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-160-39-251-182.dyn.columbia.edu (160.39.251.182), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.7kB received
	dyn-160-39-251-146.dyn.columbia.edu (160.39.251.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-250-50.dyn.columbia.edu (160.39.250.50), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.3kB received
	dyn-160-39-250-159.dyn.columbia.edu (160.39.250.159), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 22.5kB received
	dyn-160-39-243-138.dyn.columbia.edu (160.39.243.138), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 163 Bytes received
	dyn-160-39-241-190.dyn.columbia.edu (160.39.241.190), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-252-187.dyn.columbia.edu (160.39.252.187), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 64 Bytes received
	dyn-160-39-242-177.dyn.columbia.edu (160.39.242.177), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.6kB received
	dyn-160-39-252-242.dyn.columbia.edu (160.39.252.242), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-wireless-245-107.dyn.columbia.edu (160.39.245.107), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.1kB received
	dyn-160-39-242-233.dyn.columbia.edu (160.39.242.233), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.3kB received
	dyn-160-39-242-179.dyn.columbia.edu (160.39.242.179), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-252-216.dyn.columbia.edu (160.39.252.216), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 447 Bytes received
	dyn-wireless-245-195.dyn.columbia.edu (160.39.245.195), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.4kB received
	dyn-160-39-252-32.dyn.columbia.edu (160.39.252.32), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-254-123.dyn.columbia.edu (160.39.254.123), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 97 Bytes received
	dyn-160-39-253-62.dyn.columbia.edu (160.39.253.62), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 19.6kB received
	dyn-wireless-246-175.dyn.columbia.edu (160.39.246.175), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 311 Bytes received
	dyn-160-39-243-218.dyn.columbia.edu (160.39.243.218), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.4kB received
	dyn-160-39-254-227.dyn.columbia.edu (160.39.254.227), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 29.1kB received
	dyn-160-39-242-168.dyn.columbia.edu (160.39.242.168), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.1kB received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 19.5kB received
	dyn-160-39-241-46.dyn.columbia.edu (160.39.241.46), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-252-129.dyn.columbia.edu (160.39.252.129), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.6kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59719 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-253-242.dyn.columbia.edu (160.39.253.242), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 40.3kB received
	dyn-160-39-241-50.dyn.columbia.edu (160.39.241.50), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.6kB received
	Gianni.local (169.254.223.124), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 362 Bytes received
	dyn-160-39-252-234.dyn.columbia.edu (160.39.252.234), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 290 Bytes received
	dyn-160-39-243-241.dyn.columbia.edu (160.39.243.241), Port 55283 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-160-39-243-241.dyn.columbia.edu (160.39.243.241), Port 55293 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-160-39-243-241.dyn.columbia.edu (160.39.243.241), Port 55292 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-wireless-245-68.dyn.columbia.edu (160.39.245.68), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-243-225.dyn.columbia.edu (160.39.243.225), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.8kB received
	dyn-160-39-243-29.dyn.columbia.edu (160.39.243.29), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-241-166.dyn.columbia.edu (160.39.241.166), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.1kB received
	dyn-160-39-241-11.dyn.columbia.edu (160.39.241.11), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 20.5kB received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.8kB received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 49257 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-wireless-244-199.dyn.columbia.edu (160.39.244.199), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 335 Bytes received
	dyn-160-39-252-192.dyn.columbia.edu (160.39.252.192), Port 56901 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-252-192.dyn.columbia.edu (160.39.252.192), Port 56900 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-243-169.dyn.columbia.edu (160.39.243.169), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.3kB received
	dyn-160-39-252-192.dyn.columbia.edu (160.39.252.192), Port 56911 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-252-192.dyn.columbia.edu (160.39.252.192), Port 56910 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-wireless-244-29.dyn.columbia.edu (160.39.244.29), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 95 Bytes received
	dyn-160-39-250-177.dyn.columbia.edu (160.39.250.177), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-251-101.dyn.columbia.edu (160.39.251.101), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-247-122.dyn.columbia.edu (160.39.247.122), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 146 Bytes received
	dyn-wireless-245-168.dyn.columbia.edu (160.39.245.168), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-247-111.dyn.columbia.edu (160.39.247.111), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-wireless-245-231.dyn.columbia.edu (160.39.245.231), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 495 Bytes received
	dyn-160-39-241-52.dyn.columbia.edu (160.39.241.52), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	PC113824047319.local (169.254.26.167), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 175 Bytes received
	dyn-160-39-247-178.dyn.columbia.edu (160.39.247.178), Port 50760 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 270 Bytes received
	dyn-160-39-247-178.dyn.columbia.edu (160.39.247.178), Port 50763 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-242-48.dyn.columbia.edu (160.39.242.48), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-wireless-246-187.dyn.columbia.edu (160.39.246.187), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-247-247.dyn.columbia.edu (160.39.247.247), Port 51741 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 360 Bytes received
	dyn-160-39-247-247.dyn.columbia.edu (160.39.247.247), Port 51743 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-wireless-244-63.dyn.columbia.edu (160.39.244.63), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-253-186.dyn.columbia.edu (160.39.253.186), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 17.0kB received
	dyn-160-39-255-170.dyn.columbia.edu (160.39.255.170), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-252-71.dyn.columbia.edu (160.39.252.71), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-wireless-246-27.dyn.columbia.edu (160.39.246.27), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76 Bytes received
	dyn-160-39-247-43.dyn.columbia.edu (160.39.247.43), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-wireless-246-220.dyn.columbia.edu (160.39.246.220), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-252-161.dyn.columbia.edu (160.39.252.161), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 309 Bytes received
	dyn-160-39-252-133.dyn.columbia.edu (160.39.252.133), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 14.6kB received
	dyn-160-39-241-71.dyn.columbia.edu (160.39.241.71), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.7kB received
	dyn-160-39-252-243.dyn.columbia.edu (160.39.252.243), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.6kB received
	dyn-160-39-250-30.dyn.columbia.edu (160.39.250.30), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.1kB received
	dyn-160-39-243-147.dyn.columbia.edu (160.39.243.147), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 94 Bytes received
	dyn-160-39-247-132.dyn.columbia.edu (160.39.247.132), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.2kB received
	dyn-wireless-246-70.dyn.columbia.edu (160.39.246.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 11.5kB received
	dyn-wireless-246-53.dyn.columbia.edu (160.39.246.53), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.6kB received
	iPhone-29.local (169.254.63.242), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-254-47.dyn.columbia.edu (160.39.254.47), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 446 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.7kB received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 49201 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-wireless-245-252.dyn.columbia.edu (160.39.245.252), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 49199 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 270 Bytes received
	dyn-160-39-251-82.dyn.columbia.edu (160.39.251.82), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-252-70.dyn.columbia.edu (160.39.252.70), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 266 Bytes received
	dyn-160-39-251-29.dyn.columbia.edu (160.39.251.29), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 362 Bytes received
	dyn-160-39-242-253.dyn.columbia.edu (160.39.242.253), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-110.dyn.columbia.edu (160.39.255.110), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-253-119.dyn.columbia.edu (160.39.253.119), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	169.254.232.210 (169.254.232.210), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-99.dyn.columbia.edu (160.39.243.99), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.9kB received
	dyn-160-39-241-28.dyn.columbia.edu (160.39.241.28), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 232 Bytes received
	dyn-wireless-246-61.dyn.columbia.edu (160.39.246.61), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-247-157.dyn.columbia.edu (160.39.247.157), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-253-34.dyn.columbia.edu (160.39.253.34), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 51.5kB received
	dyn-160-39-241-205.dyn.columbia.edu (160.39.241.205), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 155 Bytes received
	dyn-wireless-244-43.dyn.columbia.edu (160.39.244.43), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-wireless-245-84.dyn.columbia.edu (160.39.245.84), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 405 Bytes received
	dyn-160-39-251-248.dyn.columbia.edu (160.39.251.248), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 405 Bytes received
	dyn-160-39-241-220.dyn.columbia.edu (160.39.241.220), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.1kB received
	dyn-160-39-243-17.dyn.columbia.edu (160.39.243.17), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 17.0kB received
	dyn-160-39-241-134.dyn.columbia.edu (160.39.241.134), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-252-30.dyn.columbia.edu (160.39.252.30), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-254-53.dyn.columbia.edu (160.39.254.53), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	169.254.142.27 (169.254.142.27), Port 52231 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 135 Bytes received
	dyn-wireless-244-150.dyn.columbia.edu (160.39.244.150), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 181 Bytes received
	dyn-160-39-252-225.dyn.columbia.edu (160.39.252.225), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.2kB received
	dyn-160-39-252-140.dyn.columbia.edu (160.39.252.140), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 154 Bytes received
	dyn-160-39-251-226.dyn.columbia.edu (160.39.251.226), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 293 Bytes received
	dyn-160-39-242-74.dyn.columbia.edu (160.39.242.74), Port 50186 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-247-20.dyn.columbia.edu (160.39.247.20), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-253-82.dyn.columbia.edu (160.39.253.82), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-160-39-255-11.dyn.columbia.edu (160.39.255.11), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 15.6kB received
	dyn-wireless-244-203.dyn.columbia.edu (160.39.244.203), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 133.8kB received
	dyn-160-39-255-73.dyn.columbia.edu (160.39.255.73), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-wireless-245-112.dyn.columbia.edu (160.39.245.112), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 28.1kB received
	dyn-160-39-254-175.dyn.columbia.edu (160.39.254.175), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 143 Bytes received
	dyn-160-39-251-222.dyn.columbia.edu (160.39.251.222), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.2kB received
	dyn-160-39-241-186.dyn.columbia.edu (160.39.241.186), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-241-236.dyn.columbia.edu (160.39.241.236), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-241-141.dyn.columbia.edu (160.39.241.141), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.8kB received
	dyn-160-39-247-198.dyn.columbia.edu (160.39.247.198), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.9kB received
	dyn-160-39-247-33.dyn.columbia.edu (160.39.247.33), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 96 Bytes received
	dyn-160-39-251-189.dyn.columbia.edu (160.39.251.189), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 10.8kB received
	Victoria.local (169.254.133.150), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.6kB received
	dyn-160-39-241-60.dyn.columbia.edu (160.39.241.60), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.7kB received
	dyn-160-39-252-19.dyn.columbia.edu (160.39.252.19), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	dyn-160-39-247-101.dyn.columbia.edu (160.39.247.101), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.3kB received
	dyn-160-39-255-61.dyn.columbia.edu (160.39.255.61), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	169.254.142.27 (169.254.142.27), Port 5353 (mdns), Protocol 17 (UDP), 0.6kB sent, 4.8kB received
	169.254.131.122 (169.254.131.122), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-243-252.dyn.columbia.edu (160.39.243.252), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	169.254.131.122 (169.254.131.122), Port 49698 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 138 Bytes received
	dyn-wireless-245-81.dyn.columbia.edu (160.39.245.81), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	169.254.142.27 (169.254.142.27), Port 52217 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 135 Bytes received
	dyn-160-39-242-158.dyn.columbia.edu (160.39.242.158), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	RENAPC.local (169.254.251.219), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 1.3kB received
	dyn-160-39-241-106.dyn.columbia.edu (160.39.241.106), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.6kB received
	dyn-wireless-245-163.dyn.columbia.edu (160.39.245.163), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 34.8kB received
	dyn-160-39-241-81.dyn.columbia.edu (160.39.241.81), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 96 Bytes received
	dyn-160-39-243-237.dyn.columbia.edu (160.39.243.237), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 422 Bytes received
	dyn-160-39-253-69.dyn.columbia.edu (160.39.253.69), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.4kB received
	dyn-160-39-252-143.dyn.columbia.edu (160.39.252.143), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 22.1kB received
	dyn-160-39-254-146.dyn.columbia.edu (160.39.254.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	dyn-wireless-245-47.dyn.columbia.edu (160.39.245.47), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 446 Bytes received
	dyn-160-39-241-188.dyn.columbia.edu (160.39.241.188), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-241-99.dyn.columbia.edu (160.39.241.99), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-242-30.dyn.columbia.edu (160.39.242.30), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 0.6kB received
	dyn-160-39-242-66.dyn.columbia.edu (160.39.242.66), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 438 Bytes received
	dyn-wireless-244-178.dyn.columbia.edu (160.39.244.178), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.3kB received
	dyn-160-39-243-80.dyn.columbia.edu (160.39.243.80), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.5kB received
	169.254.243.188 (169.254.243.188), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-wireless-246-195.dyn.columbia.edu (160.39.246.195), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 69 Bytes received
	dyn-160-39-243-190.dyn.columbia.edu (160.39.243.190), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	169.254.171.80 (169.254.171.80), Port 50522 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	169.254.171.80 (169.254.171.80), Port 50521 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 45 Bytes received
	dyn-160-39-253-141.dyn.columbia.edu (160.39.253.141), Port 53164 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-160-39-253-141.dyn.columbia.edu (160.39.253.141), Port 53167 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	169.254.139.91 (169.254.139.91), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-wireless-245-71.dyn.columbia.edu (160.39.245.71), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 15.6kB received
	dyn-wireless-246-146.dyn.columbia.edu (160.39.246.146), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-wireless-244-49.dyn.columbia.edu (160.39.244.49), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 16.8kB received
	dyn-160-39-254-93.dyn.columbia.edu (160.39.254.93), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	192.168.0.5 (192.168.0.5), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 244 Bytes received
	dyn-160-39-242-65.dyn.columbia.edu (160.39.242.65), Port 52445 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	169.254.215.187 (169.254.215.187), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-242-65.dyn.columbia.edu (160.39.242.65), Port 52430 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-254-235.dyn.columbia.edu (160.39.254.235), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.5kB received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-253-212.dyn.columbia.edu (160.39.253.212), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.0kB received
	dyn-160-39-254-157.dyn.columbia.edu (160.39.254.157), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-251-206.dyn.columbia.edu (160.39.251.206), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-250-183.dyn.columbia.edu (160.39.250.183), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-wireless-246-45.dyn.columbia.edu (160.39.246.45), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.2kB received
	dyn-160-39-250-102.dyn.columbia.edu (160.39.250.102), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.8kB received
	dyn-160-39-241-183.dyn.columbia.edu (160.39.241.183), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 213 Bytes received
	dyn-wireless-245-246.dyn.columbia.edu (160.39.245.246), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.2kB received
	dyn-160-39-255-243.dyn.columbia.edu (160.39.255.243), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-254-167.dyn.columbia.edu (160.39.254.167), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 7.7kB received
	dyn-wireless-244-95.dyn.columbia.edu (160.39.244.95), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 128 Bytes received
	dyn-160-39-253-141.dyn.columbia.edu (160.39.253.141), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.1kB received
	Macintosh-001CB370773E.local (169.254.216.251), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 298 Bytes received
	dyn-wireless-244-77.dyn.columbia.edu (160.39.244.77), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-wireless-245-53.dyn.columbia.edu (160.39.245.53), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 12.7kB received
	dyn-160-39-243-79.dyn.columbia.edu (160.39.243.79), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 466 Bytes received
	dyn-160-39-241-227.dyn.columbia.edu (160.39.241.227), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 496 Bytes received
	dyn-160-39-255-158.dyn.columbia.edu (160.39.255.158), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 8.5kB received
	dyn-ec-195-52.dyn.columbia.edu (160.39.195.52), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 47.3kB received
	dyn-160-39-242-161.dyn.columbia.edu (160.39.242.161), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 323 Bytes received
	dyn-wireless-246-241.dyn.columbia.edu (160.39.246.241), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.0kB received
	dyn-160-39-253-153.dyn.columbia.edu (160.39.253.153), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 65 Bytes received
	169.254.46.255 (169.254.46.255), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 48 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.6kB received
	D610C35GS81.local (169.254.73.136), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 427 Bytes received
	169.254.142.27 (169.254.142.27), Port 52195 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 180 Bytes received
	dyn-160-39-242-120.dyn.columbia.edu (160.39.242.120), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-241-139.dyn.columbia.edu (160.39.241.139), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 17.1kB received
	dyn-wireless-245-82.dyn.columbia.edu (160.39.245.82), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 446 Bytes received
	dyn-160-39-250-236.dyn.columbia.edu (160.39.250.236), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-252-239.dyn.columbia.edu (160.39.252.239), Port 53695 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-253-211.dyn.columbia.edu (160.39.253.211), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 53 Bytes received
	dyn-160-39-252-239.dyn.columbia.edu (160.39.252.239), Port 53679 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-252-239.dyn.columbia.edu (160.39.252.239), Port 53678 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-252-239.dyn.columbia.edu (160.39.252.239), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.7kB received
	dyn-160-39-251-175.dyn.columbia.edu (160.39.251.175), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 372 Bytes received
	169.254.167.26 (169.254.167.26), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 6.3kB received
	dyn-160-39-250-159.dyn.columbia.edu (160.39.250.159), Port 49772 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-250-159.dyn.columbia.edu (160.39.250.159), Port 49771 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-250-159.dyn.columbia.edu (160.39.250.159), Port 49769 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 270 Bytes received
	Macintosh-001B63E8D0B8.local (169.254.82.35), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-242-6.dyn.columbia.edu (160.39.242.6), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.8kB received
	dyn-160-39-253-137.dyn.columbia.edu (160.39.253.137), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.5kB received
	dyn-160-39-254-124.dyn.columbia.edu (160.39.254.124), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-242-13.dyn.columbia.edu (160.39.242.13), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.4kB received
	dyn-160-39-242-208.dyn.columbia.edu (160.39.242.208), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-243-142.dyn.columbia.edu (160.39.243.142), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-255-105.dyn.columbia.edu (160.39.255.105), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.7kB received
	169.254.215.187 (169.254.215.187), Port 54114 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 46 Bytes received
	169.254.215.187 (169.254.215.187), Port 54112 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 92 Bytes received
	dyn-160-39-242-100.dyn.columbia.edu (160.39.242.100), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.0kB received
	dyn-wireless-244-164.dyn.columbia.edu (160.39.244.164), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-254-49.dyn.columbia.edu (160.39.254.49), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 94 Bytes received
	dyn-wireless-246-211.dyn.columbia.edu (160.39.246.211), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-252-97.dyn.columbia.edu (160.39.252.97), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-250-139.dyn.columbia.edu (160.39.250.139), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 493 Bytes received
	Macintosh-001CB301506E.local (169.254.123.34), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 318 Bytes received
	Anthony.local (169.254.74.215), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 82 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	mob-117-191.barnard.columbia.edu (160.39.117.191), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-250-205.dyn.columbia.edu (160.39.250.205), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.8kB received
	dyn-160-39-252-203.dyn.columbia.edu (160.39.252.203), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 15.8kB received
	dyn-160-39-247-47.dyn.columbia.edu (160.39.247.47), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 116 Bytes received
	169.254.215.187 (169.254.215.187), Port 54106 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 46 Bytes received
	dyn-160-39-241-4.dyn.columbia.edu (160.39.241.4), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 4.3kB received
	dyn-160-39-243-117.dyn.columbia.edu (160.39.243.117), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.8kB received
	dyn-wireless-246-96.dyn.columbia.edu (160.39.246.96), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-120.dyn.columbia.edu (160.39.255.120), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-252-27.dyn.columbia.edu (160.39.252.27), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-243-58.dyn.columbia.edu (160.39.243.58), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.1kB received
	dyn-160-39-243-57.dyn.columbia.edu (160.39.243.57), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-wireless-244-244.dyn.columbia.edu (160.39.244.244), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.6kB received
	dyn-160-39-251-73.dyn.columbia.edu (160.39.251.73), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 13.3kB received
	dyn-wireless-244-226.dyn.columbia.edu (160.39.244.226), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 9.0kB received
	dyn-160-39-250-13.dyn.columbia.edu (160.39.250.13), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-wireless-245-42.dyn.columbia.edu (160.39.245.42), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.2kB received
	dyn-160-39-254-46.dyn.columbia.edu (160.39.254.46), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-253-244.dyn.columbia.edu (160.39.253.244), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	iPhone-250.local (169.254.215.52), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 434 Bytes received
	dyn-wireless-244-31.dyn.columbia.edu (160.39.244.31), Port 58483 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 270 Bytes received
	dyn-wireless-244-31.dyn.columbia.edu (160.39.244.31), Port 58488 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-252-84.dyn.columbia.edu (160.39.252.84), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-225.dyn.columbia.edu (160.39.255.225), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-wireless-245-204.dyn.columbia.edu (160.39.245.204), Port 57761 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-wireless-245-204.dyn.columbia.edu (160.39.245.204), Port 57760 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 90 Bytes received
	dyn-160-39-251-144.dyn.columbia.edu (160.39.251.144), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 96 Bytes received
	dyn-160-39-252-28.dyn.columbia.edu (160.39.252.28), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-255-87.dyn.columbia.edu (160.39.255.87), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-247-154.dyn.columbia.edu (160.39.247.154), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-242-223.dyn.columbia.edu (160.39.242.223), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.9kB received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 95 Bytes received
	capture-39-244-16.net.columbia.edu (10.39.244.16), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 84 Bytes received
	dyn-160-39-253-207.dyn.columbia.edu (160.39.253.207), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	169.254.114.206 (169.254.114.206), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 48 Bytes received
	dyn-160-39-241-23.dyn.columbia.edu (160.39.241.23), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 446 Bytes received
	dyn-wireless-246-228.dyn.columbia.edu (160.39.246.228), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 151 Bytes received
	dyn-wal-177-106.dyn.columbia.edu (160.39.177.106), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 275 Bytes received
	dyn-160-39-253-206.dyn.columbia.edu (160.39.253.206), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 371 Bytes received
	dyn-160-39-250-151.dyn.columbia.edu (160.39.250.151), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 319 Bytes received
	dyn-160-39-247-205.dyn.columbia.edu (160.39.247.205), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 5.9kB received
	dyn-160-39-255-125.dyn.columbia.edu (160.39.255.125), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 64 Bytes received
	dyn-160-39-243-239.dyn.columbia.edu (160.39.243.239), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-243-124.dyn.columbia.edu (160.39.243.124), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 64 Bytes received
	dyn-160-39-243-96.dyn.columbia.edu (160.39.243.96), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 33 Bytes received
	dyn-160-39-243-59.dyn.columbia.edu (160.39.243.59), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 479 Bytes received
	dyn-160-39-242-40.dyn.columbia.edu (160.39.242.40), Port 5353 (mdns), Protocol 17 (UDP), 294 Bytes sent, 0.6kB received
	dyn-wireless-245-29.dyn.columbia.edu (160.39.245.29), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 146 Bytes received
	dyn-160-39-255-236.dyn.columbia.edu (160.39.255.236), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-250-93.dyn.columbia.edu (160.39.250.93), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-250-34.dyn.columbia.edu (160.39.250.34), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 97 Bytes received
	dyn-wireless-245-151.dyn.columbia.edu (160.39.245.151), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 84 Bytes received
	dyn-160-39-251-67.dyn.columbia.edu (160.39.251.67), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 82 Bytes received
	dyn-160-39-252-245.dyn.columbia.edu (160.39.252.245), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 141 Bytes received
	dyn-160-39-241-11.dyn.columbia.edu (160.39.241.11), Port 51562 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 270 Bytes received
	dyn-160-39-247-58.dyn.columbia.edu (160.39.247.58), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-wireless-246-80.dyn.columbia.edu (160.39.246.80), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	10.0.1.1 (10.0.1.1), Port 53 (domain), Protocol 17 (UDP), 507 Bytes sent, 233 Bytes received
	10.0.1.198 (10.0.1.198), Port 5353 (mdns), Protocol 17 (UDP), 0 Bytes sent, 76 Bytes received
</pre>
</div>
<p>and for nmbd:</p>
<div style="height: 20em; overflow: scroll;">
<pre>
Connection report for process: nmbd (/usr/sbin/nmbd)
Total: 8.7kB sent, 442.9kB received
	dyn-160-39-254-144.dyn.columbia.edu (160.39.254.144), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 7.6kB received
	dyn-160-39-243-130.dyn.columbia.edu (160.39.243.130), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 4.4kB received
	dyn-160-39-255-143.dyn.columbia.edu (160.39.255.143), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-254-14.dyn.columbia.edu (160.39.254.14), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-255-113.dyn.columbia.edu (160.39.255.113), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-29.dyn.columbia.edu (160.39.254.29), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-242-86.dyn.columbia.edu (160.39.242.86), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-87.dyn.columbia.edu (160.39.255.87), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 12.5kB received
	dyn-160-39-242-150.dyn.columbia.edu (160.39.242.150), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 8.6kB received
	dyn-160-39-243-86.dyn.columbia.edu (160.39.243.86), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59773 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-168.dyn.columbia.edu (160.39.254.168), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-243-92.dyn.columbia.edu (160.39.243.92), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-242-89.dyn.columbia.edu (160.39.242.89), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 49247 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 49246 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-168.dyn.columbia.edu (160.39.254.168), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 174 Bytes received
	dyn-160-39-242-150.dyn.columbia.edu (160.39.242.150), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 8.8kB received
	dyn-160-39-243-92.dyn.columbia.edu (160.39.243.92), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-242-30.dyn.columbia.edu (160.39.242.30), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-243-204.dyn.columbia.edu (160.39.243.204), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-126.dyn.columbia.edu (160.39.254.126), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.2kB received
	dyn-160-39-242-183.dyn.columbia.edu (160.39.242.183), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 16.1kB received
	dyn-160-39-255-182.dyn.columbia.edu (160.39.255.182), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.6kB received
	dyn-160-39-255-113.dyn.columbia.edu (160.39.255.113), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-243-130.dyn.columbia.edu (160.39.243.130), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.2kB received
	dyn-160-39-255-103.dyn.columbia.edu (160.39.255.103), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 9.0kB received
	dyn-160-39-242-239.dyn.columbia.edu (160.39.242.239), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 17.7kB received
	lk7e8504.chemistry.columbia.edu (128.59.112.52), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 5.1kB received
	dyn-160-39-242-44.dyn.columbia.edu (160.39.242.44), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 4.1kB received
	160.39.243.255 (160.39.243.255), Port 138 (netbios-dgm), Protocol 17 (UDP), 3.1kB sent, 0 Bytes received
	lime.cc.columbia.edu (128.59.59.119), Port 137 (netbios-ns), Protocol 17 (UDP), 0.5kB sent, 0.5kB received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.1kB received
	dyn-160-39-242-103.dyn.columbia.edu (160.39.242.103), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-242-103.dyn.columbia.edu (160.39.242.103), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-243-240.dyn.columbia.edu (160.39.243.240), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-191.dyn.columbia.edu (160.39.254.191), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-242-152.dyn.columbia.edu (160.39.242.152), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.3kB received
	dyn-160-39-243-240.dyn.columbia.edu (160.39.243.240), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-255-143.dyn.columbia.edu (160.39.255.143), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 14.2kB received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55974 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55973 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55972 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-254-165.dyn.columbia.edu (160.39.254.165), Port 50619 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-165.dyn.columbia.edu (160.39.254.165), Port 50624 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-41.dyn.columbia.edu (160.39.254.41), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-254-165.dyn.columbia.edu (160.39.254.165), Port 50617 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-243-86.dyn.columbia.edu (160.39.243.86), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 375 Bytes received
	dyn-160-39-242-87.dyn.columbia.edu (160.39.242.87), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-243-26.dyn.columbia.edu (160.39.243.26), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-160-39-243-171.dyn.columbia.edu (160.39.243.171), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.6kB received
	dyn-160-39-242-207.dyn.columbia.edu (160.39.242.207), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.5kB received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-44.dyn.columbia.edu (160.39.255.44), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-94.dyn.columbia.edu (160.39.255.94), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-53.dyn.columbia.edu (160.39.254.53), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-243-51.dyn.columbia.edu (160.39.243.51), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-242-158.dyn.columbia.edu (160.39.242.158), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 59295 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-92.dyn.columbia.edu (160.39.255.92), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52512 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49542 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49541 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49540 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59770 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56794 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-232.dyn.columbia.edu (160.39.242.232), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-243-216.dyn.columbia.edu (160.39.243.216), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56786 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56793 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-76.dyn.columbia.edu (160.39.255.76), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.8kB received
	dyn-160-39-242-241.dyn.columbia.edu (160.39.242.241), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 4.3kB received
	dyn-160-39-242-57.dyn.columbia.edu (160.39.242.57), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 10.3kB received
	dyn-160-39-254-185.dyn.columbia.edu (160.39.254.185), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-242-89.dyn.columbia.edu (160.39.242.89), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-242-241.dyn.columbia.edu (160.39.242.241), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-243-77.dyn.columbia.edu (160.39.243.77), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-187.dyn.columbia.edu (160.39.254.187), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.8kB received
	dyn-160-39-254-64.dyn.columbia.edu (160.39.254.64), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	dyn-160-39-242-250.dyn.columbia.edu (160.39.242.250), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	dyn-160-39-254-171.dyn.columbia.edu (160.39.254.171), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-254-143.dyn.columbia.edu (160.39.254.143), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.7kB received
	dyn-160-39-243-3.dyn.columbia.edu (160.39.243.3), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-101.dyn.columbia.edu (160.39.254.101), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-242-90.dyn.columbia.edu (160.39.242.90), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-242-232.dyn.columbia.edu (160.39.242.232), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 375 Bytes received
	dyn-160-39-242-207.dyn.columbia.edu (160.39.242.207), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-81.dyn.columbia.edu (160.39.254.81), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-242-90.dyn.columbia.edu (160.39.242.90), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-32.dyn.columbia.edu (160.39.255.32), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-242-74.dyn.columbia.edu (160.39.242.74), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-160-39-255-146.dyn.columbia.edu (160.39.255.146), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-243-155.dyn.columbia.edu (160.39.243.155), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-242-250.dyn.columbia.edu (160.39.242.250), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-255-101.dyn.columbia.edu (160.39.255.101), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-254-18.dyn.columbia.edu (160.39.254.18), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.4kB received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-212.dyn.columbia.edu (160.39.254.212), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-255-44.dyn.columbia.edu (160.39.255.44), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 4.2kB received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.2kB received
	dyn-160-39-255-223.dyn.columbia.edu (160.39.255.223), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-243-152.dyn.columbia.edu (160.39.243.152), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-243-126.dyn.columbia.edu (160.39.243.126), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.0kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-242-87.dyn.columbia.edu (160.39.242.87), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 200 Bytes received
	dyn-160-39-243-155.dyn.columbia.edu (160.39.243.155), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-243-98.dyn.columbia.edu (160.39.243.98), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-160-39-243-98.dyn.columbia.edu (160.39.243.98), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-255-245.dyn.columbia.edu (160.39.255.245), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-254-173.dyn.columbia.edu (160.39.254.173), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.6kB received
	dyn-160-39-254-18.dyn.columbia.edu (160.39.254.18), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-255-112.dyn.columbia.edu (160.39.255.112), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 412 Bytes received
	dyn-160-39-255-157.dyn.columbia.edu (160.39.255.157), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 417 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51125 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.5kB received
	dyn-160-39-243-226.dyn.columbia.edu (160.39.243.226), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59767 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-243-82.dyn.columbia.edu (160.39.243.82), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 340 Bytes received
	dyn-160-39-243-234.dyn.columbia.edu (160.39.243.234), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-242-25.dyn.columbia.edu (160.39.242.25), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-242-136.dyn.columbia.edu (160.39.242.136), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.4kB received
	dyn-160-39-242-159.dyn.columbia.edu (160.39.242.159), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 4.4kB received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-255-188.dyn.columbia.edu (160.39.255.188), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-243-171.dyn.columbia.edu (160.39.243.171), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.6kB received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-254-126.dyn.columbia.edu (160.39.254.126), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-255-32.dyn.columbia.edu (160.39.255.32), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-254-29.dyn.columbia.edu (160.39.254.29), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 221 Bytes received
	dyn-160-39-242-25.dyn.columbia.edu (160.39.242.25), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 11.9kB received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-151.dyn.columbia.edu (160.39.243.151), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 50358 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-135.dyn.columbia.edu (160.39.242.135), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-254-144.dyn.columbia.edu (160.39.254.144), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 50270 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-26.dyn.columbia.edu (160.39.243.26), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-180.dyn.columbia.edu (160.39.255.180), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 200 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 62842 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59764 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-249.dyn.columbia.edu (160.39.255.249), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51123 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-212.dyn.columbia.edu (160.39.254.212), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55789 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-72.dyn.columbia.edu (160.39.242.72), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 407 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.0kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55786 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62713 (unnamed), Protocol 17 (UDP), 186 Bytes sent, 150 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62718 (unnamed), Protocol 17 (UDP), 186 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53824 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53823 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53822 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53828 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53827 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53826 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53825 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-152.dyn.columbia.edu (160.39.242.152), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-242-206.dyn.columbia.edu (160.39.242.206), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 250 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62717 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62716 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62715 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62714 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62719 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-206.dyn.columbia.edu (160.39.242.206), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 348 Bytes received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 200 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53214 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 2.1kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55787 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-152.dyn.columbia.edu (160.39.243.152), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-39.dyn.columbia.edu (160.39.243.39), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62712 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55788 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-178.dyn.columbia.edu (160.39.243.178), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-242-74.dyn.columbia.edu (160.39.242.74), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-255-223.dyn.columbia.edu (160.39.255.223), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 200 Bytes received
	dyn-160-39-243-35.dyn.columbia.edu (160.39.243.35), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.7kB received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49646 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49645 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-128.dyn.columbia.edu (160.39.243.128), Port 62700 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-94.dyn.columbia.edu (160.39.242.94), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-243-178.dyn.columbia.edu (160.39.243.178), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-242-246.dyn.columbia.edu (160.39.242.246), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.8kB received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50554 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50553 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50552 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-94.dyn.columbia.edu (160.39.242.94), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-90.dyn.columbia.edu (160.39.255.90), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-246.dyn.columbia.edu (160.39.242.246), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54238 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-44.dyn.columbia.edu (160.39.242.44), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-21.dyn.columbia.edu (160.39.255.21), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54237 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-121.dyn.columbia.edu (160.39.243.121), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 5.8kB received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-150.dyn.columbia.edu (160.39.243.150), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57470 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57471 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54240 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54241 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-188.dyn.columbia.edu (160.39.255.188), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59761 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-29.dyn.columbia.edu (160.39.243.29), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 18.0kB received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55785 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-81.dyn.columbia.edu (160.39.254.81), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 62836 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-103.dyn.columbia.edu (160.39.255.103), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53821 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-244.dyn.columbia.edu (160.39.254.244), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 500 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50037 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50038 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-17.dyn.columbia.edu (160.39.242.17), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.8kB received
	dyn-160-39-243-87.dyn.columbia.edu (160.39.243.87), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.2kB received
	dyn-160-39-243-212.dyn.columbia.edu (160.39.243.212), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-254-244.dyn.columbia.edu (160.39.254.244), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.2kB received
	dyn-160-39-254-187.dyn.columbia.edu (160.39.254.187), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-243-216.dyn.columbia.edu (160.39.243.216), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-243-212.dyn.columbia.edu (160.39.243.212), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59758 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59436 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-239.dyn.columbia.edu (160.39.243.239), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.9kB received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59435 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59434 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57464 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57466 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57465 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57467 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-142.dyn.columbia.edu (160.39.243.142), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.8kB received
	dyn-160-39-255-180.dyn.columbia.edu (160.39.255.180), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 118 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59432 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59431 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-3.dyn.columbia.edu (160.39.243.3), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-254-156.dyn.columbia.edu (160.39.254.156), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 388 Bytes received
	dyn-160-39-254-227.dyn.columbia.edu (160.39.254.227), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-243-39.dyn.columbia.edu (160.39.243.39), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59430 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59429 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-227.dyn.columbia.edu (160.39.254.227), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-255-48.dyn.columbia.edu (160.39.255.48), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51113 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59757 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-48.dyn.columbia.edu (160.39.255.48), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 174 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55942 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55941 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55940 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 49522 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55939 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55938 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55937 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55936 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-226.dyn.columbia.edu (160.39.243.226), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-191.dyn.columbia.edu (160.39.254.191), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 402 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53211 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-133.dyn.columbia.edu (160.39.254.133), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 49176 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-75.dyn.columbia.edu (160.39.254.75), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.8kB received
	dyn-160-39-255-94.dyn.columbia.edu (160.39.255.94), Port 62646 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-94.dyn.columbia.edu (160.39.255.94), Port 62645 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54233 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54232 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54231 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59426 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55781 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-31.dyn.columbia.edu (160.39.242.31), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-242-87.dyn.columbia.edu (160.39.242.87), Port 50158 (unnamed), Protocol 17 (UDP), 124 Bytes sent, 100 Bytes received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 59112 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51078 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51079 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52505 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52504 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 53153 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49537 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-223.dyn.columbia.edu (160.39.255.223), Port 49292 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57460 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57459 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53820 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 53155 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 53154 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 56453 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52503 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52501 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49539 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49538 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49189 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49190 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52500 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-234.dyn.columbia.edu (160.39.243.234), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 250 Bytes received
	dyn-160-39-254-134.dyn.columbia.edu (160.39.254.134), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 62825 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59754 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-212.dyn.columbia.edu (160.39.255.212), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.6kB received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57456 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57455 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57457 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59737 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54230 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-125.dyn.columbia.edu (160.39.255.125), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 3.4kB received
	dyn-160-39-255-202.dyn.columbia.edu (160.39.255.202), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-242-31.dyn.columbia.edu (160.39.242.31), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 450 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54229 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 55260 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-13.dyn.columbia.edu (160.39.255.13), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.9kB received
	dyn-160-39-254-147.dyn.columbia.edu (160.39.254.147), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.5kB received
	dyn-160-39-254-125.dyn.columbia.edu (160.39.254.125), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 204 Bytes received
	dyn-160-39-254-147.dyn.columbia.edu (160.39.254.147), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-87.dyn.columbia.edu (160.39.255.87), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 51881 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55780 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 51880 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54224 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 50263 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 53139 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-160.dyn.columbia.edu (160.39.242.160), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-242-183.dyn.columbia.edu (160.39.242.183), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59716 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54192 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-87.dyn.columbia.edu (160.39.243.87), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59414 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-136.dyn.columbia.edu (160.39.242.136), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55906 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55907 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55905 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51031 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-117.dyn.columbia.edu (160.39.254.117), Port 59412 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55779 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55776 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-100.dyn.columbia.edu (160.39.242.100), Port 49612 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55778 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55777 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53206 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53209 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53208 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53207 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49188 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49187 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-123.dyn.columbia.edu (160.39.255.123), Port 64548 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55775 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51015 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51016 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-166.dyn.columbia.edu (160.39.254.166), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51014 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 51013 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52494 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52495 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52493 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 59043 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 56450 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54191 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-103.dyn.columbia.edu (160.39.243.103), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-255-199.dyn.columbia.edu (160.39.255.199), Port 56901 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-103.dyn.columbia.edu (160.39.243.103), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59713 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-225.dyn.columbia.edu (160.39.243.225), Port 57917 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-225.dyn.columbia.edu (160.39.243.225), Port 57918 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56718 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-225.dyn.columbia.edu (160.39.243.225), Port 57912 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.6kB received
	dyn-160-39-255-123.dyn.columbia.edu (160.39.255.123), Port 64544 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-246.dyn.columbia.edu (160.39.255.246), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 410 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 50979 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 50980 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-53.dyn.columbia.edu (160.39.254.53), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 348 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49627 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50546 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50544 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50545 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 50249 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50543 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 50250 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-57.dyn.columbia.edu (160.39.242.57), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.5kB received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50542 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-47.dyn.columbia.edu (160.39.243.47), Port 50244 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55772 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55771 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55773 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-69.dyn.columbia.edu (160.39.255.69), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 450 Bytes received
	dyn-160-39-255-101.dyn.columbia.edu (160.39.255.101), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55768 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55767 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-69.dyn.columbia.edu (160.39.255.69), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 348 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50024 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-200.dyn.columbia.edu (160.39.254.200), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 188 Bytes received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 50322 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50022 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56261 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50023 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50025 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49625 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56260 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59710 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-146.dyn.columbia.edu (160.39.255.146), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-242-100.dyn.columbia.edu (160.39.242.100), Port 49610 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-100.dyn.columbia.edu (160.39.242.100), Port 49604 (unnamed), Protocol 17 (UDP), 124 Bytes sent, 100 Bytes received
	dyn-160-39-242-100.dyn.columbia.edu (160.39.242.100), Port 49609 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-173.dyn.columbia.edu (160.39.254.173), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 49273 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-194.dyn.columbia.edu (160.39.255.194), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-255-194.dyn.columbia.edu (160.39.255.194), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 49272 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-242.dyn.columbia.edu (160.39.254.242), Port 49269 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-96.dyn.columbia.edu (160.39.243.96), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-243-96.dyn.columbia.edu (160.39.243.96), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 250 Bytes received
	dyn-160-39-242-113.dyn.columbia.edu (160.39.242.113), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 211 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56712 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56711 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-229.dyn.columbia.edu (160.39.243.229), Port 55526 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56678 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59707 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56683 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-149.dyn.columbia.edu (160.39.242.149), Port 56676 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 55259 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-123.dyn.columbia.edu (160.39.255.123), Port 64538 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-123.dyn.columbia.edu (160.39.255.123), Port 64543 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-65.dyn.columbia.edu (160.39.254.65), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-254-225.dyn.columbia.edu (160.39.254.225), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	dyn-160-39-255-202.dyn.columbia.edu (160.39.255.202), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-254-225.dyn.columbia.edu (160.39.254.225), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-255-199.dyn.columbia.edu (160.39.255.199), Port 56809 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-199.dyn.columbia.edu (160.39.255.199), Port 56814 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50538 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50537 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50539 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49622 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-237.dyn.columbia.edu (160.39.243.237), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57442 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57441 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57440 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-77.dyn.columbia.edu (160.39.243.77), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59702 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-94.dyn.columbia.edu (160.39.255.94), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49616 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49614 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55766 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55765 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-115.dyn.columbia.edu (160.39.255.115), Port 49613 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-75.dyn.columbia.edu (160.39.254.75), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 50313 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-13.dyn.columbia.edu (160.39.255.13), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-254-133.dyn.columbia.edu (160.39.254.133), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.8kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 50312 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-254-17.dyn.columbia.edu (160.39.254.17), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-242-158.dyn.columbia.edu (160.39.242.158), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.6kB received
	dyn-160-39-254-66.dyn.columbia.edu (160.39.254.66), Port 50307 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-229.dyn.columbia.edu (160.39.243.229), Port 55523 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-82.dyn.columbia.edu (160.39.255.82), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 53076 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-21.dyn.columbia.edu (160.39.255.21), Port 62264 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-229.dyn.columbia.edu (160.39.243.229), Port 55517 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54162 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-229.dyn.columbia.edu (160.39.243.229), Port 55522 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56250 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55898 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55897 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55896 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59699 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 55255 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 55256 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56237 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56235 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-243-201.dyn.columbia.edu (160.39.243.201), Port 55250 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-4.dyn.columbia.edu (160.39.242.4), Port 56234 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53202 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53204 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53205 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53203 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49185 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49186 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-51.dyn.columbia.edu (160.39.243.51), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 417 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52104 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52470 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52469 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49342 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 58888 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-29.dyn.columbia.edu (160.39.255.29), Port 56442 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-12.dyn.columbia.edu (160.39.243.12), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 215 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59696 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.0kB received
	dyn-160-39-254-235.dyn.columbia.edu (160.39.254.235), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 2.2kB received
	dyn-160-39-254-146.dyn.columbia.edu (160.39.254.146), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50010 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50009 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-212.dyn.columbia.edu (160.39.255.212), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-242-83.dyn.columbia.edu (160.39.242.83), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50006 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-80.dyn.columbia.edu (160.39.255.80), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50008 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50007 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50005 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 50003 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-147.dyn.columbia.edu (160.39.242.147), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 0.9kB received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49997 (unnamed), Protocol 17 (UDP), 62 Bytes sent, 50 Bytes received
	dyn-160-39-255-250.dyn.columbia.edu (160.39.255.250), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 228 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49999 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-147.dyn.columbia.edu (160.39.242.147), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49995 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59693 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-160.dyn.columbia.edu (160.39.242.160), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 450 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 0.7kB received
	160.39.243.255 (160.39.243.255), Port 137 (netbios-ns), Protocol 17 (UDP), 0.7kB sent, 0 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 413 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59690 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50528 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50530 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-154.dyn.columbia.edu (160.39.242.154), Port 50529 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-204.dyn.columbia.edu (160.39.243.204), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 350 Bytes received
	dyn-160-39-243-190.dyn.columbia.edu (160.39.243.190), Port 58882 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-36.dyn.columbia.edu (160.39.242.36), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-255-158.dyn.columbia.edu (160.39.255.158), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.1kB received
	dyn-160-39-254-235.dyn.columbia.edu (160.39.254.235), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 450 Bytes received
	dyn-160-39-242-36.dyn.columbia.edu (160.39.242.36), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 348 Bytes received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 49174 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-182.dyn.columbia.edu (160.39.255.182), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 250 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57424 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57427 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57426 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57425 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 52990 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-82.dyn.columbia.edu (160.39.255.82), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-255-129.dyn.columbia.edu (160.39.255.129), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 357 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55761 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55760 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-223.dyn.columbia.edu (160.39.255.223), Port 49262 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55762 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55764 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55763 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-129.dyn.columbia.edu (160.39.255.129), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 418 Bytes received
	dyn-160-39-254-146.dyn.columbia.edu (160.39.254.146), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 211 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59687 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57422 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-104.dyn.columbia.edu (160.39.255.104), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57421 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54128 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52087 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55875 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55874 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55876 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55872 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55873 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55871 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-14.dyn.columbia.edu (160.39.243.14), Port 55870 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52085 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53200 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53199 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53198 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 49456 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 49455 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49175 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-89.dyn.columbia.edu (160.39.254.89), Port 53197 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59684 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-78.dyn.columbia.edu (160.39.254.78), Port 49172 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51077 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54106 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54105 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 57949 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 57948 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 57947 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-234.dyn.columbia.edu (160.39.255.234), Port 57946 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52083 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52448 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52447 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52446 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52443 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52442 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49335 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-57.dyn.columbia.edu (160.39.255.57), Port 58725 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49985 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49984 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-87.dyn.columbia.edu (160.39.242.87), Port 50085 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52081 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52080 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-42.dyn.columbia.edu (160.39.254.42), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 52987 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53816 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-88.dyn.columbia.edu (160.39.254.88), Port 52986 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49329 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-146.dyn.columbia.edu (160.39.243.146), Port 49530 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55758 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-21.dyn.columbia.edu (160.39.255.21), Port 62235 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52079 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49173 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52077 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52076 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52075 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-61.dyn.columbia.edu (160.39.242.61), Port 49982 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-148.dyn.columbia.edu (160.39.242.148), Port 52078 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49331 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49330 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49334 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49333 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49332 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-35.dyn.columbia.edu (160.39.243.35), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 300 Bytes received
	dyn-160-39-243-190.dyn.columbia.edu (160.39.243.190), Port 58814 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-71.dyn.columbia.edu (160.39.255.71), Port 54104 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-190.dyn.columbia.edu (160.39.243.190), Port 58808 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51076 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49326 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49328 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49325 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49324 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49323 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-242-238.dyn.columbia.edu (160.39.242.238), Port 52440 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-52.dyn.columbia.edu (160.39.242.52), Port 49327 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49171 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-242-133.dyn.columbia.edu (160.39.242.133), Port 49172 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 62744 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-59.dyn.columbia.edu (160.39.243.59), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 1.3kB received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 51870 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59681 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-243-168.dyn.columbia.edu (160.39.243.168), Port 51869 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-239.dyn.columbia.edu (160.39.243.239), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 1.5kB received
	dyn-160-39-242-83.dyn.columbia.edu (160.39.242.83), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 400 Bytes received
	dyn-160-39-254-251.dyn.columbia.edu (160.39.254.251), Port 49454 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-106.dyn.columbia.edu (160.39.255.106), Port 62739 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-243-176.dyn.columbia.edu (160.39.243.176), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 201 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55755 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55754 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55753 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57388 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53808 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59678 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53809 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53815 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53814 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53813 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53812 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53811 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 100 Bytes received
	dyn-160-39-255-102.dyn.columbia.edu (160.39.255.102), Port 53810 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-254-211.dyn.columbia.edu (160.39.254.211), Port 138 (netbios-dgm), Protocol 17 (UDP), 0 Bytes sent, 429 Bytes received
	dyn-160-39-255-158.dyn.columbia.edu (160.39.255.158), Port 137 (netbios-ns), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-116.dyn.columbia.edu (160.39.254.116), Port 55751 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-179.dyn.columbia.edu (160.39.254.179), Port 57387 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-255-155.dyn.columbia.edu (160.39.255.155), Port 59677 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 50162 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 150 Bytes received
	dyn-160-39-243-70.dyn.columbia.edu (160.39.243.70), Port 50198 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51061 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
	dyn-160-39-254-237.dyn.columbia.edu (160.39.254.237), Port 51066 (unnamed), Protocol 17 (UDP), 0 Bytes sent, 50 Bytes received
</pre>
</div>
<p>Now, I know that mDNSResponder is the daemon behind <a href="http://developer.apple.com/networking/bonjour/index.html">Bonjour</a>, and nmbd is a &#8220;NetBIOS name server to provide NetBIOS over IP naming services to clients&#8221;, according to <a href="http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/nmbd.8.html">this man page</a>. (<a href="http://developer.apple.com/opensource/internet/bonjour.html">Bonjour page that mentions mDNSResponder</a>) (<a href="http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man8/mDNSResponder.8.html">mDNSResponder man page</a>)</p>
<p>So I don&#8217;t know whether mDNSResponder and nmbd are directly interacting with each other, or whether they&#8217;re independently reacting to being connected to a LAN with, apparently, thousands of computers. I don&#8217;t actually know how to get a count of nodes on a LAN. But it looks like this one is fairly immense.</p>
<p>(The behaviour of Finder&#8217;s Network location in pretty strange. It seems to generally list 75-90 entries, but they&#8217;re constantly changing.)</p>
<p>I sent a SIGINFO siglan to mDNSResponder as described on its man page, and then searched the system log for entries from its process ID &#8211; 2825 found. That&#8217;s a lot.</p>
<p>Also, in the time I&#8217;ve been writing this, mDNSResponder has recieved another 18MB of data. Thats a lot.</p>
<p>I don&#8217;t actually have a specific point to this post. Just publishing my observations, hoping Google will pick them up, and one day perhaps connect me to someone who may be able to help shed some light on what&#8217;s going on, and whether I may want to do something about it, or whether any of this behaviour represents a problem, that Apple should correct.</p>
<p>My primary concerns about this behaviour are for battery life, CPU utilization, and security. I&#8217;m using a power adapter right now, but I wonder how many students have found their battery life mysteriously shorter than usual when connected to Columbia&#8217;s network. (My load averages are 0.63 0.73 0.66, that&#8217;s pretty high for writing a blog post.)</p>
<p>(I&#8217;m running Mac OS X 10.5.2, build 9C31, on a 2.2GHz Santa Rosa Merom MacBook with 4GB of <a href="http://macsales.com/">OWC</a> RAM, and a 200GB 7200RPM Hitachi HDD.)</p>
]]></content:encoded>
			<wfw:commentRss>http://aviflax.com/post/bonjour-and-extremely-large-lans/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

