Re: NAS-Port-Type

Webmaster ( (no email) )
Thu, 2 Jul 1998 02:00:01 +0200

>> Users defined as async should not be able to connect to the I and
vis-versa
>> users with ISDN should not be able to connect to the async.
>> That how it should be.
>>
>> But this doesn't work in my case, any ISDN user knowing the async dial up
>> number can connect et vis-versa.
>
>Are you trying to use server port access ot check attributes? Is
>this in ODBC mode or text? What does the authentication request
>look like that should fail, but doesn't?

If I use server port access, then it works: the user is denied access to
the port async ports
and allowed access to one of the 10 B channels.
But with server port access enabled, roaming users are denied access to
through Ipass (radius
doesnt recognize the type of port, of course there is no physical ports
there).

With check attributes, it doesn't work as I a explained earlier. I am using
ODBC only
In the text file it looks like this :

xxxxxxx Password = "yyyyyy", Expiration = "Aug 01 1998"
Framed-Protocol = 1
NAS-Port-Type = 2
Port-Limit = 1
User-Service = 0

the authentication process is like the following:

decrypted password:dghgdhdfgfh

sql statement: RadGetConfigs 91

loading radius defaults for this type...
SQL statement : RadGetATConfigs 'ISDN '

User-Service = Framed-user (2)
Framed-protocol = PPP (1)
Port-Limit = 1 (1)
NAS-Port-Type = ISDN (2)
Sending Ack of id 239 to c33de104
User-Service = Framed-user
Framed-protocol = PPP
Port-Limit = 1
NAS-Port-Type = ISDN