After the upgrade from 2.1.6 to 2.1.7 my two servers died 3-4 times
daily with the following error:
Thu Sep 24 19:07:13 2009 : Error: Received conflicting packet from
client AP-8 port 32777 - ID: 240 due to unfinished request 2396. Giving
up on old request.
Thu Sep 24 19:07:13 2009 : Error:
Maja Wolniewicz wrote:
After the upgrade from 2.1.6 to 2.1.7 my two servers died 3-4 times
daily with the following error:
Thu Sep 24 19:07:13 2009 : Error: Received conflicting packet from
client AP-8 port 32777 - ID: 240 due to unfinished request 2396. Giving
up on old request.
Thu Sep
Hi again all :)
I have a primary and secondary server, each of which receive accounting
requests from multiple NAS servers.
Both my servers proxy these requests to each other to stay in sync.
I would like to setup a virtual server on my secondary to handle the
incoming proxy requests from
With the above config I have listen sections for auth and acct.
Do I understand the documentation correctly if I add this to the above
existing config:
client primary_server {
ipaddr= primary_server_ip
secret= shared_secret
09/24/2009 12:03 PM, Ivan Kalik::
What RADIUS attribute would suit to account expiration?
Expiration.
I cannot find its documentation (its syntax)
A hint:
http://www.open.com.au/pipermail/radiator/2008-July/014935.html
But not more...
A help?
--
Architecte Informatique chez
09/25/2009 02:59 PM, Rakotomandimby Mihamina::
09/24/2009 12:03 PM, Ivan Kalik::
What RADIUS attribute would suit to account expiration?
Expiration.
I cannot find its documentation (its syntax)
http://www.portmasters.com/tech/docs/pdf/radius-release20.pdf
In RADIUS 1.16, if a user record
Patric wrote:
server requests_from_primary {
listen {
ipaddr = *
port = 0
type = acct
}
Delete that listen section. It conflicts with the global one.
The global one will accept packets on the accounting port, IP *, and
will look up the client. If the
09/24/2009 12:03 PM, Ivan Kalik::
What RADIUS attribute would suit to account expiration?
Expiration.
I cannot find its documentation (its syntax)
doc/rlm_expiration.
A hint:
http://www.open.com.au/pipermail/radiator/2008-July/014935.html
Why, oh why, do people trawl the internet for
Ivan Kalik wrote:
With the above config I have listen sections for auth and acct.
Do I understand the documentation correctly if I add this to the above
existing config:
client primary_server {
ipaddr= primary_server_ip
secret=
Alan DeKok wrote:
Patric wrote:
server requests_from_primary {
listen {
ipaddr = *
port = 0
type = acct
}
Delete that listen section. It conflicts with the global one.
The global one will accept packets on the accounting port, IP *, and
will look
Alan DeKok wrote:
Joe Maimon wrote:
Here is what I am doing with rlm_policy
You had control above. Why request here?
These are all the patches I am currently carrying.
OK... my $0.02 is put them in github. Fork the stable branch, apply
your patches, and send me a link to the
To resolve this should I now remove the primary server from my nas table
as I am defining it in the clients.conf ?
Yes, pick one.
Or is there a way to leave it
in the nas table and assign a virtual_server directive to it?
Yes. In 2.1.7 schema supports virtual servers but that line is
hi,
not really covered on the WIKI and there is some stuff on the mailing list
archives so it would be good for some clarification.
if a RADIUS server has a certificate that has been signed by an intermediate
certificate, what is the corretc process to ensure that the client is
happy with the
Ivan Kalik wrote:
To resolve this should I now remove the primary server from my nas table
as I am defining it in the clients.conf ?
Yes, pick one.
Or is there a way to leave it
in the nas table and assign a virtual_server directive to it?
Yes. In 2.1.7 schema supports virtual
I am out of the office until 09/28/2009.
Please contact Rob Bodenhamer with any urgent issues.
Note: This is an automated response to your message Freeradius-Users
Digest, Vol 53, Issue 104 sent on 9/25/09 8:20:21.
This is the only notification you will receive while this person is away.
-
hello,
I am running slackware 12.1 as my OS. I am running freeradius version 2.1.4.
I am also running Mysql as a backend server to freeradius. I made changed to
the Msql database on what times the wireless internet will be available to
clients. I wanted to test to see if the times that I set are
- Oorspronkelijk bericht -
Van
: Alexander Clouter [mailto:a...@digriz.org.uk]
Verzonden
: donderdag
, september
24, 2009 05:24 PM
Aan
: freeradius-users@lists.freeradius.org
Onderwerp
: Re: Mimic lower_user in FR2
Thor Spruyt thor.spr...@telenet.be wrote:
Since lower_user doesn't
I am running slackware 12.1 as my OS. I am running freeradius version
2.1.4.
I am also running Mysql as a backend server to freeradius. I made changed
to
the Msql database on what times the wireless internet will be available to
clients. I wanted to test to see if the times that I set are
Or maybe there's a better way which I don't know about to get the same
result...
Perl.
$RAD_REQUEST{'User-Name'} = lc($RAD_REQUEST{'User-Name'});
Ivan Kalik
Kalik Informatika ISP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi Ivan,
How could doing a radtest help me see if the Radius server is actually not
allowing people from using the wireless at the times I have set in the
mysql database?
thanks,
jon
On Fri, Sep 25, 2009 at 3:52 PM, Ivan Kalik t...@kalik.net wrote:
I am running slackware 12.1 as my OS. I am
Please don't tell me that you have Slackware installed and you don't
know how to find more info about radtest?
man radtest
google - radtest
etc
jon jon wrote:
Hi Ivan,
How could doing a radtest help me see if the Radius server is
actually not allowing people from using the wireless at
Alan DeKok al...@deployingradius.com wrote:
Maja Wolniewicz wrote:
After the upgrade from 2.1.6 to 2.1.7 my two servers died 3-4 times
daily with the following error:
Thu Sep 24 19:07:13 2009 : Error: Received conflicting packet from
client AP-8 port 32777 - ID: 240 due to unfinished
22 matches
Mail list logo
