noted. tks
On Tue, Aug 20, 2013 at 9:43 PM, Alan DeKok al...@deployingradius.comwrote:
ultaman khoo wrote:
Thanks alan, i alreaady on it right now, anything from the RFC that you
aware of can challenge the back the changes of NAS ip is wrong? Thanks
All of the RADIUS RFCs assume that
Thanks alan, i alreaady on it right now, anything from the RFC that you
aware of can challenge the back the changes of NAS ip is wrong? Thanks
On Fri, Aug 16, 2013 at 10:41 AM, Alan DeKok al...@deployingradius.comwrote:
ultaman khoo wrote:
btw the nas ip changes is due to NAS system
ultaman khoo wrote:
Thanks alan, i alreaady on it right now, anything from the RFC that you
aware of can challenge the back the changes of NAS ip is wrong? Thanks
All of the RADIUS RFCs assume that a client has one IP, and only one IP.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
ultaman khoo wrote:
I have faced an issue with NAS IP Changes
RADIUS assumes that NAS IPs don't change. If they do, you are running
a VERY unusual system.
causes radius accouting insert
instead of update, this has causes an issue with the reporting wenever
the NAS IP changes, for example
ultaman khoo wrote:
I have faced an issue with NAS IP Changes
RADIUS assumes that NAS IPs don't change. If they do, you are running
a VERY unusual system.
Do you mean it doesnt conform to the radius acct RFC standard in this case?
if im get it right the FR3.0 should have take care of the NAS
btw the nas ip changes is due to NAS system supplying the radius acct
has failover to the backup unit, radius acct is then supply from there. so
it get change
On Fri, Aug 16, 2013 at 7:39 AM, ultaman khoo ultaman.k...@gmail.comwrote:
ultaman khoo wrote:
I have faced an issue with NAS IP
ultaman khoo wrote:
btw the nas ip changes is due to NAS system supplying the radius acct
has failover to the backup unit, radius acct is then supply from there.
so it get change
It's still garbage.
The FreeRADIUS SQL queries assume that one NAS sends all of the
accounting traffic for
7 matches
Mail list logo