<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Yeah, there’s that too. We need to create
these vlans within the edge switches as well. Once created, you shouldn’t
have to touch them again. </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Or you don’t create them at the
edge, and instead just create them in the core, however that kind of kills the
advantage of extending your vlans to the edge.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<p style='margin-bottom:12.0pt'><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Matt Ashfield<br>
Network Analyst<br>
Integrated Technology Services<br>
University of New Brunswick<br>
(506) 447-3033<br>
mda@unb.ca</span></font></p>
</div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> robinson santos
[mailto:robinson.a.s.santos@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> April 19, 2007 12:31 PM<br>
<b><span style='font-weight:bold'>To:</span></b> mda@unb.ca; FreeRadius users
mailing list<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: suggestions for
multiple vlans in hundreds of switches</span></font></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-right:0cm;margin-bottom:12.0pt;margin-left:
36.0pt'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Matt,
how about the configuration that you have to have in the switch????<br>
<br>
Can you Help me????<br>
<br>
Robinson<br>
<a href="mailto:robinson.a.s.santos@gmail.com">robinson.a.s.santos@gmail.com</a></span></font></p>
<div>
<p class=MsoNormal style='margin-left:36.0pt'><span class=gmailquote><font
size=3 face="Times New Roman"><span style='font-size:12.0pt'>On 4/19/07, <b><span
style='font-weight:bold'>Matt Ashfield</span></b> <<a
href="mailto:mda@unb.ca">mda@unb.ca</a>> wrote:</span></font></span></p>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Hi,<br>
<br>
We'd like to use FR to assign users on our wired network to one of 30<br>
different vlans on campus, based on an LDAP field. Currently, we are doing<br>
this with huntgroups. Namely, we create a huntgroup for the NAS (in our <br>
case, a network switch), and then in the users file, we put the following:<br>
<br>
DEFAULT Huntgroup-Name == mySWITCH1, Ldap-Group == staff<br>
User-Name=`%{User-Name}`,<br>
Tunnel-Private-Group-Id=176,<br>
Tunnel-Type=VLAN,<br>
Fall-Through = no<br>
<br>
DEFAULT Huntgroup-Name == mySWITCH1, Ldap-Group == student<br>
User-Name=`%{User-Name}`,<br>
Tunnel-Private-Group-Id=177,<br>
Tunnel-Type=VLAN, <br>
Fall-Through = no<br>
And so on...for other groups of user like faculty, admin, etc..<br>
<br>
This seems to work. The issue is scale. I have would conceivably have to<br>
have a huntgroup definition in the huntgroups file for each NAS. And if I <br>
wanted 30 vlans, I'd have to have 30 definitions like the ones above in my<br>
users file for EACH one of my NAS's.<br>
<br>
I'm sure there's a simpler way of doing things that I'm missing. Any advice <br>
is appreciated.<br>
<br>
Thanks<br>
<br>
<br>
Matt<br>
<a href="mailto:mda@unb.ca">mda@unb.ca</a><br>
<br>
<br>
<br>
-<br>
List info/subscribe/unsubscribe? See <a
href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html
</a></span></font></p>
</div>
<p class=MsoNormal style='margin-left:36.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
</div>
</body>
</html>