They are most likely still rejected by freeradius but your NAS lets them
in. Debug NAS and see why is that happening.
Ivan Kalik
Kalik Informatika ISP
Dana 8/9/2008, "Chris Moss" <[EMAIL PROTECTED]> piše:
>Thanks for all the help on this. I finally just added those 2-3 users to
>the users file
Thanks for all the help on this. I finally just added those 2-3 users to
the users file with REJECT. I did notice that anytime it would allow
them to connect there was a simultaneous attempt from another user at
the exact time. That doesn't happen very often so it must have something
to do with
Chris Moss wrote:
> No, cache was not enabled.
Then your OS is buggy.
> Just a thought on the denying, I thought
> maybe it just couldn't get a good result one way or the other so it
> would just allow it.
Absolutely not.
> Any other thoughts on would could be causing this
> issue?
As
No, cache was not enabled. Just a thought on the denying, I thought
maybe it just couldn't get a good result one way or the other so it
would just allow it. Any other thoughts on would could be causing this
issue? Like I said this only seems to be happening on dsl customers that
constantly try
Chris Moss wrote:
> We are running version 1.1.3. We do have thousands of users in the
> passwd file, could that have something to do with it?
Maybe. Did you enable "cache" in the "unix" module? If so, have you
disabled it?
> Is there a way to
> tell the radius server that if it can't authen
>Is there a way to
>tell the radius server that if it can't authenticate to deny it.
The user attempt with "invalid" shell was rejected:
Wed Sep 3 08:33:48 2008 : Auth: rlm_unix: [username]: invalid shell
[*one Oak United Methodist:/home/loumc:/bin/false*
Wed Sep 3 08:33:48 2008 : Auth: Login inc
We are running version 1.1.3. We do have thousands of users in the
passwd file, could that have something to do with it? Is there a way to
tell the radius server that if it can't authenticate to deny it. I'm
wondering if the OS itself is getting overloaded causing this.
Chris Moss
Alan DeK
Chris Moss wrote:
> Here is an example of a user who is turned off. This shows the invalid
> shell where it pulls out part of the passwd entry of another user. Note
> the username in this is all the same user.
>
> Wed Sep 3 08:33:34 2008 : Auth: rlm_unix: [username]: invalid password
The serve
Here is an example of a user who is turned off. This shows the invalid
shell where it pulls out part of the passwd entry of another user. Note
the username in this is all the same user.
Wed Sep 3 08:33:34 2008 : Auth: rlm_unix: [username]: invalid password
Wed Sep 3 08:33:34 2008 : Auth: Logi
Here is a debug of when it works:
rad_recv: Access-Request packet from host XXX.XXX.XXX.X:1812, id=113,
length=100
User-Name = "[EMAIL PROTECTED]"
User-Password = "0844"
NAS-Identifier = "redback"
Calling-Station-Id = "mdvi11100400714"
Service-Type = Framed-Us
Chris Moss wrote:
> We've been running Freeradius for a long time without any issues. We
> typically turn a customer off by changing the password in the passwd
> file. We use the passwd file for authentication. The issue is
> intermittent the customer is DSL so they will try to log in for a couple
We've been running Freeradius for a long time without any issues. We
typically turn a customer off by changing the password in the passwd
file. We use the passwd file for authentication. The issue is
intermittent the customer is DSL so they will try to log in for a couple
of hours constantly be
12 matches
Mail list logo
