Hi Heikki,
some hours of debugging and testing later:
Radiator 4.19 is now running together with the german NREN upstream
radsecproxy, but I don't know what went wrong yesterday, sic!
Yesterday I see the following lines in the debug file:
Mon Aug 7 16:14:02 2017 030094: DEBUG:
On 8.8.2017 12.36, Karl Gaissmaier wrote:
nothing has changed at the upstream since I upgraded yesterday, here you
see it after I switched back to 4.17:
Tue Aug 8 09:07:43 2017 099341: DEBUG: Packet dump:
*** Received from 193.174.XX.YY port 3
Code: Status-Server
Identifier: 0
Hi Heikki,
Am 08.08.2017 um 11:15 schrieb Heikki Vatiainen:
On 8.8.2017 11.46, Karl Gaissmaier wrote:
just as info before I'll do more debugging.
StatusServer seems to be broken in 4.19 and latest patches applies at
least here at Ulm University.
Quick check: does the upstream add
On 8.8.2017 11.46, Karl Gaissmaier wrote:
just as info before I'll do more debugging.
StatusServer seems to be broken in 4.19 and latest patches applies at
least here at Ulm University.
Quick check: does the upstream add Message-Authenticator attribute in
Status-Server requests and do they