<?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>Comments on: PRIVATE-VLAN&#8217;s</title>
	<atom:link href="http://blog.ipexpert.com/2008/11/06/private-vlans/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ipexpert.com/2008/11/06/private-vlans/</link>
	<description>CCIE Candidates blog for all technical overviews relating to CCIE R&#38;S, CCIE Voice, CCIE Security &#38; CCIE SP</description>
	<lastBuildDate>Wed, 08 Sep 2010 13:02:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tyson Scott</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-180</link>
		<dc:creator>Tyson Scott</dc:creator>
		<pubDate>Fri, 04 Sep 2009 14:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-180</guid>
		<description>Symon,

Yes it is possible.  Below is a reference URL for you.

http://tinyurl.com/nkgatp

Regards,

Tyson Scott</description>
		<content:encoded><![CDATA[<p>Symon,</p>
<p>Yes it is possible.  Below is a reference URL for you.</p>
<p><a href="http://tinyurl.com/nkgatp" rel="nofollow">http://tinyurl.com/nkgatp</a></p>
<p>Regards,</p>
<p>Tyson Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyson Scott</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-3174</link>
		<dc:creator>Tyson Scott</dc:creator>
		<pubDate>Fri, 04 Sep 2009 14:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-3174</guid>
		<description>Symon,

Yes it is possible.  Below is a reference URL for you.

http://tinyurl.com/nkgatp

Regards,

Tyson Scott</description>
		<content:encoded><![CDATA[<p>Symon,</p>
<p>Yes it is possible.  Below is a reference URL for you.</p>
<p><a href="http://tinyurl.com/nkgatp" rel="nofollow">http://tinyurl.com/nkgatp</a></p>
<p>Regards,</p>
<p>Tyson Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Symon</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-179</link>
		<dc:creator>Symon</dc:creator>
		<pubDate>Fri, 04 Sep 2009 12:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-179</guid>
		<description>Hello,

I have one question: is it possible to propagate PVLAN through a trunk port on a 3560G sw? I have 2 4948 configured with PVLAN and connected with eachother using a 3560G. I cannot find any command to configure the trunk port in the 3560G user guide. Any idea?</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I have one question: is it possible to propagate PVLAN through a trunk port on a 3560G sw? I have 2 4948 configured with PVLAN and connected with eachother using a 3560G. I cannot find any command to configure the trunk port in the 3560G user guide. Any idea?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Symon</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-3173</link>
		<dc:creator>Symon</dc:creator>
		<pubDate>Fri, 04 Sep 2009 12:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-3173</guid>
		<description>Hello,

I have one question: is it possible to propagate PVLAN through a trunk port on a 3560G sw? I have 2 4948 configured with PVLAN and connected with eachother using a 3560G. I cannot find any command to configure the trunk port in the 3560G user guide. Any idea?</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I have one question: is it possible to propagate PVLAN through a trunk port on a 3560G sw? I have 2 4948 configured with PVLAN and connected with eachother using a 3560G. I cannot find any command to configure the trunk port in the 3560G user guide. Any idea?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyson Scott</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-178</link>
		<dc:creator>Tyson Scott</dc:creator>
		<pubDate>Tue, 09 Dec 2008 14:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-178</guid>
		<description>Zeeshan,

I guess it is important to understand the purpose of private vlan&#039;s.  The purpose is to seperate devices into private clusters to prevent communication from device to device.  If you then allow communication from device to device you have then effectively overcome the security features of private vlan&#039;s.

You can use proxy-arp to make it so the isolated devices can communicate with each other if it was necessary for something in the CCIE lab but it would not be a recommended security practice to ever do it in the real world in any situation that I can think of.  You would have the communication occuring on a seperate private subnet.

So proxy-arp breaks the intentional design of private vlan&#039;s.  If you want to have devices communicate with each other then you need to put the devices on seperate VLAN&#039;s.  You are effictively doing such with proxy-arp in a non recommended design.</description>
		<content:encoded><![CDATA[<p>Zeeshan,</p>
<p>I guess it is important to understand the purpose of private vlan&#8217;s.  The purpose is to seperate devices into private clusters to prevent communication from device to device.  If you then allow communication from device to device you have then effectively overcome the security features of private vlan&#8217;s.</p>
<p>You can use proxy-arp to make it so the isolated devices can communicate with each other if it was necessary for something in the CCIE lab but it would not be a recommended security practice to ever do it in the real world in any situation that I can think of.  You would have the communication occuring on a seperate private subnet.</p>
<p>So proxy-arp breaks the intentional design of private vlan&#8217;s.  If you want to have devices communicate with each other then you need to put the devices on seperate VLAN&#8217;s.  You are effictively doing such with proxy-arp in a non recommended design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyson Scott</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-3172</link>
		<dc:creator>Tyson Scott</dc:creator>
		<pubDate>Tue, 09 Dec 2008 14:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-3172</guid>
		<description>Zeeshan,

I guess it is important to understand the purpose of private vlan&#039;s.  The purpose is to seperate devices into private clusters to prevent communication from device to device.  If you then allow communication from device to device you have then effectively overcome the security features of private vlan&#039;s.

You can use proxy-arp to make it so the isolated devices can communicate with each other if it was necessary for something in the CCIE lab but it would not be a recommended security practice to ever do it in the real world in any situation that I can think of.  You would have the communication occuring on a seperate private subnet.

So proxy-arp breaks the intentional design of private vlan&#039;s.  If you want to have devices communicate with each other then you need to put the devices on seperate VLAN&#039;s.  You are effictively doing such with proxy-arp in a non recommended design.</description>
		<content:encoded><![CDATA[<p>Zeeshan,</p>
<p>I guess it is important to understand the purpose of private vlan&#8217;s.  The purpose is to seperate devices into private clusters to prevent communication from device to device.  If you then allow communication from device to device you have then effectively overcome the security features of private vlan&#8217;s.</p>
<p>You can use proxy-arp to make it so the isolated devices can communicate with each other if it was necessary for something in the CCIE lab but it would not be a recommended security practice to ever do it in the real world in any situation that I can think of.  You would have the communication occuring on a seperate private subnet.</p>
<p>So proxy-arp breaks the intentional design of private vlan&#8217;s.  If you want to have devices communicate with each other then you need to put the devices on seperate VLAN&#8217;s.  You are effictively doing such with proxy-arp in a non recommended design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeeshan Sanullah</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-177</link>
		<dc:creator>Zeeshan Sanullah</dc:creator>
		<pubDate>Fri, 07 Nov 2008 07:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-177</guid>
		<description>Thanks Tyson ...

One more thing ...

What the Cisco Documentation says that we can communicate between different secondary vlans through a layer 3 device attached to promiscuous port ..

Thus the devices must ping each other through the L3 Device .. in your topology they cannot ... is it because you have not enabled local ip proxy arp.</description>
		<content:encoded><![CDATA[<p>Thanks Tyson &#8230;</p>
<p>One more thing &#8230;</p>
<p>What the Cisco Documentation says that we can communicate between different secondary vlans through a layer 3 device attached to promiscuous port ..</p>
<p>Thus the devices must ping each other through the L3 Device .. in your topology they cannot &#8230; is it because you have not enabled local ip proxy arp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeeshan Sanullah</title>
		<link>http://blog.ipexpert.com/2008/11/06/private-vlans/comment-page-1/#comment-3171</link>
		<dc:creator>Zeeshan Sanullah</dc:creator>
		<pubDate>Fri, 07 Nov 2008 07:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=222#comment-3171</guid>
		<description>Thanks Tyson ...

One more thing ...

What the Cisco Documentation says that we can communicate between different secondary vlans through a layer 3 device attached to promiscuous port ..

Thus the devices must ping each other through the L3 Device .. in your topology they cannot ... is it because you have not enabled local ip proxy arp.</description>
		<content:encoded><![CDATA[<p>Thanks Tyson &#8230;</p>
<p>One more thing &#8230;</p>
<p>What the Cisco Documentation says that we can communicate between different secondary vlans through a layer 3 device attached to promiscuous port ..</p>
<p>Thus the devices must ping each other through the L3 Device .. in your topology they cannot &#8230; is it because you have not enabled local ip proxy arp.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
