Hello,
I am facing issue with MS CHAP authentication in Ubuntu 13.04 . Also
NTLM Authentication takes place when putting 'wait = no' in
/etc/freeradius/modules/ntlm_auth
ie
exec ntlm_auth {
wait = no
program = “/usr/bin/ntlm_auth -request-nt-key
-username=%{mschap:User-Name}
Hi,
Hello,
I am facing issue with MS CHAP authentication in Ubuntu 13.04 . Also
NTLM Authentication takes place when putting 'wait = no' in
/etc/freeradius/modules/ntlm_auth
is ntml_auth on the command line working?
Please provide some debug output.
regards
-andreas
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi.
Wondering what authentication method you are using as maybe looking at wrong
ntlm check the mschap module for its ntlm_auth incantation. Also, if you
have doubts about the AD account used to bind them follow that up. Get it
bound in
Hi,
Yesterday caught an email about the release of FR 2.2.2 on Monday to fix a
proxy problem. As I've just migrated 2 of my servers from 2.2.0 to 2.2.1 the
sudden release of 2.2.2 sounds important. What does 2.2.2 fix?
Rgds
Ale
x
-
List info/subscribe/unsubscribe? See
On 4 Oct 2013, at 10:19, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hi,
Yesterday caught an email about the release of FR 2.2.2 on Monday to fix a
proxy problem. As I've just migrated 2 of my servers from 2.2.0 to 2.2.1 the
sudden release of 2.2.2 sounds important. What does 2.2.2 fix?
Hi Clint,
On Thu, Oct 03, 2013 at 09:53:57PM +, Clint Petty wrote:
...
[detail] expand: %t - Thu Oct 3 21:45:27 2013
++[detail] returns ok
++[unix] returns ok
[radutmp] expand: /var/log/radius/radutmp - /var/log/radius/radutmp
[radutmp] expand: %{User-Name} - test
On 10/04/2013 07:02 AM, Shameek Bhattacharya wrote:
Hello,
I am facing issue with MS CHAP authentication in Ubuntu 13.04 .
Also NTLM Authentication takes place when putting 'wait = no' in
/etc/freeradius/modules/ntlm_auth
ie
exec ntlm_auth {
wait = no
wait = no is wrong here.
On 4 Oct 2013, at 10:37, Arran Cudbard-Bell a.cudba...@freeradius.org wrote:
On 4 Oct 2013, at 10:19, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hi,
Yesterday caught an email about the release of FR 2.2.2 on Monday to fix a
proxy problem. As I've just migrated 2 of my servers from 2.2.0
Hi,
a couple of logic issues that meant case/switch and if() worked different
to 2.x - thats been fixed. ..and an issue if your server does a lot of proxying
work - in which worker threads arent dealt with properly - your log file
will be full of core and module messages if you are being hit.
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request 17630 in com
ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request 17635 in com
ponent core module thread.
Fri Oct 4 11:24:14 2013 : Info: WARNING: Child is hung for
We've recently upgraded our radius servers from 2.1.12 (CentOS 6
packaged default) to 2.2.1 (latest stable from FR, built by hand).
A config that used to work under 2.1.12 no longer appears to work the
same way under 2.2.1. Our Cisco WLCs send periodic probes in the form of
a test
Yep, those are the ones. :-)
Stefan
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request
17630 in com ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request
17635 in com ponent core module thread.
Fri Oct 4
On 4 Oct 2013, at 12:00, Alex Sharaz alex.sha...@york.ac.uk wrote:
Hmm
like these then?
Fri Oct 4 11:24:12 2013 : Info: WARNING: Child is hung for request 17630 in
com
ponent core module thread.
Fri Oct 4 11:24:13 2013 : Info: WARNING: Child is hung for request 17635 in
com
ponent
Does anyone have any tips for debugging this in a minimally disruptive way?
At the moment we don't have any development WLCs but we might have to get
some so we can have a separate environment for testing. In the meantime I'm
trying to get this code block to work so we can use the newer
On 04/10/13 13:46, Arran Cudbard-Bell wrote:
If I asked particularly nicely, and promised you a beer at the next networkshop
we were both in attendance at, would you be willing to try git head?
I'll roll a v2.2.2_rc0 if it sweetens the deal any? It'd just be really good to
know that that
Hi,
If I asked particularly nicely, and promised you a beer at the next
networkshop
we were both in attendance at, would you be willing to try git head?
I'll take the beer - am running HEAD since last night on one server :-)
(as I said to Alan, i'll report at end of day)
alan
-
List
Woah! that's getting g to be lots of beer.
I'll run it on one of my outward facing servers. Point me at something I can
build and run
A
On 4 Oct 2013, at 14:33, a.l.m.bu...@lboro.ac.uk wrote:
Hi,
If I asked particularly nicely, and promised you a beer at the next
networkshop
we were
Hi
early report :(
2.2.2 HEAD still showing:
Fri Oct 4 13:20:43 2013 : Info: WARNING: Child is hung for request 3767589 in
component core module thread.
Fri Oct 4 13:20:45 2013 : Info: WARNING: Child is hung for request 3767589 in
component core module thread.
Fri Oct 4 13:20:47 2013 :
Can someone tell me if it is possible in FR to cache in memory (for a short
amount of time) Calling-Station-Id from successful machine authentications so
that subsequent user authentications can test whether the user is connecting
from an authorized device? This is a feature that is available
Using EAP? use the EAP cache and populate the entry with whatever is needed.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 10/04/2013 06:53 AM, a.l.m.bu...@lboro.ac.uk wrote:
a couple of logic issues that meant case/switch and if() worked different
to 2.x - thats been fixed.
I need a clarification. Do you mean worked differently ONLY IN 2.2.1?
But 2.2.2 is 100% logic consistent with all 2.x, except 2.2.1?
--
On Fri, Oct 04, 2013 at 09:54:29AM -0400, Garber, Neal wrote:
Can someone tell me if it is possible in FR to cache in memory
(for a short amount of time) Calling-Station-Id from successful
rlm_cache ?
http://wiki.freeradius.org/modules/Rlm_cache
Matthew
--
Matthew Newton, Ph.D.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Some things started acting differently in 2.2.1 compared to previous releases
of 2.x
2.2.2 should revert that so things behave the same - so far that seems to be
true but we are still seeing stalled module in core messages that we did not
see
On 4 Oct 2013, at 17:43, Alan Buxey a.l.m.bu...@lboro.ac.uk wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Some things started acting differently in 2.2.1 compared to previous releases
of 2.x
2.2.2 should revert that so things behave the same - so far that seems to be
true
More debug output would help. The last patch came from output sent by
Stefan. The patch seems to help. But there's an underlying issue which is
harder to debug. It looks like a Linux specific IPv6 problem. I don't see any
issue with v4.
Alan DeKok.
On 2013-10-04, at 9:41 AM,
Garber, Neal wrote:
Can someone tell me if it is possible in FR to cache in memory (for a
short amount of time) Calling-Station-Id from successful machine
authentications so that subsequent user authentications can test whether
the user is connecting from an authorized device? This is a
26 matches
Mail list logo
