simultaneous checking

[Kanwar Ranbir Sandhu]

On Tue, 2009-07-21 at 15:58 -0400, Kanwar Ranbir Sandhu wrote:
> On Tue, 2009-07-21 at 15:00 -0400, Kanwar Ranbir Sandhu wrote:
> > The DB shows the exact same Acct-Session-Id that is in the packets
> > themselves. Below are the three rows that get entered into radacct when
> > the AAA test is run from the E120.  Is it the "=" in the
> > callingstationid field that's throwing things off?
> > 
> > erx atm 2/0.42:100.416:000104929        58eb6e48d17d83d4
> > test1 at blah.ca           blah.ca         1.2.3.4         543424928
> > xDSL    2009-07-21 14:39:47     NULL    0       RADIUS
> > speed:UBR:12000                 0       0
> > =23company-E120-1=23this is a description=23100=
> > Framed-User     PPP     4.5.6.7         0       0        
> 
> I just realized that it's not actually just an "=". The complete string
> is "=23", which is ASCII for "#".  I added the "#" to the safe
> characters list, and now in mysql I can see the "=23" replaced with hash
> marks.  This is good.
> 
> Unfortunately, I'm still seeing 3 rows for every AAA attempt.

HA!  I figured it out: the acctsessionid field was truncating the
Acct-Session-Id attribute being received from the NAS.  I bumped the
field up to 100 characters, and viola, the default SQL queries in
dialup.conf started working.  Yeah!

We actually had the same problem with the callingstationid field.

I'd recommend the radacct table have an increased field size for
acctsessionid and callingstationid.  I know it can be tweaked by the
user afterwards, but if it was larger to begin with, problems like the
ones I encountered wouldn't crop up.

Thanks,

Ranbir

-- 
Kanwar Ranbir Sandhu
Linux 2.6.27.25-170.2.72.fc10.x86_64 x86_64 GNU/Linux 
16:20:40 up 3 days, 22:51, 3 users, load average: 2.01, 1.85, 1.73