> Ok, heres the the problem.. but I dunno the cause:
>
> Apparently the portmaster is assigning damn 0.0.0.0 for some reason
> I have no idea why.. What could cause this? And it seems rather
> random.. a bug perhaps? it's running v3.1.3c2
Ugh. As frustrating as this may be, it seems that the only solution to
this is to reboot the Portmaster. We have had this problem on a couple
occasions a couple months ago, on the same Portmaster. I am confident that
it's not a radius misconfiguration or a Portmaster misconfiguration, since
it is only one of 12 or so PM's using the same radiusd server, and a
(soft, command-line) reboot always fixed it.
Chris Woods Senior System Administrator USAinternet, Inc.
GCS/CM/IT d- s++:+ a- C++++$ ULS++++$ P+++$>++++ L++++$ E W$ N+ !o
K++ !w--- !O !M-- !V-- PS+? !PE !Y+>++ PGP+ t+@ !5 X !R tv? b+ DI++
D+@ G++ e h---- r+++ y++++
cjwoods@usa1.net http://www.usa1.com 508-774-4700