Hello, Freeradius-snapshot-20061203 crashes, when running just "radiusd" with proxy ("radiusd -X" doesn't crash): It logs the following "Error: Assertion failed in listen.c, line 621", which is "rad_assert(request->proxy_listener == listener);" Thanks.
Guilherme Franco wrote:
Hello,
Freeradius-snapshot-20061203 crashes, when running just "radiusd" with proxy ("radiusd -X" doesn't crash):
It logs the following "Error: Assertion failed in listen.c, line 621", which is "rad_assert(request->proxy_listener == listener);"
And what does the stack trace show? Are you HUPing the server? That can cause problems with that code, for a variety of reasons. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hi, I'm not HUPing the server in any way, never. GDB output: Starting program: /usr/local/sbin/radiusd [Thread debugging using libthread_db enabled] [New Thread 182896328384 (LWP 31483)] Detaching after fork from child process 31486. Program exited normally. (gdb) info threads No registers. (gdb) thread apply all bt full (gdb) Quit -------------------------------------- [foo@foo ~]# /usr/local/var/log/radius/radius.log: Wed Dec 6 20:33:08 2006 : Info: FreeRADIUS Version 2.0.0-pre0, for host x86_64-unknown-linux-gnu, built on Dec 3 2006 at 21:00:48 Wed Dec 6 20:33:08 2006 : Info: Starting - reading configuration files ... Wed Dec 6 20:33:08 2006 : Info: rlm_sql (sql): Driver rlm_sql_oracle (module rlm_sql_oracle) loaded and linked Wed Dec 6 20:33:08 2006 : Info: rlm_sql (sql): Attempting to connect to foo@10.10.10.2:/(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)( HOST=10.10.10.2)(PORT=1521))(CONNECT_DATA=(SID=DB_R))) Wed Dec 6 20:33:09 2006 : Info: rlm_sql (sql_postgresql): Driver rlm_sql_postgresql (module rlm_sql_postgresql) loaded and linked Wed Dec 6 20:33:09 2006 : Info: rlm_sql (sql_postgresql): Attempting to connect to foo@10.10.10.3:/DB_R Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621 Thank you.
Guilherme Franco wrote:
I'm not HUPing the server in any way, never.
Ok..
GDB output:
Starting program: /usr/local/sbin/radiusd [Thread debugging using libthread_db enabled] [New Thread 182896328384 (LWP 31483)] Detaching after fork from child process 31486.
Program exited normally.
<sigh> You've just printed out the GDB information from the server process that starts the daemon... which exits normally. Please send the gdb information from the core file. i.e. the program that is failing.
Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621
Immediately? Without ever receiving packets? That's very weird... Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hello, I did a "set follow-fork-mode child" in gdb now but then, there's no assertion failed! The "radiusd" child process keeps running now but no one can authenticate: [foo@foo tmp]# cat /usr/local/var/log/radius/radius.log Sat Dec 9 15:47:02 2006 : Info: FreeRADIUS Version 2.0.0-pre0, for host x86_64-unknown-linux-gnu, built on Dec 3 2006 at 21:00:48 Sat Dec 9 15:47:02 2006 : Info: Starting - reading configuration files ... Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql): Driver rlm_sql_oracle (module rlm_sql_oracle) loaded and linked Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql): Attempting to connect to foo@10.10.10.1:/(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.10.10.1)(PORT=1521))(CONNECT_DATA=(SID=DB_R))) Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql_postgresql): Driver rlm_sql_postgresql (module rlm_sql_postgresql) loaded and linked Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql_postgresql): Attempting to connect to foo@10.10.10.2:/DB_R Sat Dec 9 15:47:04 2006 : Info: Ready to process requests. Sat Dec 9 15:47:52 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:47:58 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:48:04 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:48:16 2006 : Error: TIMEOUT for request 0 in module <server core>, component <server core> Sat Dec 9 15:48:23 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:29 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:35 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:40 2006 : Error: TIMEOUT for request 1 in module <server core>, component <server core> Sat Dec 9 15:48:46 2006 : Error: TIMEOUT for request 2 in module <server core>, component <server core> Sat Dec 9 15:48:47 2006 : Error: TIMEOUT for request 3 in module <server core>, component <server core> Sat Dec 9 15:49:19 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 59 due to unfinished request 22 So: Running "radiusd" alone, without gdb, generates "Assertion failed in listen.c, line 621"; Running "radiusd" inside gdb generates no error, but does not works (as shown in the logs); Running "radiusd -X" alone or inside gdb works without any problems. What might it be? ps. Regarding the previous post, the "Assertion failed" occurs only when the first packet is received. Thanks you! On 12/6/06, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
I'm not HUPing the server in any way, never.
Ok..
GDB output:
Starting program: /usr/local/sbin/radiusd [Thread debugging using libthread_db enabled] [New Thread 182896328384 (LWP 31483)] Detaching after fork from child process 31486.
Program exited normally.
<sigh> You've just printed out the GDB information from the server process that starts the daemon... which exits normally.
Please send the gdb information from the core file. i.e. the program that is failing.
Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621
Immediately? Without ever receiving packets? That's very weird...
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hello, I did a "set follow-fork-mode child" in gdb now but then, there's no assertion failed! The "radiusd" child process keeps running now but no one can authenticate: [foo@foo tmp]# cat /usr/local/var/log/radius/radius.log Sat Dec 9 15:47:02 2006 : Info: FreeRADIUS Version 2.0.0-pre0, for host x86_64-unknown-linux-gnu, built on Dec 3 2006 at 21:00:48 Sat Dec 9 15:47:02 2006 : Info: Starting - reading configuration files ... Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql): Driver rlm_sql_oracle (module rlm_sql_oracle) loaded and linked Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql): Attempting to connect to foo@10.10.10.1:/(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.10.10.1 )(PORT=1521))(CONNECT_DATA=(SID=DB_R))) Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql_postgresql): Driver rlm_sql_postgresql (module rlm_sql_postgresql) loaded and linked Sat Dec 9 15:47:03 2006 : Info: rlm_sql (sql_postgresql): Attempting to connect to foo@10.10.10.2:/DB_R Sat Dec 9 15:47:04 2006 : Info: Ready to process requests. Sat Dec 9 15:47:52 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:47:58 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:48:04 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 57 due to unfinished request 0 Sat Dec 9 15:48:16 2006 : Error: TIMEOUT for request 0 in module <server core>, component <server core> Sat Dec 9 15:48:23 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:29 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:35 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 58 due to unfinished request 3 Sat Dec 9 15:48:40 2006 : Error: TIMEOUT for request 1 in module <server core>, component <server core> Sat Dec 9 15:48:46 2006 : Error: TIMEOUT for request 2 in module <server core>, component <server core> Sat Dec 9 15:48:47 2006 : Error: TIMEOUT for request 3 in module <server core>, component <server core> Sat Dec 9 15:49:19 2006 : Error: Discarding duplicate request from client NAS-1 port 50000 - ID: 59 due to unfinished request 22 So: Running "radiusd" alone, without gdb, generates "Assertion failed in listen.c, line 621"; Running "radiusd" inside gdb generates no error, but does not works (as shown in the logs); Running "radiusd -X" alone or inside gdb works without any problems. What might it be? ps. Regarding the previous post, the "Assertion failed" occurs only when the first packet is received. Thanks you! On 12/6/06, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
I'm not HUPing the server in any way, never.
Ok..
GDB output:
Starting program: /usr/local/sbin/radiusd [Thread debugging using libthread_db enabled] [New Thread 182896328384 (LWP 31483)] Detaching after fork from child process 31486.
Program exited normally.
<sigh> You've just printed out the GDB information from the server process that starts the daemon... which exits normally.
Please send the gdb information from the core file. i.e. the program that is failing.
Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621
Immediately? Without ever receiving packets? That's very weird...
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Guilherme Franco wrote:
Hello,
I did a "set follow-fork-mode child" in gdb now but then, there's no assertion failed!
And the server doesn't process any requests, either.
ps. Regarding the previous post, the "Assertion failed" occurs only when the first packet is received.
That's not what the debug log showed. The log you posted showed NOTHING being received, and the server dying. I find that very hard to believe. Please post a debug log showing that the server dies AFTER receiving a packet, and AFTER deciding that the packet has to be proxied. You posted:
Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621
i.e. NOT packet received, AND it dies. That's pretty much impossible. It looks to me like you're still running the old version of the server, without the fix for that problem. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Mr. Alan. Sorry for bothering you. If I run "radiusd" and setup the NAS to not send any requests to this radius server, radiusd stays up all day in "Info: Ready to process requests.". In the momment that I setup the NAS to send request to the radius server and the first request goes to it, radiusd dies. Maybe sometimes radiusd is not even taking a chance to log that someone tried to auth and just dies. But of all the logs that I have, just ONE shows the following: Wed Dec 7 09:15:04 2006 : Info: Ready to process requests. Wed Dec 7 09:15:04 2006 : Auth: Invalid user: [bonam@foo.com] (from client NAS-4 port 2952792216) Wed Dec 7 09:15:04 2006 : Error: Assertion failed in listen.c, line 621 All the other are just like: Wed Dec 6 11:02:46 2006 : Info: Ready to process requests. Wed Dec 6 11:02:46 2006 : Error: Assertion failed in listen.c, line 621 Besides that, I've installed the latest CVS above the old one, not a clean install. That might be the problem, what do you think? Thank you. On 12/11/06, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
Hello,
I did a "set follow-fork-mode child" in gdb now but then, there's no assertion failed!
And the server doesn't process any requests, either.
ps. Regarding the previous post, the "Assertion failed" occurs only when the first packet is received.
That's not what the debug log showed. The log you posted showed NOTHING being received, and the server dying. I find that very hard to believe.
Please post a debug log showing that the server dies AFTER receiving a packet, and AFTER deciding that the packet has to be proxied.
You posted:
Wed Dec 6 20:33:09 2006 : Info: Ready to process requests. Wed Dec 6 20:33:09 2006 : Error: Assertion failed in listen.c, line 621
i.e. NOT packet received, AND it dies. That's pretty much impossible.
It looks to me like you're still running the old version of the server, without the fix for that problem.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Guilherme Franco wrote:
But of all the logs that I have, just ONE shows the following:
Wed Dec 7 09:15:04 2006 : Info: Ready to process requests. Wed Dec 7 09:15:04 2006 : Auth: Invalid user: [bonam@foo.com <mailto:bonam@foo.com>] (from client NAS-4 port 2952792216) Wed Dec 7 09:15:04 2006 : Error: Assertion failed in listen.c, line 621
You CAN run it multi-threaded with the full debugging information. Use "-xxx", and you will see a LOT more information than what you've posted above.
Besides that, I've installed the latest CVS above the old one, not a clean install.
That might be the problem, what do you think?
Yes. Delete ALL of the server binaries and libraries. THEN install the new one. As I said, you're probably using the old version of the server, which is why you're running into a problem that was fixed months ago. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Ok, The log is below, thank you. Gonna delete and clean install it, I just thought that "./configure, make, make install" would overwrite everything except the confs. radiusd -xxx Mon Dec 11 19:47:58 2006 : Info: Ready to process requests. Mon Dec 11 19:47:58 2006 : Debug: Nothing to do. Sleeping until we see a request. Mon Dec 11 19:47:58 2006 : Debug: Thread 1 waiting to be assigned a request Mon Dec 11 19:47:58 2006 : Debug: Thread 2 waiting to be assigned a request Mon Dec 11 19:47:58 2006 : Debug: Thread 5 waiting to be assigned a request Mon Dec 11 19:47:58 2006 : Debug: Thread 3 waiting to be assigned a request Mon Dec 11 19:47:58 2006 : Debug: Thread 4 waiting to be assigned a request rad_recv: Access-Request packet from host 10.10.2.11 port 50000, id=206, length=234 Mon Dec 11 19:48:17 2006 : Debug: --- Walking the entire request list --- Mon Dec 11 19:48:17 2006 : Debug: Thread 1 got semaphore Mon Dec 11 19:48:17 2006 : Debug: Threads: total/active/spare threads = 5/0/5 Mon Dec 11 19:48:17 2006 : Debug: Thread 1 handling request 0, (1 handled so far) Mon Dec 11 19:48:17 2006 : Debug: Waking up in 1 seconds... User-Password = "bogus123" User-Name = "bogus@foo.com" Acct-Session-Id = "nas GigabitEthernet 11/0.165:2165:0028716608" Service-Type = Framed-User Framed-Protocol = PPP ERX-Pppoe-Description = "pppoe 00:0b:23:fd:1d:8c" Calling-Station-Id = "NAS-01#2165" NAS-Port-Type = Ethernet NAS-Port = 2952792181 NAS-Port-Id = "GigabitEthernet 11/0.165:2165" NAS-IP-Address = 10.10.2.11 NAS-Identifier = "NAS-01" Mon Dec 11 19:48:17 2006 : Debug: Processing the authorize section of radiusd.conf Mon Dec 11 19:48:17 2006 : Debug: modcall: entering group authorize for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling preprocess (rlm_preprocess) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from preprocess (rlm_preprocess) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "preprocess" returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling auth_log (rlm_detail) for request 0 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: '/usr/local/var/log/radius/radacct/10.10.2.11/auth-detail-20061211' Mon Dec 11 19:48:17 2006 : Debug: rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/10.10.2.11/auth-detail-20061211 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: 'Mon Dec 11 19:48:17 2006' Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from auth_log (rlm_detail) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "auth_log" returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling chap (rlm_chap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from chap (rlm_chap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "chap" returns noop for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling mschap (rlm_mschap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from mschap (rlm_mschap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "mschap" returns noop for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling unix (rlm_unix) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from unix (rlm_unix) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "unix" returns notfound for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling suffix (rlm_realm) for request 0 Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Looking up realm "foo.com" for User-Name = "bogus@foo.com" Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Found realm "foo.com" Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Adding Stripped-User-Name = "bogus" Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Proxying request from user bogus to realm foo.com Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Adding Realm = "foo.com" Mon Dec 11 19:48:17 2006 : Debug: rlm_realm: Preparing to proxy authentication request to realm "foo.com" Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from suffix (rlm_realm) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "suffix" returns updated for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling files (rlm_files) for request 0 Mon Dec 11 19:48:17 2006 : Debug: users: Matched entry DEFAULT at line 173 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from files (rlm_files) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "files" returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling sql (rlm_sql) for request 0 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: 'bogus@foo.com' Mon Dec 11 19:48:17 2006 : Debug: rlm_sql (sql): sql_set_user escaped user --> 'bogus@foo.com' Mon Dec 11 19:48:17 2006 : Debug: rlm_sql (sql): Reserving sql socket id: 14 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: 'SELECT id,UserName,Attribute,Value,op FROM radcheck WHERE Username = 'bogus@foo.com' ORDER BY id' Mon Dec 11 19:48:17 2006 : Debug: SELECT id,UserName,Attribute,Value,op FROM radcheck WHERE Username = 'bogus@foo.com' ORDER BY id Mon Dec 11 19:48:17 2006 : Debug: rlm_sql (sql): User found in radcheck table Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: 'SELECT id,UserName,Attribute,Value,op FROM radreply WHERE Username = 'bogus@foo.com' ORDER BY id' Mon Dec 11 19:48:17 2006 : Debug: SELECT id,UserName,Attribute,Value,op FROM radreply WHERE Username = 'bogus@foo.com' ORDER BY id Mon Dec 11 19:48:17 2006 : Debug: rlm_sql (sql): Released sql socket id: 14 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from sql (rlm_sql) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "sql" returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling expiration (rlm_expiration) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from expiration (rlm_expiration) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "expiration" returns noop for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling logintime (rlm_logintime) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from logintime (rlm_logintime) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "logintime" returns noop for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: calling pap (rlm_pap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[authorize]: returned from pap (rlm_pap) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[authorize]: module "pap" returns noop for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall: group authorize returns updated for request 0 Mon Dec 11 19:48:17 2006 : Debug: Processing the pre-proxy section of radiusd.conf Mon Dec 11 19:48:17 2006 : Debug: modcall: entering group pre-proxy for request 0 Mon Dec 11 19:48:17 2006 : Debug: modsingle[pre-proxy]: calling pre_proxy_log (rlm_detail) for request 0 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: '/usr/local/var/log/radius/radacct/10.10.2.11/pre-proxy-detail-20061211' Mon Dec 11 19:48:17 2006 : Debug: rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/10.10.2.11/pre-proxy-detail-20061211 Mon Dec 11 19:48:17 2006 : Debug: radius_xlat: 'Mon Dec 11 19:48:17 2006' Mon Dec 11 19:48:17 2006 : Debug: modsingle[pre-proxy]: returned from pre_proxy_log (rlm_detail) for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall[pre-proxy]: module "pre_proxy_log" returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: modcall: group pre-proxy returns ok for request 0 Mon Dec 11 19:48:17 2006 : Debug: proxy: allocating destination 30.30.2.1 port 1812 - Id 191 Sending Access-Request of id 191 to 30.30.2.1 port 1812 User-Password = "bogus123" User-Name = "bogus" Acct-Session-Id = "nas GigabitEthernet 11/0.165:2165:0028716608" Service-Type = Framed-User Framed-Protocol = PPP ERX-Pppoe-Description = "pppoe 00:0b:23:fd:1d:8c" Calling-Station-Id = "NAS-01#2165" NAS-Port-Type = Ethernet NAS-Port = 2952792181 NAS-Port-Id = "GigabitEthernet 11/0.165:2165" NAS-IP-Address = 10.10.2.11 NAS-Identifier = "NAS-01" Proxy-State = 0x323036 Mon Dec 11 19:48:17 2006 : Error: Assertion failed in listen.c, line 621
participants (2)
-
Alan DeKok -
Guilherme Franco