* This is the VOP Radius mailing list * > 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.
Craig, We have the exact same problem. Our is big, though, because "our" DSL customers are actually customer's of the phone company, authenticated on our RADIUS server. So, it means that I cannot touch the server's (that is, the RADIUS client) configuration. As far as I can see, you caught the right thing: the first AUTH packet does not contain the IP address. If you compare with a regular dial-up AUTH packet from a Portmaster (my case), you'll see the clear difference. The strange thing is this: if I use a *nix RADIUS server called freeradius, it all works fine. Although the RADIUS client (cisco DSL stuff) does not send the IP address with the first AUTH packet, it does send it in the first ACCT packet. Then the RADIUS server gets it and we're all set. Using VPRRS, something goes wrong and THE SAME CLIENT does NOT send the IP address in the first ACCT packet either. It sends the attribute, but instead of the IP address it shows 255.255.255.254. Poor man's solution? Use freeradius as a proxy to VPRRS. It's the only way to get the IP address to VPRRS. I raised that with Vircom during my 30-day free support period, but I got no clear answer. I have debugs from both freeradius and VPRRS. I can probably get something from the telco as well, if I ask kindly enough. I'll post my side's debugs tomorrow, when I'm back at the office. -- Luiz Lima Image Link Internet http://www.imagelink.com.br ** To leave this list, send an email to [EMAIL PROTECTED] and put the word "LEAVE" in the BODY of the email.
