freeradius + MySQL not working after upgrade from 1.0.1

[marc-ml at neoharmonix.net]

Hello.  I have encountered a problem upon upgrading from freeradius
version 1.0.1.  I'm using the sql module (rlm_sql_mysql) for authorization
and accounting of dialup users (reselling dialup from several networks). 
After upgrading to 1.0.2 with the same configuration, it no longer works. 
>From the logs I see that authorization works:
  Login OK: [xxxx at xxxxx.com] (from client xxxxxxxx port 15)
and it sends "Access-Accept" but the connecting dialup user can't connect.

I now have two servers with the same freeradius configuration (minus minor
changes from the upgrade) and the same MySQL database with one running
version 1.0.1 (which works) and the other running 1.0.4 (which does not
work).  Comparing the logs produced by "radiusd -X", I see that the only
substantial difference is the X-Ascend-Data-Filter Attributes which look
something like this:


WORKING VERSION 1.0.1:

Sending Access-Accept of id 158 to 216.126.136.243:1814
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 255.255.255.254
Framed-IP-Netmask = 255.255.255.255
Port-Limit = 1
Idle-Timeout = 600
Session-Timeout = 28800
Filter-Id = "data6330_1"
Proxy-State = 0x3532
X-Ascend-Data-Filter += "ip in forward tcp est"
X-Ascend-Data-Filter += "ip in forward dstip 200.100.100.10/32 0"
X-Ascend-Data-Filter += "ip in forward dstip 66.55.44.0/24 0"
X-Ascend-Data-Filter += "ip in forward dstip 66.44.55.0/24 0"
X-Ascend-Data-Filter += "ip in drop tcp dstport = 25"
X-Ascend-Data-Filter += "ip in forward 0"
Finished request 0
Going to the next request



NON-WORKING VERSION 1.0.4:

Sending Access-Accept of id 154 to 216.126.136.243:1814
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 255.255.255.254
Framed-IP-Netmask = 255.255.255.255
Port-Limit = 1
Idle-Timeout = 600
Session-Timeout = 28800
X-Ascend-Data-Filter += 0x697020696e20666f72776172642074637020657374
X-Ascend-Data-Filter +=
0x697020696e20666f7277617264206473746970203230392e3130322e3130372e37372f33322030
X-Ascend-Data-Filter +=
0x697020696e20666f72776172642064737469702036342e32342e33352e302f32342030
X-Ascend-Data-Filter +=
0x697020696e20666f72776172642064737469702036362e34352e3234332e302f32342030
X-Ascend-Data-Filter +=
0x697020696e2064726f702074637020647374706f7274203d203235
X-Ascend-Data-Filter += 0x697020696e20666f72776172642030
Filter-Id = "data6330_1"
Proxy-State = 0x3234
Finished request 3
Going to the next request



The working version proceeds to do accounting sometime after sending that
while the other version stops there.  I suspect those long strings are the
culprit since everything else in the logs looks the same.  The attributes
come from the database and they look fine there.  Any ideas how I can get
the previous behavior or get the newer versions to work?  Or maybe the
problem is something else?

Thanks,
Marc