[RADIATOR] Radiator and radsecproxy, status-server and failover algo, one step forward

[Stefan Winter]

Hi,

> status-server musnt be proxied....its only for the first-hop check of
> a remote proxy and not the end target - but that surely isnt the issue?
> a Status-Server message is easy to deal with - you just send something back
> to show you are alive - RADIATOR has been sending a basic statts page back
> for status-server queries to it for years.

This is about Status-Server requests *originating* from Radiator to
check another server's alive state. Radiator sends a Proxy-State in the
request (which is not supposed to be done), and then complains that it
doesn't get it back (which is only supposed to happen with
Access-Requests, not Status-Server).

Greetings,

Stefan Winter

-- 
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
Url : http://www.open.com.au/pipermail/radiator/attachments/20130715/32f0e8dc/attachment.bin