Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 126.96.36.199.1
Oracle Communications Billing and Revenue Management - Version: 188.8.131.52.0 to 184.108.40.206.0 [Release: 6.5.0 to 7.2.1]
HP-UX PA-RISC (64-bit)
HP-UX PA-RISC (32-bit)
Oracle Solaris on SPARC (64-bit)
Communications Apps (Portal) - Version: Communications Apps (Portal) - Version: 220.127.116.11.0 to 18.104.22.168.0
Checked for relevance on 6th May 2010
A user is using RADIUS Manager from Infranet to receive and log RADIUS messages. On the production server he has configured several IP addresses:
Primary + Secondary (using aliasing)
For RADIUS messages received on a Secondary IP address Infranet RADIUS Server sends ACK messages using the Primary server address. This leads to many retry messages from the RADIUS client and thus to duplicate unnecessary messages.
In details, for the user, Infranet + RADIUS is set up on one machine with
Requests are sent from another machine (xxx.xx.xx.300), using rad_tester.
For the first request
rad_tester -h xxx.xx.xx.100 -p 1812 -a 1813...
the Primary IP is specified as server address and the user receives an NAK answer.
For the second request
rad_tester -h xxx.xx.xx.200 -p 1812 -a 1813...
the secondary IP is specified as server address and the user does not receive any answer from it.
How can one specify in the Infranet RADIUS configuration the IP address that should be included in ACK messages?
Is there a parameter for the RADIUS Server that specifies the bind address (all open sockets will be on a specific, configurable network interface. All request will be accepted only with this address as destination IP and all responses would be sent from this address)?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms