Hi Neal:

Thanks for the response.
authorize {

 if ("%{NAS-Port-Type}" =~ /^Wireless/){
    if ("%{NAS-Identifier}" =~ /^gktest-nas-id/){

if ("%{Called-Station-Id}" =~ /(.*):(.*)/){

update control {
%{Called-Station-SSId} = "%{2}"

If I do anything like above try and use any new variable
for example here,
%{Called-Station-SSId}

I get this error when starting radius deamon.

Sun Oct 17 18:19:02 2010 : Error: /etc/freeradius/sites-enabled/default[71]: Invalid expansion: "%{2}"

Look forward to your comments.

Best Regards

-Gyan

It happens both in update request and update control

On Fri, Oct 15, 2010 at 3:00 AM, <freeradius-devel-request@lists.freeradius.org> wrote:
Send Freeradius-Devel mailing list submissions to
       freeradius-devel@lists.freeradius.org

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.freeradius.org/mailman/listinfo/freeradius-devel
or, via email, send a message with subject or body 'help' to
       freeradius-devel-request@lists.freeradius.org

You can reach the person managing the list at
       freeradius-devel-owner@lists.freeradius.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Freeradius-Devel digest..."


Today's Topics:

  1. RE: Upgrading Free Radius Proxy functionality (Garber, Neal)


----------------------------------------------------------------------

Message: 1
Date: Thu, 14 Oct 2010 09:42:59 -0400
From: "Garber, Neal" <Neal.Garber@iberdrolausa.com>
Subject: RE: Upgrading Free Radius Proxy functionality
To: "'FreeRadius developers mailing list'"
       <freeradius-devel@lists.freeradius.org>
Message-ID:
       <3FF48394E621F14F97A9117CF92D138E5863CDAE1D@EEROCH1CMS1.Energyeast.net>

Content-Type: text/plain; charset="us-ascii"

> SSID based forwarding takes precedence over realm and default forwarding.

> Please give comments or pointers about how to include this functionality to enhance forwarding and to change order.

Use unlang.  We use Cisco APs which pass the SSID in a Cisco-AVPair attribute.  So, perhaps you could use something similar to the following in the authorize section of sites-enabled/default:

       # Adjust below to capture the SSID from the request
       # If you're not sure what attr. has SSID, look at your debug output
       # If it's not in any request attr, consult your NAS documentation on how to make it pass it
       if (Cisco-AVPair =~ /ssid=(.*)/) {
          update request {
               SSID-Name = "%{1}"
          }
       }

       # Adjust SSID and Realm names below
       # Ensure you create the realms in proxy.conf
       if (SSID-Name) {
          if (SSID-Name == "SSID1") {
             update control {
                Proxy-To-Realm = "Realm1"
             }
          }
          elseif (SSID-Name == "SSID2") {
             update control {
                Proxy-To-Realm = "Realm2"
             }
          }
       }

Also, you'll need to add SSID-Name to the dictionary file as a local attribute.  Something like the following:

ATTRIBUTE   SSID-Name                   3012    string
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freeradius.org/pipermail/freeradius-devel/attachments/20101014/e1326b84/attachment-0001.html>

------------------------------

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


End of Freeradius-Devel Digest, Vol 66, Issue 6
***********************************************