20 Nov
2015
20 Nov
'15
5:50 p.m.
On Nov 20, 2015, at 5:42 PM, Bill Schoolfield <bill@billmax.com> wrote:
This is a followup on a resolution. Posted here so someone else won't have to go through this pain. After trying Juniper support (they were clueless)
As expected.
and dozens of other changes, I decided that perhaps the format of the Acct-Session-Id value was the issue. The one used included interface info as well as hex encoded session number.
The router has a command to change this format to a normal decimal number:
routername(config)#radius acct-session-id-format decimal
Once set, the disconnect requests work.
Uh... so their software doesn't like the Acct-Session-Id value it sends out? That's stupid. It's like they tried *hard* to break everything. Alan DeKok.