- Freeradius-Users - lists.freeradius.org

rlm_exec and authentication
by Oguzhan Kayhan 03 Dec '07

03 Dec '07

Hello all, I wanna write an authentication script which will control the username&password pair from an IMAP server. Acutally the script is about ready but, i couldt find a way to execute from radius. I first tried rlm_perl which i thouhgt it will be better and easier But i had the error "undefined symbol: Perl_Tstack_sp_ptr (failed! run '/usr/sbin/freeradius -x' to find out why.)" Then i reinstalled freeradius checked the updates of perl etc but no solution.. And i decided to use rlm_exec for that. But i am not sure how will i use it as authentication. Anybody has an example regarding to that? Or even a solution for my rlm_perl Thank u Oguzhan Kayhan

2 3

EAP-TTLS help...
by Raghavendra. S 03 Dec '07

03 Dec '07

Hi All, I am configuring wpa supplicant to use EAP-TTLS on wpa supplicant ported to marvell 8686. But have few raod block. Plz help me to solve the issue. luckily i am not getting any error in RADIUS server side... *1. Getting SSL connect error.* SSL: SSL_connect:before/connect initialization SSL: (where=0x1001 ret=0x1) SSL: SSL_connect:SSLv3 write client hello A SSL: (where=0x1002 ret=0xffffffff) SSL: SSL_connect:error in SSLv3 read server hello A SSL: SSL_connect - want more data SSL: 102 bytes pending from ssl_out SSL: 102 bytes left to be sent out (of total 102 bytes) EAP: method process -> ignore=FALSE methodState=MAY_CONT decision=FAIL *2. EAP entering failure state* EAP: EAP entering state FAILURE CTRL-EVENT-EAP-FAILURE EAP authentication failed EAPOL: SUPP_PAE entering state AUTHENTICATING EAPOL: SUPP_BE entering state FAIL *my wpa_supplicant.conf as below* update_config=1 eapol_version=1 ap_scan=1 fast_reauth=1 network={ ssid="3Com" scan_ssid=1 auth_alg=OPEN proto=WPA key_mgmt=WPA-EAP IEEE8021X pairwise=TKIP CCMP group=CCMP TKIP WEP104 WEP40 eap=TTLS identity="jbibe" anonymous_identity="jbibe" password="whatever" priority=2 phase2="auth=MD5" } -Raghu -- Regards & Thanks Raghavendra. S

1 0

RE: 64-bit issues ( SNMP issues )
by Edvin Seferovic 02 Dec '07

02 Dec '07

Hi Alan, thank you ! As you mentioned - net-snmp libraries do have a problem. Although I've found a patch on their mailing list covering this problem for net-snmp 5.3.1 ( I am attaching it ). Nevertheless I cannot get any data... freeradius seems to register just fine : Sun Dec 2 20:17:11 2007 : Debug: SMUX connect try 1 Sun Dec 2 20:17:11 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 20:17:11 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 20:17:11 2007 : Debug: SMUX open password: rad Sun Dec 2 20:17:11 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 20:17:11 2007 : Debug: SMUX register priority: -1 Sun Dec 2 20:17:11 2007 : Debug: SMUX register operation: 1 Sun Dec 2 20:17:11 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 20:17:11 2007 : Debug: SMUX register priority: -1 Sun Dec 2 20:17:11 2007 : Debug: SMUX register operation: 1 Sun Dec 2 20:17:11 2007 : Debug: Listening on authentication address 172.19.10.3 port 1812 as server mac-auth Sun Dec 2 20:17:11 2007 : Debug: Listening on accounting address 172.19.10.3 port 1813 as server mac-auth Sun Dec 2 20:17:11 2007 : Debug: Listening on SNMP SMUX with OID .1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 20:17:11 2007 : Debug: Ready to process requests. Sun Dec 2 20:17:11 2007 : Debug: SMUX read start Sun Dec 2 20:17:11 2007 : Debug: SMUX read len: 6 Sun Dec 2 20:17:11 2007 : Debug: SMUX message received type: 67 rest len: 4 Sun Dec 2 20:17:11 2007 : Debug: SMUX_RRSP Sun Dec 2 20:17:11 2007 : Debug: SMUX_RRSP value: 0 errstat: 0 Sun Dec 2 20:17:11 2007 : Debug: Ready to process requests. Sun Dec 2 20:17:11 2007 : Debug: SMUX read start Sun Dec 2 20:17:11 2007 : Debug: SMUX read len: 6 Sun Dec 2 20:17:11 2007 : Debug: SMUX message received type: 67 rest len: 4 Sun Dec 2 20:17:11 2007 : Debug: SMUX_RRSP Sun Dec 2 20:17:11 2007 : Debug: SMUX_RRSP value: 0 errstat: 0 Dec 2 20:18:50 sphinx snmpd[17853]: NET-SNMP version 5.3.1 Dec 2 20:19:28 sphinx snmpd[17853]: Connection from UDP: [127.0.0.1]:32784 Dec 2 20:19:41 sphinx snmpd[17853]: [smux_accept] accepted fd 10 from 127.0.0.1:60772 Dec 2 20:19:41 sphinx snmpd[17853]: accepted smux peer: oid SNMPv2-SMI::enterprises.11344.1.1.1, descr radiusd Dec 2 20:19:48 sphinx snmpd[17853]: Connection from UDP: [127.0.0.1]:32784 sphinx:~/software# snmpwalk -v 2c -m /usr/share/snmp/mibs/RADIUS-AUTH-SERVER-MIB.txt -c public 127.0.0.1 radiusAuth RADIUS-AUTH-SERVER-MIB::radiusAuthentication = No more variables left in this MIB View (It is past the end of the MIB tree) Any ideas what might go wrong ? TIA Regards, E:S -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Sonntag, 02. Dezember 2007 17:44 To: Edvin Seferovic Subject: 64-bit issues I don't know if the net-snmp libraries are 64-bit clean, either. In any case, I've cleaned up src/main/smux.c. Please try downloading && building CVS head. Maybe that will fix it... Alan DeKok. __________ NOD32 2697 (20071202) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com

1 0

Re: FreeRADIUS ( 2 ) and SNMP - "broken pipe error" - password not accepted
by Alan DeKok 02 Dec '07

02 Dec '07

Edvin Seferovic wrote: > Is the patch already in the CVS ? Can you send me the BugID ( can't find it > :( ) ? Can you give me a hint what needs to be ajusted ? There is no patch in CVS. If it's not in bugs.freeradius.org, it's in the mailing list archives. As for a fix, the code uses "int" where it should really be either "int32" for protocol packing, or "size_t" for lengths. Once those changes are made, it should work. Alan DeKok.

2 1

Re: FreeRADIUS ( 2 ) and SNMP - "broken pipe error" - password not accepted
by Alan DeKok 02 Dec '07

02 Dec '07

Edvin Seferovic wrote: > Hello, > > I have set up FreeRADIUS ( pre2 ) and activated SNMP ( rebuilt it with > --with-snmp ... ). The snmpd is also configured with the smuxpeer and the > correct password, but password seems to be rejected. I am using snmpd-5.3.1 > on Debian Etch ( AMD64 ). Both passwords are the same. Does anyone have an > idea what might be wrong? The SMUX code in src/main doesn't appear to be 64-bit clean. There's a patch from Redhat on bugs.freeradius.org that helps, but apparently it still doesn't work. Alan DeKok.

2 1

FreeRADIUS ( 2 ) and SNMP - "broken pipe error" - password not accepted
by Edvin Seferovic 02 Dec '07

02 Dec '07

Hello, I have set up FreeRADIUS ( pre2 ) and activated SNMP ( rebuilt it with --with-snmp ... ). The snmpd is also configured with the smuxpeer and the correct password, but password seems to be rejected. I am using snmpd-5.3.1 on Debian Etch ( AMD64 ). Both passwords are the same. Does anyone have an idea what might be wrong? Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: Listening on authentication address 172.19.10.3 port 1812 as server mac-auth Sun Dec 2 09:47:20 2007 : Debug: Listening on accounting address 172.19.10.3 port 1813 as server mac-auth Sun Dec 2 09:47:20 2007 : Debug: Listening on SNMP SMUX with OID .1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX read len: 3 Sun Dec 2 09:47:20 2007 : Debug: SMUX message received type: 0 rest len: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX Unknown type: 0 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX connection closed: 12 Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX read len: 3 Sun Dec 2 09:47:20 2007 : Debug: SMUX message received type: 0 rest len: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX Unknown type: 0 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX connection closed: 12 Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX read len: 3 Sun Dec 2 09:47:20 2007 : Debug: SMUX message received type: 0 rest len: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX Unknown type: 0 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX connection closed: 12 Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX read len: 3 Sun Dec 2 09:47:20 2007 : Debug: SMUX message received type: 0 rest len: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX Unknown type: 0 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX connection closed: 12 Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX read len: 3 Sun Dec 2 09:47:20 2007 : Debug: SMUX message received type: 0 rest len: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX Unknown type: 0 Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: SMUX read start Sun Dec 2 09:47:20 2007 : Debug: SMUX connection closed: 12 Sun Dec 2 09:47:20 2007 : Debug: SMUX connect try 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX open oid: 1.3.6.1.4.1.11344.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX open progname: radiusd Sun Dec 2 09:47:20 2007 : Debug: SMUX open password: rad Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.1.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX SMUX register oid: 1.3.6.1.2.1.67.2.1.1.1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register priority: -1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register operation: 1 Sun Dec 2 09:47:20 2007 : Debug: SMUX register message send failed: Broken pipe Sun Dec 2 09:47:20 2007 : Debug: Ready to process requests. Sun Dec 2 09:47:20 2007 : Debug: Exiting... Dec 2 09:34:22 sphinx snmpd[8966]: [smux_accept] Calling accept() Dec 2 09:34:22 sphinx snmpd[8966]: [smux_accept] accepted fd 10 from 127.0.0.1:37448 Dec 2 09:34:22 sphinx snmpd[8966]: dumpx_recv: Dec 2 09:34:22 sphinx snmpd[8966]: 02 01 00 Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: dumpv_recv: Dec 2 09:34:22 sphinx snmpd[8966]: Integer:^I0 (0x00) Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 763: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] version 0, len 26, type 2 Dec 2 09:34:22 sphinx snmpd[8966]: dumpx_recv: Dec 2 09:34:22 sphinx snmpd[8966]: 06 0A 2B 06 01 04 01 D8 50 01 01 01 Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: dumpv_recv: Dec 2 09:34:22 sphinx snmpd[8966]: ObjID: Dec 2 09:34:22 sphinx snmpd[8966]: SNMPv2-SMI::enterprises.11344.1.1.1 Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 776: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] smux peer: SNMPv2-SMI::enterprises.11344.1.1.1 Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 778: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] len 14, type 6 Dec 2 09:34:22 sphinx snmpd[8966]: dumpx_recv: Dec 2 09:34:22 sphinx snmpd[8966]: 04 07 72 61 64 69 75 73 64 Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: dumpv_recv: Dec 2 09:34:22 sphinx snmpd[8966]: String:^Iradiusd Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 790: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] smux peer descr: Dec 2 09:34:22 sphinx snmpd[8966]: r Dec 2 09:34:22 sphinx snmpd[8966]: a Dec 2 09:34:22 sphinx snmpd[8966]: d Dec 2 09:34:22 sphinx snmpd[8966]: i Dec 2 09:34:22 sphinx snmpd[8966]: u Dec 2 09:34:22 sphinx snmpd[8966]: s Dec 2 09:34:22 sphinx snmpd[8966]: d Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 795: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] len 5, type 4 Dec 2 09:34:22 sphinx snmpd[8966]: dumpx_recv: Dec 2 09:34:22 sphinx snmpd[8966]: 04 03 72 61 64 Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: dumpv_recv: Dec 2 09:34:22 sphinx snmpd[8966]: String:^Irad Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 808: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] smux peer passwd: Dec 2 09:34:22 sphinx snmpd[8966]: r Dec 2 09:34:22 sphinx snmpd[8966]: a Dec 2 09:34:22 sphinx snmpd[8966]: d Dec 2 09:34:22 sphinx snmpd[8966]: Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_open_process(): mibgroup/smux/smux.c, 813: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_open_process] len 0, type 4 Dec 2 09:34:22 sphinx snmpd[8966]: refused smux peer: oid SNMPv2-SMI::enterprises.11344.1.1.1, descr radiusd Dec 2 09:34:22 sphinx snmpd[8966]: trace: Dec 2 09:34:22 sphinx snmpd[8966]: smux_send_close(): mibgroup/smux/smux.c, 844: Dec 2 09:34:22 sphinx snmpd[8966]: smux: Dec 2 09:34:22 sphinx snmpd[8966]: [smux_close] sending close to fd 10, reason 5 Regards, E:S

1 0

Re: Packets in Accounting ?
by Alan DeKok 01 Dec '07

01 Dec '07

Edvin Seferovic wrote: > I found this in an older sql.conf file of mine : <shrug> It's always possible that there were local changes... > I suppose, the packets were in the schema, but I cannot confirm that for version < 1.0 since the FTP server of freeradius doesn't respond :( Hmm... OK. > Packets are also defined in the dictionary, why not have them in the accounting DB ? There are hundreds of accounting attributes in the dictionaries. Most NASes only send 5-6 attributes in an accounting packet. The default schema covers the common attributes. Alan DeKok.

1 0

Re: Packets in Accounting ?
by Alan DeKok 01 Dec '07

01 Dec '07

Edvin Seferovic wrote: > what happened to the Acct-Input/Output-Packets in Accounting. MySQL > schema doesn’t have those fields anymore. Any special reason ? Were they ever in the schema? I don't see them in 1.1.x. Alan DeKok.

2 1

Newbie: What does this mean (Wrong NAS port ID)?
by Piero Giobbi 01 Dec '07

01 Dec '07

Hi all. Im using freeradius 1.1.7 with Proxim AP4000 and it works. But i get this in my syslog. Error: rlm_radutmp: Logout entry for NAS ap-serverummet port 9 has wrong ID What does this mean? Can i ignore it? Can't really find anything useful on the net.. client-conf: client 10.0.5.191 { secret = xxx shortname = ap-serverummet nastype = other # localhost isn't usually a NAS... } thx. p

2 1

LDAP Authentication: filter problem
by Carlos Parada 01 Dec '07

01 Dec '07

Hi all, I'm using an LDAP-based authentication. I'd have a simple (typical filter) like this filter = uid=%{User-Name} Now, in addition, I'd need to authenticate based on a Service-Info attribute. So I need something like filter = "(&(uid=%{User-Name})(radiusServiceInfo=%{Service-Info})) The problem is that when Service-Info doesn't come in the Radius packet (because is not mandatory for me), it doesn't work, and I see on LDAP the following filter="(&(uid=test1)(?=undefined))" If Service-Info not present, I would expect something like filter="(&(uid=test1)(radiusSeviceInfo=))" Worse, in fact, what I need is a filter slightly different like filter = "(&(uid=%{User-Name})(!(radiusServiceInfo=%{Service-Info}))) In that case (using the !), the query sent is the following filter="(&(uid=test1)(?=error))" I've already search about that on the freeradius mailing-lists and I didn't saw any report about this problem. Is that any kind of bug? Or am I doing something wrong? I appreciate some help. Best Regards, Carlos Parada

2 1