Re: [Help-gnu-radius] Fall-Through and databases

[Luis Miguel Navas Santos]

Just to add some additional points to this issue.

In the table radius_passwd, would there be one row with login='userX' and
passwd='pwdX' ?

If so, the check_attribute table would have two entries for the same user
with two different Calling-Station-Id's. I think it should fail when
checking the attributes...

Regards,
Luis Miguel Navas.

----- Original Message ----- 
From: "Sergey Poznyakoff" <address@hidden>
To: "Luis Miguel Navas Santos" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, June 30, 2004 10:46 AM
Subject: Re: [Help-gnu-radius] Fall-Through and databases


> Luis Miguel Navas Santos <address@hidden> wrote:
>
> > This is a sample of the users file:
> >
> > userX        Password = "pwdX", Calling-Station-Id= "983222222",
> > Service-Type = Framed-User
> >                 Framed-IP-Address = 10.0.0.10,
> >                 Framed-IP-Netmask = 255.255.255.255,
> >                 Idle-Timeout = 3600,
> >                 Fall-Through = Yes
> >
> > userX        Password = "pwdX", Calling-Station-Id= "983333333",
> > Service-Type = Framed-User
> >                 Framed-IP-Address = 10.0.0.10,
> >                 Framed-IP-Netmask = 255.255.255.255,
> >                 Idle-Timeout = 3600,
> >                 Fall-Through = Yes
> >
>
> In both cases Fall-Through is not needed. GNU Radius always selects
> the best matching entry. So, if the request contains
> Calling-Station-Id= "983333333", radius will not even try the first entry.
>
> > My question is the following: Providing that the auth_query must return
just
> > ONE row, is it possible to use the Fall-Through attribute or is there
any
> > other mechanism to allow this behavior?
>
> Given what I said above, there should be no problem with it.
>
> Regards,
> Sergey