<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
>
<channel>
	<title>LanTopolog 2 Rated and Reviewed</title>
	<atom:link href="http://lantopolog-2.yuriy-volokitin.qarchive.org/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://lantopolog-2.yuriy-volokitin.qarchive.org/#comments</link>
	<description>Read what other users have to say about LanTopolog 2. Dozens of reviews, opinions, comments, ratings and discussions updated in real time.</description>
	<lastBuildDate><br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <b>/backup/qa/www/sub/rss/product.php</b> on line <b>32</b><br />
Sat, 07 May 2011 04:31:30 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<item>
		<title>Author: Graham Newton</title>
		<link>http://lantopolog-2.yuriy-volokitin.qarchive.org/#comment-35354</link>
		<dc:creator>Graham Newton</dc:creator>
<br />
<b>Warning</b>:  date() [<a href='function.date'>function.date</a>]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in <b>/backup/qa/www/sub/rss/product.php</b> on line <b>46</b><br />
		<pubDate>Sat, 07 May 2011 04:31:30 -0500</pubDate>
		<guid isPermaLink="true">http://lantopolog-2.yuriy-volokitin.qarchive.org/#comment-35354</guid>
		<description><![CDATA[I needed to map the network topology of our small office. I wanted to figure out which machines were connected to which switch without having to figure out the physical connections by tracing each network port to the patch panel which is a bit of a mess.  LanTopology looked just the job.  It did find the managed switches I didn\'t expect it to find the unmanaged ones but that would be a cool feature. However that was it.  I had a diagram of two switches connected together. Accurate but I already knew that. As for finding what was connected to the switches well no joy there so I had to do it manually.  A network topology goes further than just the switches. I suspect that the network topoplogy is just implemented using a bit of SNMP and all the effort is in the presentation which is quite nice.  It would be more useful in a larger office with lots of managed switches.  If you need to find out your managed switch connections then this would help.  But I would suggest if you did have that many managed switches then you would probably have some kind of documentation detailing the topology anyway.]]></description>
		<content:encoded><![CDATA[I needed to map the network topology of our small office. I wanted to figure out which machines were connected to which switch without having to figure out the physical connections by tracing each network port to the patch panel which is a bit of a mess.  LanTopology looked just the job.  It did find the managed switches I didn\'t expect it to find the unmanaged ones but that would be a cool feature. However that was it.  I had a diagram of two switches connected together. Accurate but I already knew that. As for finding what was connected to the switches well no joy there so I had to do it manually.  A network topology goes further than just the switches. I suspect that the network topoplogy is just implemented using a bit of SNMP and all the effort is in the presentation which is quite nice.  It would be more useful in a larger office with lots of managed switches.  If you need to find out your managed switch connections then this would help.  But I would suggest if you did have that many managed switches then you would probably have some kind of documentation detailing the topology anyway.]]></content:encoded>
	</item>
</channel>
</rss> 

