We are running an old, unsupported Vircom Radius server, which is doing it's job wonderfully. We have just switched from Lucent PM3's to AS5300, and functionally everything is ok, but there's one annoying cosmetic problem:
After authenticating and authorizing the caller, radius server itself thinks the callers IP address is 0.0.0.0, regardless if the IP came from the AS5300 pool or was an static address assigned by the radius server. I have a web page that lists users online and their IP addresses, and I've noticed that right after authentication/authorization the radius server displays the IP address correctly, for a second or two, and also during logout, the address in the list is the correct one. And finally, with multilink ISDN users, the first call shows 0.0.0.0, but the second one shows the correct IP address.
And like I wrote, it's just an cosmetic problem in the radius server, the user gets a correct IP and AS5300 sets up all the routes etc. With PM3, radius server listed the record of user IP's correctly.
Any ideas? Missing radius attributes or something?
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...