Len Conrad wrote: > the monit that is failing the radius test is running on the same machine as > FreeRadius.
If it's going to an external IP, it still has to be routed. > doesn't the concatenated IP:portsecret error give some hint? > > "failed protocol test [RADIUS] at INET[xx.4.62.16:1812testing123] via UDP" That's just how the error message is generated. It prints the IP, port, and other text, all jammed together. See src/util.c, Util_portDescription(). If the kernel is generating a "no route to host" error, then there is no route to the IP address. No amount of poking an application configuration will fix an OS layer networking issue. Alan DeKok. -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
