Multiple Radius sending Accounting Request

Multiple Radius sending Accounting Request SearchSearch

SMS & MMS Technical Forum » Now.WAP Proxy (Product Support Only) » Multiple Radius sending Accounting Request « Previous || Next »
Author Message
Felix Sanchez
New member
Username: Filixdikat

Post Number: 5
Registered: 12-2009
Posted on Tuesday, March 20, 2012 - 08:52 pm:   

Hello.

We have NowWap ver v2010.02.01, so far its being working fine. However we are planing to change the radius server, and that involve some tests before any migration.
We are using radiator 4.3 as radius server managing 2 apns without any issues, however i'm testing the second radius server handling another apn.
The msisdn is able to connect to the 3 apn, im able to browse using all the apn, the radius log file shows the Accounting-Connect/Accounting-Disconnect of both radius server. The difference its that inside the waplog theres no info about the user ip address of the second radius server, and its not forwarding MSISDN and IP address of that particular APN (second) radius.

I wonder if it could be any restriction in your application that isnt forwarding the information properly.

if you need more info, i will give it privately.

regards,
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3849
Registered: 08-2008
Posted on Wednesday, March 21, 2012 - 07:21 pm:   

Hi Felix,

As long as the "shared secret" is the same, packets from multiple RADIUS servers is fine.

If the RADIUS-yyyymmdd.LOG doesn't include MSISDN (PhoneNumber=) and/or client IP address (AssignedIP=) information, then this suggests that those attributes are not present in the RADIUS accounting packet.

I'd suggest downloading a copy of Wireshark to intercept/decode the RADIUS packets to confirm this.

--
Des
NowSMS Support
Felix Sanchez
New member
Username: Filixdikat

Post Number: 6
Registered: 12-2009
Posted on Wednesday, March 21, 2012 - 07:40 pm:   

Hi Des,

This is basicly what it show in the RADIUS log file. The NASIP with problems is the 172.27.109.22, so far the info sent by both radius is accepted by the NowWAP, however i dont if is reject its still shown in the log file

Accounting-Connect,20/Mar/2012:14:53:53 -0500,NASIP=172.27.99.202,NASPort=54740928,PhoneNumber=XXXXXXX7295,UserName=XXXX XXX7295,SourceIP=172.27.109.22,AssignedIP=10.6.0.131,3GPP-SGSN-ADDRESS=XXX.XX.16 7.193,3GPP-IMSI=XXXXXXX02725060
Accounting-Disconnect,20/Mar/2012:15:42:39 -0500,NASIP=172.27.99.202,NASPort=54740928,PhoneNumber=XXXXXXX7295,UserName=XXXX XXX7295,SourceIP=172.27.109.22,AssignedIP=10.6.0.131,3GPP-SGSN-ADDRESS=XXX.XX.16 7.193,3GPP-IMSI=XXXXXXX02725060
Accounting-Connect,20/Mar/2012:15:42:48 -0500,NASIP=172.27.98.58,NASPort=67642568,PhoneNumber=XXXXXXX7295,UserName=XXXXX XX7295,SourceIP=172.27.99.132,AssignedIP=10.1.168.167,3GPP-SGSN-ADDRESS=XXX.XX.1 67.193,3GPP-IMSI=XXXXXXX02725060
Accounting-Disconnect,20/Mar/2012:15:43:30 -0500,NASIP=172.27.98.58,NASPort=67642568,PhoneNumber=XXXXXXX7295,UserName=XXXXX XX7295,SourceIP=172.27.99.132,AssignedIP=10.1.168.167,3GPP-SGSN-ADDRESS=XXX.XX.1 67.193,3GPP-IMSI=XXXXXXX02725060
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3850
Registered: 08-2008
Posted on Wednesday, March 21, 2012 - 08:59 pm:   

Hi Felix,

I did some checking, and if a RADIUS packet is received but not accepted, or not understood, there should be an entry in that RADIUS-yyyymmdd.LOG. It would indicate something liken invalid transaction type, or an invalid shared secret. At least that is what should happen, it is possible that we might have missed an error condition and forgot to log it, but that is unlikely.

I'd suggest WireShark in this regard, as you can use it to intercept packets and see if anything is there.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3851
Registered: 08-2008
Posted on Wednesday, March 21, 2012 - 09:07 pm:   

here is what the log should show for a packet that is not processed for some reason:


Accounting,21/Mar/2012:18:00:43 -0400,SourceIP=127.0.0.1
Felix Sanchez
New member
Username: Filixdikat

Post Number: 7
Registered: 12-2009
Posted on Wednesday, March 21, 2012 - 09:26 pm:   

Which is not my case (i guess), i did some captures and everything looks the same. I not sure if restarting the NowWAP may fix the problem. The only difference wasnt sending the Username in the radius packet but i fixed.
How can i send you the pcap files in order to see the difference.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3856
Registered: 08-2008
Posted on Wednesday, March 21, 2012 - 10:43 pm:   

Felix,

You can send them to nowsms@nowsms.com with Attention: Des in the subject line.

However ... that said ... was there a typo in the 3rd post in this thread?

You said "The NASIP with problems is the 172.27.109.22" ... did you mean 172.27.109.202?

If that is the case, then the RADIUS log seems to indicate that the packet had all the required attributes and was accepted.

As a next step, check WAPGW-yyyymmdd.LOG to see if the subsequent requests were received from an IP address matching "AssignedIP=" from the RADIUS log. In the case above, that would be 10.6.0.131. It might be that there is a NAT between that subnet and NowWAP, so the source IP gets changed.

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics