hello
> Yes it is defined in my /etc/services file with the following entries > > radius 1812/tcp > radius 1812/udp > radius-acct 1813/tcp > radius-acct 1813/udp I doubt it is. The question is, if the LOCAL /etc/services is applied to REMOTE servers. It sounds logical if the port is omitted but *I don't know*. So in my case I just use the ports of the remote server explicitely. Why not try it? > Yes, I am using -s -x this time. you can see even more if you add more "x". e.g. it would be interesting to know, why A thinks that this request is for him whilst it is for B. > I then see on radius server on redhat's screen showing request get processed > with user-name = "popo@jenhwa" and not forward to Radius server jenhwa at > all. In my case I see how the proxying server *gets* the requests, then how it resends it and finally how it arrives at the responsible server and is answered back. The proxying server confirms this arrival and resends the message to the client, etc. I suppose nothing of this kind happens to you :-) > No, I haven't change anything, my current configuration is exactly the same > as you suggested. Now, I am assuming I should see radius server B(jenhwa) > get the User-Name = "popo@jenhwa" and processed it but not in this case, > instead it is Radius Server A get it processed. In addition here is my you should control your configuration for any DEFAULT and NULL realms and for further options within the realm definition. Otherwise I can't help you: I do have the same type of configuration and it works perfectly. It has never even tried to not to work :-) It just worked immediately. If you are really in worry, you can send me a tar.gz copy of your $INSTALLDIR/etc/raddb directory. I will try to find the problem. It seems to me that you understand the principal. (If you decide to send me these files, please edit them before removing any sensitive information) > "raddb/users" setting at both Radius Server A(redhat) and Radius Server > B(jenhwa) I am not sure this will trigger any problem. > > DEFAULT Auth-Type := ACCEPT > Fall-Through = yes, > Exec-Program = "/usr/local/sbin/myprogram %u %n %f %i" > > where myprogram just simply a shell program dump out the User-Name, > NAS-IP-Address, Framed-IP-Address and Calling-Station-ID into a file. > It looks like > > #! /bin/sh > echo `/bin/date` " User-Name = " $1 NAS IP = " $2 "Framed-IP = " $3 > "Calling-Station-ID = " $4 >> /tmp/myprogramlog I have no idea if it has something to do with your proxy problem - why don't you test with some local dumb user like "steve" who is present in the example configuration? - but at least in my shell your program doesn't work: something is wrong... Sorry, artur -- ------------------------------------------------------------------ o [EMAIL PROTECTED] | o IRCNET:MadArt@#karlsruhe o [EMAIL PROTECTED] | o http://www.madart.de ------------------------------------------------------------------- - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
