On 20 Mar 2017, at 19:49, [email protected] wrote:
Hi,
After the above, I tried with Net::DNS 1.08 and Radiator failed to
get a response for its SRV query. After testing a couple of more
versions, a quick test shows that 1.02 is the last version that
works.
1.03 causes a crash and 1.04 and later fail similarly. Net::DNS
changelog shows that there have been quite a few changes in the
recent versions that explain the crash and quite likely are the cause
of missed response.
well....thats.....rubbish..really - wheres their testing/regression
tests? we are tirelessly told to be running
up to date versions of code to avoid bugs/security issues...and then
this sort of thing happens...where you have a failed
service if you *do* that :/
I remember to have posted (maybe just privately) patches to catch
Net::DNS problems in the past to avoid radiusd to keel over and
gracefully handle them. I lost track if they ever made it in.
I also used to have patches to get multi-NAPTR pointer support (try them
in sequence until success and only then fall back to Route), as well as
multiple Route entries back then in order to try different orders for
fallbacks on different servers, etc. (as you’d kind of know from
other config parts).
In case any of this stuff would be interesting or help, I could go and
see if I can find them again.
/bz
_______________________________________________
radiator mailing list
[email protected]
http://lists.open.com.au/mailman/listinfo/radiator
