Alex,

Features such as 'bandwidth and port blocking" (if any) are allocated/configured on the _NAS_ (in this case a NAS port) via AV pair/s provided by RADIUS... the '802.1x Supplicant" (Client/Endpoint) in simple terms... provides a secure/standard conduit which facilitates the communication of credentials (from the Supplicant to the Authenticator).  The '802.1x Authenticator" (or NAS) _MAY_ provision/enforce Authorization for the specific endpoint in the context of a user or group... 

The management & granularity of this functionality verifies greatly by switch vendor? as a result providing this functionality across a multi-vendor environment... in a large scale deployment... is often too complex to seriously consider.

-------- Original Message --------
Subject: RE: 802.1x
From: "Alex M" <alexm@lrcommunications.net>
Date: Wed, November 02, 2005 9:10 am
To: "'FreeRadius users mailing list'"
<freeradius-users@lists.freeradius.org>

Now im totally lost...
Can u give me an example what 802.1x does?





-----Original Message-----
From: freeradius-users-bounces@lists.freeradius.org
[mailto:freeradius-users-bounces@lists.freeradius.org] On Behalf Of Alan
DeKok
Sent: Wednesday, November 02, 2005 11:04 AM
To: FreeRadius users mailing list
Subject: Re: 802.1x

"Alex M" <alexm@lrcommunications.net> wrote:
> So then such features as bandwidth and port blocking could be controlled
via
> 802.1x?

 No.

 Alan DeKok.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html