Discussion:
[Packetfence-users] Ruckus Wireless Controllers
Jordan Hinman
2012-01-03 17:53:44 UTC
Permalink
Hi there,

I was wondering if anyone has had any luck with getting a Ruckus controller
to properly disassociate and re-associate a wireless client after device
registration. I have been looking through the CLI commands to make a custom
script to do it but have not been able to find a suitable command. Any
thoughts? Thanks for the help!
--
*Jordan Hinman*
Network Analyst | Technology Services | Elk Island Catholic Schools
T: (780) 449-6484 ext. 222 | E: ***@eics.ab.ca
Paul Marin
2012-01-04 15:56:26 UTC
Permalink
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jordan,<br>
<br>
Recently, i contacted ruckus support to ask them if their
controllers could be integrated with Packetfence. This is what they
told me:<br>
<br>
First<br>
<blockquote type="cite">
<pre wrap="">RFC 3576 has been obsoleted by RFC 5176 in 2008.
Starting from v9.2, ZD supports "Disconnect Messages (DM)" sent from RADIUS server, but not "Change-of-Aurthorization (CoA)" which is also specified in RFC5176.
Depending on the customer's usage, most likely they can work around the need of CoA using DM, and the implementation of RFC 3576 &amp; RFC 5176 are compatible other than some returned error codes might be different.
</pre>
</blockquote>
And then..
<blockquote type="cite"><tt><span
style="font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">We

are working with PacketFence on qualifying our ZD/AP as
supported devices. &nbsp;We don't have a date on when they will say
we are approved as a supported WLAN vendor.</span></tt></blockquote>
<br>
I don't know which workaround can be done here. If you know which
is, please let us know. I am looking forward to get some ruckus
controllers working with packetfence.<br>
<br>
<br>
Kindly,<br>
<br>
Paul<br>
<br>
El 03/01/2012 01:23 p.m., Jordan Hinman escribi&oacute;:
<blockquote
cite="mid:CANj-YFTMFL3+t4gdNvnozRpj+***@mail.gmail.com"
type="cite">Hi there,
<div><br>
</div>
<div>I was wondering if anyone has had any luck with getting a
Ruckus controller to properly disassociate and&nbsp;re-associate&nbsp;a
wireless client after device registration. I have been looking
through the CLI commands to make a custom script to do it but
have not been able to find a&nbsp;suitable&nbsp;command. Any thoughts?
Thanks for the help!<br clear="all">
<div><br>
</div>
-- <br>
<div><b>Jordan Hinman</b></div>
<div>Network Analyst |&nbsp;Technology Services |&nbsp;Elk Island Catholic
Schools
<div>
<div>
<div>
<div>T: (780) 449-6484 ext. 222 |&nbsp;E: <a
moz-do-not-send="true"
href="mailto:***@eics.ab.ca" target="_blank">***@eics.ab.ca</a></div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
<a class="moz-txt-link-freetext" href="http://p.sf.net/sfu/intel-appdev">http://p.sf.net/sfu/intel-appdev</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Packetfence-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Packetfence-***@lists.sourceforge.net">Packetfence-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/packetfence-users">https://lists.sourceforge.net/lists/listinfo/packetfence-users</a>
</pre>
</blockquote>
<br>
</body>
</html>
Olivier Bilodeau
2012-01-05 13:57:37 UTC
Permalink
Post by Paul Marin
RFC 3576 has been obsoleted by RFC 5176 in 2008.
Starting from v9.2, ZD supports "Disconnect Messages (DM)" sent from RADIUS server, but not "Change-of-Aurthorization (CoA)" which is also specified in RFC5176.
Depending on the customer's usage, most likely they can work around the need of CoA using DM, and the implementation of RFC 3576 & RFC 5176 are compatible other than some returned error codes might be different.
Our DM implementation (based on RFC3576) should work with RFC5176. The
only reason why we haven't explicitly stated so is because we don't have
any RFC5176 hardware to test against but both are very similar.
--
Olivier Bilodeau
***@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
Loading...