Specifying Any Port for RADIUS Client

Det Det det.explorer at yahoo.com
Thu Sep 8 07:25:02 CEST 2011


yeah you are right. realized that the ports value is actually not in use. it actually get the shortname not the nasname which is why i get an 'unknown client' error. i left the shortname empty.



________________________________
From: Fajar A. Nugraha <list at fajar.net>
To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
Sent: Thursday, September 8, 2011 11:40 AM
Subject: Re: Specifying Any Port for RADIUS Client

On Thu, Sep 8, 2011 at 10:15 AM, Det Det <det.explorer at yahoo.com> wrote:
> please disregard this email. I thought that the 'ports' field in 'nas' table
> means the 'source' port the client will use to connect to the RADIUS server
> when it actually means the port on the RADIUS server that the client will
> connect to.

I don't think that's the case.

While the default nas table has many columns (including ports), the
default query on dialup.conf is

    nas_query = "SELECT id, nasname, shortname, type, secret, server FROM
${nas_table}"

... which should mean only those columns are used.

-- 
Fajar
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20110907/1bcaf450/attachment.html>


More information about the Freeradius-Users mailing list