* This is the VOP Radius mailing list *
Guys, Have you tried this command on the Cisco router. aaa accounting delay-start just add this line to your Cisco router configuration . this will Delay generation of the start accounting record until the user IP address is established. so the IPAddress will be included on the Accounting Start Packet. Pls try and let me know. Best regards, Shadi Haddadin ________________________________ Internet Systems Manager Mob : +962-77-390098 Tel : +962-6-4736800 http://www.next.jo NEXT Co. LTD. _______________________________ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Craig Norborg Sent: 28 August 2002 05:28 PM To: [EMAIL PROTECTED] Subject: [VOP RADIUS] Problems getting IP Address from DSL Customers in Platypus * This is the VOP Radius mailing list * I tried getting the nice people at Vircom to answer this, but they wanted me to purchase a $1200 support contract (on upgrades only right now) and I didn't really think it was worth that much, I'd rather bang my head on it some more before I went that route... But, I thought I might see if anyone else was running up against this at all... We're having problems getting our VOPRadius (latest revision) to log the IP addresses of our DSL customers coming in through our Cisco router and put it into our Platypus CallsOnline database. It seems that the initial accounting packet is not including the IP address assigned from the pool on the Cisco. Right now I've "kinda" solved it by using watchdog packets. On the Cisco I set them up using: aaa accounting update periodic X (where X is the timer in minutes) But, you can also put in aaa accounting update newinfo periodic X which tells it not only to send the update packets every X minutes, but to send any updates immediately when they happen (which in this case it sends a packet almost immediately after the initial packet when the IP address is initially assigned - you can also do just the update packets, but that runs into other problems from what I can see). However, after a user is "updated" in any way, their "AcctStatusType" in the CallsOnline database gets set to "-1", which with the way that field was originally set up in that table wouldn't work (the field was a tiny int which can't be -1)... Does anyone know why it is setting this field to "-1"? Is there any way I can keep it from doing this, or any reason I shouldn't let it become "-1"? Another question would be, is there any way to get VOPRadius to accept the "newinfo" packet without setting the watchdog timer? This would keep it from having to update every X minutes which might be nice... Or alternatively, does anyone know of a better way to be handling this? (and I did try SNMP updates too, no effect on getting the IP address)... ----- Craig Norborg CCNA/CCDA/CSE/MCSE 574.254.5254 Datacruz, Inc. FAX 574.256.1144 [EMAIL PROTECTED] <http://www.datacruz.com> Official Tucows Affiliate <http://tucows.datacruz.com> 2500 Miracle Lane, Suite D. PO Box 220 Mishawaka IN 46546-0220 ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email. ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
