<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on How to configure a Mac VLAN ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-332230/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-24T19:40:00-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Heres the detail]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3746394]]></link>
        <description><![CDATA[It was working ok with 10.6.8 but failed with 10.7.5. Out of a classroom of 25 imacs on started up 10 came up with a red dot at login prompt, had not obtained an ip address but could be seen from the router via their mac ethernet address. After restarting numerous times these 10 machines reduced to 5. University network guru checked it all out and said sorry its the macs. My only recourse is to install 10.8 and pray it continually pings the dhcp to get an ip address. Installed 1, lost all templates and refined settings and although it comes up with a red dot on login, this fades after 2 minutes. If anyone knows how to get the os to request dhcp on boot with a virtual interface.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3746394]]></guid>
        <dc:creator><![CDATA[Unique Design]]></dc:creator>
        <pubDate>Mon, 11 Feb 2013 23:03:55 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Doubtful that after almost 2 years,]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3664430]]></link>
        <description><![CDATA[the author is going to bother with re-writing it...he/she might post a new article with more detail, but there is no reason to &quot;append&quot; this old one.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3664430]]></guid>
        <dc:creator><![CDATA[wizard57m-cnet]]></dc:creator>
        <pubDate>Fri, 27 Apr 2012 14:05:07 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[More detail needed.]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3664384]]></link>
        <description><![CDATA[The article goes a long way to tell you just enough that the feature is available and where to find it, but lacks a concrete example on how to use and implement it that people can take from reading this article.  It shows great promise, but fails to really show how it really works in a networked environment.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3664384]]></guid>
        <dc:creator><![CDATA[stre0539@...]]></dc:creator>
        <pubDate>Fri, 27 Apr 2012 10:09:15 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[RE: How to configure a Mac VLAN]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3311886]]></link>
        <description><![CDATA[This is cool!  Yet another reason I am impressed with mac.    The other responses are correct; &quot;what would this be used for?&quot;   Then I began thinking, maybe moving back and forth between VLANs as a administrator would be useful.    Could this be the first steps in prepping the OS for server features or virtualization possibly?Nonetheless, a cool feature.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3311886]]></guid>
        <dc:creator><![CDATA[david.franck@...]]></dc:creator>
        <pubDate>Sat, 19 Jun 2010 06:36:31 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[RE: How to configure a Mac VLAN]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3310643]]></link>
        <description><![CDATA[why exactly do you want to do this on the workstation? wouldnt the network be more logical to implement vlan?]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3310643]]></guid>
        <dc:creator><![CDATA[b.sikkes@...]]></dc:creator>
        <pubDate>Thu, 17 Jun 2010 04:40:08 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Configure Mac VLAN more detail needed]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3310358]]></link>
        <description><![CDATA[The article is all fine; but, it does not explain why a step is done and the impact of doing the step.Example: tags 1 through 4094 or whatever. What is a tag, what does it do, how does it relate to VLAN on W XP, etc?Unless you are already an expert in VLAN, this article is not understandable. And if you are already an expert, you don't need this article because you already know what to do.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-332230-3310358]]></guid>
        <dc:creator><![CDATA[Dalece]]></dc:creator>
        <pubDate>Wed, 16 Jun 2010 15:56:40 -0700</pubDate>
    </item>
    </channel>
</rss>

