On Aug 14, 2015, at 5:01 , Alan DeKok <aland@deployingradius.com> wrote:
There may be a regression in 2.2.8. I've put some fixes in which should help. Please try the v2.x.x branch from github.
Yes. That seems to have done it. I now get status-server requests after a few answered requests. See radsniff output below. # radsniff Access-Request Id 72 172.20.20.14:63985 -> 172.20.20.245:1812 +0.000 User-Name = "aabbccddeeff" User-Password = "\365#3\343x\333]\306#\337n\203\361\206\027\235" NAS-IP-Address = 192.168.239.141 NAS-Port = 11 Message-Authenticator = 0x54d0b48a7fe13ec820f86a6569889002 Access-Request Id 122 172.20.20.246:1814 -> 172.20.20.184:1812 +0.000 User-Name = "aabbccddeeff" User-Password = "\312\020\n,\023\3324\263\330\031\235 \253j\265'" NAS-IP-Address = 192.168.239.141 NAS-Port = 11 Message-Authenticator = 0xa91110b861554dd78132297f0c6a19e3 Proxy-State = 0x3732 Access-Request Id 72 172.20.20.14:63985 -> 172.20.20.245:1812 +4.347 User-Name = "aabbccddeeff" User-Password = "\365#3\343x\333]\306#\337n\203\361\206\027\235" NAS-IP-Address = 192.168.239.141 NAS-Port = 11 Message-Authenticator = 0x54d0b48a7fe13ec820f86a6569889002 Access-Request Id 122 172.20.20.246:1814 -> 172.20.20.184:1812 +4.348 User-Name = "aabbccddeeff" User-Password = "\312\020\n,\023\3324\263\330\031\235 \253j\265'" NAS-IP-Address = 192.168.239.141 NAS-Port = 11 Message-Authenticator = 0xa91110b861554dd78132297f0c6a19e3 Proxy-State = 0x3732 Status-Server Id 143 172.20.20.246:1814 -> 172.20.20.184:1812 +6.002 Message-Authenticator = 0x8561c3bc9e1baaa1dc4b3d7660c5bc80 NAS-Identifier = "Status Check. Are you alive?” Thank you for your help. -- Louis Munro lmunro@inverse.ca :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)