Thanks, I didn't think about searching for it when the documentation didn't have it - usually if it's not in the documentation it can't be found!
This is now working for me, I'll recap for the sake of anybody who comes upon this thread in a search:
A radius reply attirbute with Mikrotik-Address-List will put the IP address that's been allocated to the user into the correct address list. Note that you should not include a "rate-limit" attribute, as you should not double queue the traffic. My RADIUS replies look like:
Vendor Attribute Data
Standard User-Service Framed-User
Standard Framed-Protocol PPP
Standard Session-Timeout 86400
Mikrotik Mikrotik-Address-List Standard
Each pppoe session is now being assigned to the correct address list. However, I set up a test:
- Two laptops are associated to a 2.4GHz-B/G AP
- Each laptop connects with PPPoE and is assigned the "Standard" address list
- Queueing is set up as the example above
The results are that the two PPPoE connections share the resources of the "Standard_Download" when doing an RX b-test from the laptops. That is to say, I start b-test on one laptop and it immediately RX'es 1Mbps. Then I start b-test on the 2nd laptop, and over the course of a minute or two they balance out to 500kbps each.
So now the question is - what needs to be changed in my queue tree configuration such that each member of the list would get the full 1Mbps until the parent queue reaches resource contention?
For example:
Total_Download limit => 10M
Enhanced_Download (per customer) => 2M
Standard_Download (per customer) => 1M
Restricted_Download (per customer) => 768kbps
The idea is, each customer should have access to their full rate until Total_Download reaches contention, then each customer would be granted packets evenly so as to fairly share the available bandwidth.