<?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>All_about_network &#187; S6500</title>
	<atom:link href="http://www.kuncar.net/blog/tag/s6500/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kuncar.net/blog</link>
	<description></description>
	<lastBuildDate>Wed, 12 May 2010 00:09:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Port isolate vs. Mac Forced Forwarding</title>
		<link>http://www.kuncar.net/blog/mac-forced-forwarding/2009/</link>
		<comments>http://www.kuncar.net/blog/mac-forced-forwarding/2009/#comments</comments>
		<pubDate>Thu, 09 Apr 2009 16:28:10 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[mac-forced-forwarding]]></category>
		<category><![CDATA[port isolate]]></category>
		<category><![CDATA[S3900]]></category>
		<category><![CDATA[S5600]]></category>
		<category><![CDATA[S6500]]></category>
		<category><![CDATA[VRP 3.10]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=211</guid>
		<description><![CDATA[<img class="alignleft size-thumbnail wp-image-118" title="Huawei Logo" src="http://www.kuncar.net/blog/wp-content/uploads/2009/03/huawei_logo_001-150x150.jpg" alt="Huawei Logo" width="120" height="120" />Let me first say that these two features are supposed to do very similar things - they are designed to separate access users so their traffic cannot go directly between them without any control. This is a must as most of the attacks are actually executed from inside your own network and specifically in the same subnet where the]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/mac-forced-forwarding/2009/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>DHCP Relay quick howto</title>
		<link>http://www.kuncar.net/blog/dhcp-relay-quick-howto/2008/</link>
		<comments>http://www.kuncar.net/blog/dhcp-relay-quick-howto/2008/#comments</comments>
		<pubDate>Fri, 27 Jun 2008 14:40:53 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[DHCP]]></category>
		<category><![CDATA[DHCP relay]]></category>
		<category><![CDATA[dhcp snooping]]></category>
		<category><![CDATA[S3900]]></category>
		<category><![CDATA[S6500]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=11</guid>
		<description><![CDATA[This post is brief introduction to configuration of DHCP relay with option 82 on S3900,S5600 and S6500.

Scenario I
Let's use S3900 as an aggregation switch and relay directly from there. As the S5600 is almost the same I expect that configuration of these two devices are the same (and the configuration as well). Actually the config options are much better than on S6500.
Vlans 10 and 100 are used for the realization]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/dhcp-relay-quick-howto/2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DHCP option 82 and DHCP relay</title>
		<link>http://www.kuncar.net/blog/dhcp-option-82-and-dhcp-relay/2008/</link>
		<comments>http://www.kuncar.net/blog/dhcp-option-82-and-dhcp-relay/2008/#comments</comments>
		<pubDate>Fri, 27 Jun 2008 12:13:17 +0000</pubDate>
		<dc:creator>tnk</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[Huawei]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[DHCP]]></category>
		<category><![CDATA[DHCP relay]]></category>
		<category><![CDATA[option 82]]></category>
		<category><![CDATA[S3900]]></category>
		<category><![CDATA[S6500]]></category>
		<category><![CDATA[S8500]]></category>

		<guid isPermaLink="false">http://www.kuncar.net/blog/?p=10</guid>
		<description><![CDATA[<img class="alignleft" title="IETF logo" src="http://www.autonomic-communication.org/web/bodies/ietflogo2e.gif" alt="" width="168" height="96" />I was actually playing with DHCP relay and what I did find out is kind of interesting. For what is DHCP relay look for <a href="http://www.ietf.org/rfc/rfc3046.txt">rfc3046 </a>.
In short it is when the client sends a DHCP a broadcast message (discover) some device (usually the switch that is the client directly connected to) intercepts the packet and sends a unicast discover instead of]]></description>
		<wfw:commentRss>http://www.kuncar.net/blog/dhcp-option-82-and-dhcp-relay/2008/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
