(RADIATOR) Strange problem when upgrading
hugh at open.com.au
Wed Jul 17 17:33:29 CDT 2002
Salut Jeje -
Comment va la vie?
The first question is "have you also applied all the patches for 3.1?".
The second question is the usual "can you please send me a copy of
the configuration file (no secrets) together with a trace 4 debug
showing what is happening?".
BTW - in what you show below, why don't you use an AuthBy INTERNAL?
At 18:25 +0200 17/7/02, Jerome Fleury wrote:
>When upgrading from 2.19 to. 3.1, I had a strange problem that made
>me cancel the upgrade.
>this code (some hidden for security purpose):
> <AuthBy FILE>
> # accepte toutes les requetes venant du proxy
> Filename /dev/null
> AddToReply \
> Tunnel-Type=L2TP, \
> Tunnel-Medium-Type=IP, \
> Tunnel-Server-Endpoint=188.8.131.52, \
> Tunnel-Assignment-ID=184.108.40.206, \
> Tunnel-Server-Auth-ID=LNSTISFT01, \
> RB-Tunnel-Remote-Name=LNSTISFT01, \
> Class = "L2FT"
>used to work in 2.19.
>when upgrading to 3.1, AddToReply did not work any more and no
>attributes were sent back during Access-Accept. I saw in Changelog
>that a lot of code has been rewritten about Reply attributes.
>Why doesn't this work anymore ? Is there a workaround ?
>Archive at http://www.open.com.au/archives/radiator/
>Announcements on radiator-announce at open.com.au
>To unsubscribe, email 'majordomo at open.com.au' with
>'unsubscribe radiator' in the body of the message.
NB: I am travelling this week, so there may be delays in our correspondence.
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator