Hi,
A bit of background info first.
I know this is a freeradius list, let me mention the cistron stuff first
as it's related.
We rent some dial up ports off a nation wide provider.
They run a RADIUS proxy server, I dont know which version.
We run Cistron radius 1.6.1 on debian potato for our own NAS's.
They insisted we needed 1.6.4 to support long attribute data.
So we installed debian woody (testing) on a box and installed the 1.6.4
Cistron radius.

The problem; we would see the request come in and authenticate user and
send the reply. nothing happens, we know the reply leaves as we set up
logging of ipchains to watch.

We called in the experts, agents of the nation wide provider. They
couldn't work it out and temprarily installed Radiator. It worked. The
outgoing packet info looked exactly the same as our cistron packets.

So we installed freeradius 0.3 as per instructions and tested it and it
worked. Experts went home.

Here's the kicker. I built the debain package of freeradius, installed it
and setup the configs exactly as we had done before and it did the same
thing as the Cistron version did!

The request comes in, authenticates user and the reply data goes out, but
that's all.

We think it must have something to do with the libraries/programs that the
debian build uses for both cistron and freeradius.

I'm no expert in source code or compiling so I can't go any further. I
want to use the debian package so it's easy to upgrade and all the files
are where we traditionally expect to see them.

If anyone can help I'd be grateful. If you want me to do soemthing to
capture data or something, just tell me what to do and I'll be glad to
help.

thanks
Mervyn



Mervyn Jack, Technical Services, Country Netlink, Cobram, Vic, Australia.
Providing Internet access to the Goulburn Valley and North East.
Phone  03 5871 1000  |  Fax 03 5871 1874  |  Mobile 0409 960 520
Work: http://www.cnl.com.au  |  Pers: http://www.cnl.com.au/users/mervynj



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to