Hi,
I am having strange behavior of rlm_expiration where it always returns
userlock, no matter what I put as expiration value.
my radius install is latest from git repository, with default
configuration (unchanged in any way),
rlm_expiration rejects this user, date 10 Jan 2009, although it
Previous answers to questions about user expiration told to write
dates like
Expiration := May 10 2008 21:00:00
So in your case, you should perhaps try:
Expiration := Jan 01 2009 00:00:00
Have a nice day!
Am 01.10.2008 um 11:31 schrieb Flamur Rogova:
Hi,
I am having strange
[preacct]: module files returns noop for request 5
modcall: leaving group preacct (returns ok) for request 5
Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 5
radius_xlat: '/var/log/radius/radacct/10.0.1.2/detail-20081001'
rlm_detail: /var/log/radius
Hi,
I am just updating from an old freeradius (1.1.x) to a new
one (2.1.1). Currently we have old style entries in the
proxy.conf, some entries like:
realm DEFAULT {
type = radius
authhost = 111.222.111.222:1812
accthost = 111.222.111.222:1813
secret = whatever
Radius is working fine. Your problem is with NAS:
..
rad_recv: Accounting-Request packet from host 10.0.1.2:5007, id=61,
length=271
..
Acct-Status-Type = Stop
..
Acct-Session-Time = 120
..
Acct-Terminate-Cause = Lost-Carrier
..
Connection breaks after two minutes. Debug
Marco C. Coelho wrote:
Did you put main_pool and main_pool into a fail-over section, as
documented in man unlang ?
No, and I must be blind, because I have read the section and cannot
find mention of it.
Sorry, the redundant section should do what you want.
Alan DeKok.
-
List
Olaf Gellert wrote:
Using the same configuration file (which should still be supported), we
get:
Tue Sep 30 17:19:28 2008 : Error: PROXY: Marking home server
111.222.111.222 port 1813 as zombie (it looks like it is dead).
Note: IP *and* port.
For both servers (auth at
Could someone spread some light how a new configuration (using
home_server and home_server_pool etc) should look like?
What is unclear about instructions in proxy.conf?
Ivan Kalik
Kalik Infromatika ISP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I have an issue were Freeradius 1.1.7 dies after doing a kill -HUP on
FreeBSD 7.1. I saw that there was an issue with this in version 1.1.6
but I did not see that it had been resolved. Anyone have a fix or a
work around?
Thanks,
LB
-
List info/subscribe/unsubscribe? See
I have a working FreeRadius installation used for PPPOE clients using a
Mikrotik NAS (Essentialy Linux)
I am using Freeradius to limit data a user can send/receive within a month
and automatically reset it every month.
I used an example from chilliuspot hotspot for this.
However
Lisa Besko wrote:
I have an issue were Freeradius 1.1.7 dies after doing a kill -HUP on
FreeBSD 7.1. I saw that there was an issue with this in version 1.1.6
but I did not see that it had been resolved. Anyone have a fix or a
work around?
Upgrade to 2.1.1.
Or, re-start radiusd rather
Please forgive me as I'm a newbie to Radius. I've been reading FAQs and
archived mail list for three days and haven't seen a problem similar to
mine. ntlm_auth works as expected on the command line, however it does
not work in radius. In radius it ALWAYS returns a status ok and
authenticates
[EMAIL PROTECTED] wrote:
Very specifically, I followed the (out of
date) guide by Alan DeKok called Deploying Radius
Hmm... OK. I've updated the instructions for 2.x.
exec ntlm_auth {
wait = no
That's the issue. It should say wait = yes. Sorry.
I've
Alan DeKok wrote:
For both servers (auth at 111.222.111.222:1812 and acc at port 1813)
it reports Marking _home_ server, so does it not differentiate
between both? Or is this just an oversimplification?
It doesn't matter. The server is identified by IP port, which is
what's being
Alan DeKok wrote:
Lisa Besko wrote:
I have an issue were Freeradius 1.1.7 dies after doing a kill -HUP on
FreeBSD 7.1. I saw that there was an issue with this in version 1.1.6
but I did not see that it had been resolved. Anyone have a fix or a
work around?
Upgrade to 2.1.1.
Or,
: Auth: Invalid user (rlm_sqlcounter: Maximum
monthly usage time reached): [njale/CHAP-Password] (from client OldPPPOES
port 40541 cli 00:0C:29:0B:44:66)
I kept increasing the data limit via dialupadmin till it allowed me to
connect.
Ideas?
__ NOD32 3485 (20081001) Information
--- El mié, 1/10/08, Alan DeKok [EMAIL PROTECTED] escribió:
De: Alan DeKok [EMAIL PROTECTED]
Asunto: Re: ntlm_auth works on commandline but not in radiusd.conf
Para: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Fecha: miércoles, 1 octubre, 2008 2:38
[EMAIL PROTECTED]
Hi !
I am actually setting up a freeradius server that will manage authentication
from different places (hotels actually).
I am just a beginner toward that technology, and i have one problem :
I need to create some accounts that can be enabled at different places: for
example you have an account
Guk Victor wrote:
Hi all.
I have problem with EAP-TLS. Computer with OS Windows Vista, Freeradius
1.1.3.
Immediately access to the network exists after connection, but access is
forbidden through several minutes.
This is what it is obtained:
Well. I had very similar issue. If your NAS is
dialupadmin till it allowed me to
connect...
Ideas?
__ NOD32 3485 (20081001) Information __
This message was checked by NOD32 antivirus system.
http://www.eset.com
-
List info/subscribe/unsubscribe? See
luis a wrote:
i believe that you saw the images that i sent to you to see :)
As a general rule, I ignore most private email asking for free help.
That's what the list is for.
radtest luis ..4wr123,,todoloco 127.0.0.1 0 testing123
Sending Access-Request of id 137 to 127.0.0.1
Olaf Gellert wrote:
Well, I guess the term home_server and the fact, that
in the example the IP address is 127.0.0.1 made me think
of something local, not a remote server to which
requests are proxied.
It's the users home. It's where they are authenticated. The term
is widely used in the
Hi Marcel
I don't know if i'm right, or if it's related to your problem, but if
you check the source of rlm_sqlcounter (rlm_sqlcounter.c), you may see
that this module seems really time based (Alan will correct me if i'm
wrong). Indeed the module contains a function that make it possible for
a
sorry
what they say is ...
The access point has an IP 10.0.31.x and is included within
raddb/client.conf, forget the IP 10.0.42.250 because I connect to that
network to another topic.
The server is in the 10.30.1.x , we do not need to be on the same network
because they are VLAN
http://hotjobs.mycasacorp.com/images
there are the images step by step setting up freeradius against AD
and its not working for me in the config
in the command line everything work okay but in the config he does not
check it there pals
greetings
--- El mié, 1/10/08, Alan DeKok [EMAIL
hello!!
Well, as was the theme for the month so again clarify the principle also
returned thread.
The server is installed and tested it with the test and walk in perfect
condition.
I configured the radius in the client (access point) and a local user
testing,
the user is in a notebook in which
query = SELECT SUM(AcctInputOctets - GREATEST((%b -
UNIX_TIMESTAMP(AcctStartTime)), 0))+ SUM(AcctOutputOctets -GREATEST((%b -
UNIX_TIMESTAMP(AcctStartTime)), 0)) FROM radacct WHERE UserName='%{%k}' AND
UNIX_TIMESTAMP(AcctStartTime) + AcctSessionTime '%b'
What is GREATEST((%b -
I was under impression I answered this already, but I don't see it on
the list, so here we go again:
1. Your ntlm_auth users file entry is wrong. There is no username or
DEFAULT in it.
2. Instructions clearly say to put the entry at the beginning of the
users file. What did you do - you put that
http://wiki.freeradius.org/index.php/FreeRADIUS_Wiki:FAQ#It_still_doesn.27t_work.21
Ivan Kalik
Kalik Informatika ISP
Dana 1/10/2008, super_tomtom [EMAIL PROTECTED] piše:
Hi !
I am actually setting up a freeradius server that will manage authentication
from different places (hotels actually).
The access point has an IP 10.0.31.x and is included within
raddb/client.conf, forget the IP 10.0.42.250 because I connect to that
network to another topic.
The server is in the 10.30.1.x , we do not need to be on the same network
because they are VLAN ruteables. Pinging responds well.
What could
30 matches
Mail list logo
