proxy accounting in cvs
appears to not set the src_ipaddr, even though server is bound to single ip on multiple IP'd host machine. Therefore all accounting servers marked dead. Proxy auth appears to work. Joe
Joe Maimon wrote:
appears to not set the src_ipaddr, even though server is bound to single ip on multiple IP'd host machine.
Therefore all accounting servers marked dead.
Proxy auth appears to work.
Joe - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
And this little hack into proxy.c:487 fixes accounting.... /* Hack in src_ipaddr */ if(!request->proxy->src_ipaddr.af) memcpy(&request->proxy->src_ipaddr, &request->packet->dst_ipaddr, sizeof(request->proxy->src_ipaddr)); which truly stinks and something better should be done, such as take the first address bound to, accept a src_ip/interface argument in proxy.conf.......
Joe Maimon <jmaimon@ttec.com> wrote:
And this little hack into proxy.c:487 fixes accounting....
OK, thanks. Your other issues from yesterday should be fixed in today's CVS.
which truly stinks and something better should be done, such as take the first address bound to, accept a src_ip/interface argument in proxy.conf.......
Or in a "listen" section, which is the preferred method. That may not be hard to add, and I'll see what I can do. Alan DeKok.
Alan DeKok wrote:
Joe Maimon <jmaimon@ttec.com> wrote:
And this little hack into proxy.c:487 fixes accounting....
OK, thanks. Your other issues from yesterday should be fixed in today's CVS.
Ive seen it, not tried it yet. Thanks.
which truly stinks and something better should be done, such as take the first address bound to, accept a src_ip/interface argument in proxy.conf.......
Or in a "listen" section, which is the preferred method.
That may not be hard to add, and I'll see what I can do.
Alan DeKok.
How does the concept of choosing which address to source packets proxied fit in with the concept of choosing which address/port to accept request? Unlike in the hack I exampled there is no real reason to tie them together. Also conceivably an admin might appreciate being able to specify different src addr/ports for different realms.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
How does the concept of choosing which address to source packets proxied fit in with the concept of choosing which address/port to accept request?
OK, so it's not a "listen" directive, but it's pretty similar.
Also conceivably an admin might appreciate being able to specify different src addr/ports for different realms.
Yes. That's the long-term goal, and one of the reasons 2.0 is delayed. Once we fix that, 2.0 should be pretty much ready to go. Alan DeKok.
participants (2)
-
Alan DeKok -
Joe Maimon