unknown proxy ?
Hello, Collegues! I'm using freeradius-0.7.1. I'm trying to configure this freeradius as proxy server to remote. -- rad_recv: Access-Reject packet from host 195.123.5.10:1288, id=1, length=48 Ignoring request from unknown proxy 195.123.5.10:1288 -- Host 195.123.5.10 was configured in proxy.conf In naslist too. Tell me, please, what I forgot to do? ;) -- Alex Radetsky AR2657-RIPE RAD-UANIC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: unknown proxy ?
On Wed, Dec 10, 2003 at 03:11:42PM +0100, Thomas MARCHESSEAU wrote:
Hi Alex,
did u check clients.conf ?
[EMAIL PROTECTED] bin]# grep 195.123.5.10 /usr/local/radius-proxy/etc/raddb/*
clients: 195.123.5.10 123
clients.conf: client 195.123.5.10 {
proxy.conf: authhost= 195.123.5.10:1812
proxy.conf: accthost= 195.123.5.10:1645
Yes, I do.
Ok, I'll search this message in sources and will find what I got to do.
Thanks! ;)
Thomas .
Alex Radetsky wrote:
Hello, Collegues!
I'm using freeradius-0.7.1. I'm trying to configure this freeradius
as proxy server to remote.
--
rad_recv: Access-Reject packet from host 195.123.5.10:1288, id=1, length=48
Ignoring request from unknown proxy 195.123.5.10:1288
--
Host 195.123.5.10 was configured in proxy.conf
In naslist too.
Tell me, please, what I forgot to do? ;)
--
Alex Radetsky
AR2657-RIPE
RAD-UANIC
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: unknown proxy ?
On Wed, Dec 10, 2003 at 04:18:30PM +0200, Alexey Balabushevich wrote: I'm using freeradius-0.7.1. I'm trying to configure this freeradius as proxy server to remote. -- rad_recv: Access-Reject packet from host 195.123.5.10:1288, id=1, length=48 Ignoring request from unknown proxy 195.123.5.10:1288 -- Host 195.123.5.10 was configured in proxy.conf In naslist too. Tell me, please, what I forgot to do? ;) what about clients ? clients conf configured. Please see latest message. -- Alexey Balabushevich nic-hdl: AB433-RIPE Wow. Very glad to see you. :) -- Alex Radetsky AR2657-RIPE RAD-UANIC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
unknown proxy ? part 2
Hello!
I found this in files.c :
--
REALM *cl;
/*
* Note that we do NOT check for inactive realms!
*
* If we get a packet from an end server, then we mark it
* as active, and return the realm.
*/
for(cl = realms; cl != NULL; cl = cl-next)
if ((ipaddr == cl-ipaddr) (port == cl-auth_port)) {
cl-active = TRUE;
return cl;
} else if ((ipaddr == cl-acct_ipaddr) (port == cl-acct_port)) {
cl-acct_active = TRUE;
return cl;
}
return NULL;
--
So, if radius got packet from remote server with configured source_ip and
port, radiusd marks it as active.
But in my case, radius got packet from configured source_ip, but another
port.
What does it mean? Does some one proxy exist between my and remote radius?
Is it correct?
PS. I can rewrite this code to create workaround. But I do not know, may
be it will not correct.
--
Alex Radetsky
AR2657-RIPE
RAD-UANIC
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Problem with running.
On Fri, Oct 10, 2003 at 11:17:16AM -0400, Alan DeKok wrote: Alex Radetsky [EMAIL PROTECTED] wrote: Please tell me, what changes are made in modules interfaces from 0.7.1 to 0.9.1. I don't think there were any changes to the module interface. What a problem may be with my module? I would suggest using 'gdb' to track down any errors. Great thanks, Alan. I found error in my module with memory operations. Thanks! -- Alex Radetsky AR2657-RIPE RAD-UANIC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Problem with running.
Dear Collegues! Now, I write first message to this list. I can be wrong. ;) I'm using freeradius from 0.4.x version. When I was study radius protocol and freeradius config files I found that one of many solutions for my dialup system will be development of my own module. My module was develped by me and works fine from first my version of freeradius to 0.7.1 where it lives now. But, when I try to compile with 0.9.1 on latest gentoo-linux I found some errors in my modules. I fix it. When I run 'radiusd -X' radius got signal 11 (segmentation fault). Look: (my module is rlm_xisp AKA xisp) Please tell me, what changes are made in modules interfaces from 0.7.1 to 0.9.1. What a problem may be with my module? Thank you. radius -X run log Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /usr/local/radius/etc/raddb/proxy.conf Config: including file: /usr/local/radius/etc/raddb/clients.conf Config: including file: /usr/local/radius/etc/raddb/snmp.conf main: prefix = /usr/local/radius main: localstatedir = /usr/local/radius/var main: logdir = /usr/local/radius/var/log/radius main: libdir = /usr/local/radius/lib main: radacctdir = /usr/local/radius/var/log/radius/radacct main: hostname_lookups = no main: max_request_time = 60 main: cleanup_delay = 10 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = yes main: log_file = /usr/local/radius/var/log/radius/radius.log main: log_auth = yes main: log_auth_badpass = no main: log_auth_goodpass = no main: pidfile = /usr/local/radius/var/run/radiusd.pid main: user = root main: group = root main: usercollide = no main: lower_user = no main: lower_pass = no main: nospace_user = no main: nospace_pass = no main: checkrad = /usr/local/radius/sbin/checkrad main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = no proxy: dead_time = 120 proxy: post_proxy_authorize = yes proxy: wake_all_if_all_dead = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist Using deprecated naslist file. Support for this will go away soon. read_config_files: reading clients Using deprecated clients file. Support for this will go away soon. read_config_files: reading realms Using deprecated realms file. Support for this will go away soon. radiusd: entering modules setup Module: Library search path is /usr/local/radius/lib Module: Loaded xisp Segmentation fault radius -X run log end -- Alex Radetsky AR2657-RIPE RAD-UANIC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Acct-Termination-Cause Question
Hello! Now I am writing freeradius module for our billing system. I do it because I wanna get all ability to manage all operations with users and NASes. :) Our database is highly tailored. My module works with freeradius versions from 0.3 to 0.5. So, my question about Ascend MAX 4060 Acct-Termination-Cause radius attribute. I have a MAX4060 for test new version of billing system. When radius receive an accounting stop I look for Acct-Termination-Cause || Ascend-Disconnect-Cause attr. And I got Ascend-Disconnect-Cause pair with string value. But in the Ascend MAX Radius Configuration Guide I see that radius can give me string with integer value. ;) For example: Ascend-Disconnect-Cause = PPP-Rcv-Terminate-Req I want to get: Ascend-Disconnect-Cause = 45 Can you tell me how can I get it? Thank you very much. PS. Sorry for may bad English. ;) -- Alex Radetsky AR2657-RIPE RAD-UANIC - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
