I have configured a Mikrotik 750 routerboard as pppoe Server. As AAA server is a remote Radius (Porta Billing).
A user for example TEST is configured in Radius with the profile download/ upload 512/128 kbps. But when i try to connect via a pppoe client with this user TEST, it got authenticated, but is not receiving the profile properly. The logs at mikrotik is as below:

Aug/20/2011 13:25:14 radius,debug,packet Idle-Timeout = 86400
Aug/20/2011 13:25:14 radius,debug,packet Session-Timeout = 0
Aug/20/2011 13:25:14 radius,debug,packet Ascend-Data-Rate = 512000
Aug/20/2011 13:25:14 radius,debug,packet Unknown-Attribute(type=255) = 0x0001f400
Aug/20/2011 13:25:14 radius,debug,packet Framed-IP-Address = 255.255.255.254
Aug/20/2011 13:25:14 radius,debug,packet Framed-IP-Netmask = 255.255.255.255
Aug/20/2011 13:25:14 radius,debug,packet Framed-MTU = 1500

We contact the RAdius Support and they say that the radius is sending ok the attribute to the mikrotik as below: but the problem might be at the Mikrotik not understanding the radius:


Service-Type = Framed-User
Idle-Timeout = 86400
Session-Timeout = 0
Ascend-Data-Rate = 512000
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv CORRECT VALUE
Ascend-Xmit-Rate = 128000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ CORRECT VALUE
Framed-IP-Address = 255.255.255.254
Framed-IP-Netmask = 255.255.255.255
Framed-MTU = 1500

Please help me in this issue
Thank you

Gerta

http://wiki.mikrotik.com/wiki/Manual:RADIUS_Client

Mikrotik-Rate-Limit - Datarate limitation for clients. Format is: rx-rate[/tx-rate] [rx-burst-rate[/tx-burst-rate] [rx-burst-threshold[/tx-burst-threshold] [rx-burst-time[/tx-burst-time] [priority] [rx-rate-min[/tx-rate-min]]]] from the point of view of the router (so "rx" is client upload, and "tx" is client download). All rates should be numbers with optional 'k' (1,000s) or 'M' (1,000,000s). If tx-rate is not specified, rx-rate is as tx-rate too. Same goes for tx-burst-rate and tx-burst-threshold and tx-burst-time. If both rx-burst-threshold and tx-burst-threshold are not specified (but burst-rate is specified), rx-rate and tx-rate is used as burst thresholds. If both rx-burst-time and tx-burst-time are not specified, 1s is used as default. Priority takes values 1..8, where 1 implies the highest priority, but 8 - the lowest. If rx-rate-min and tx-rate-min are not specified rx-rate and tx-rate values are used. The rx-rate-min and tx-rate-min values can not exceed rx-rate and tx-rate values.

You can try sending back the Mikrotik-Rate-Limit attribute instead.
But the two attributes you want to send are also supported:

Ascend-Data-Rate - tx/rx data rate limitation if multiple attributes are provided, first limits tx data rate, second - rx data rate. If used together with Ascend-Xmit-Rate, specifies rx rate. 0 if unlimited. Ignored if Rate-Limit attribute is present
Ascend-Xmit-Rate - tx data rate limitation. It may be used to specify tx limit only instead of sending two sequental Ascend-Data-Rate attributes (in that case Ascend-Data-Rate will specify the receive rate). 0 if unlimited. Ignored if Rate-Limit attribute is present

So if you need that working and it isn't send an email to support@mikrotik.com. This forum is for the user community and the vendor may not read your thread - but only the vendor can fix bugs. It does seem to be a bug, my RADIUS dictionaries also claim that Ascend-Xmit-Rate is type 255.