Hi Alan, Many thanks... It really helped me narrowing down the scope of the problem. Very likely it's because of a buggy kernel being used by the home RADIUS server. I've tested with a different kernel version and didn't receive any malformed packets. with the buggy OS, roughly 20% of malformed incidents are guaranteed. srg. On Thu, May 29, 2008 at 12:59 PM, Alan DeKok <aland@deployingradius.com> wrote:
rsg wrote:
I agree it's not a RADIUS server. It's a WAP gateway running on Kannel with minimal support for RADIUS as described by http://www.kannel.org/download/1.4.1/userguide-1.4.1/userguide.html#AEN1038
Nit-picking games aren't necessary. If it's supposed to receive Accounting-Request packets and send Accounting-Response packets, it's supposed to be a RADIUS server.
In any case, it's not a STANDARDS COMPLIANT RADIUS server, if that sounds better.
I understand your point. However, there's no better alternative for the moment.
Then fix their code. It's broken.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html