Radius attributes extension

I don’t know if it’s possible but…
By now, only possible solution for billing users differently based on where they go and what kind of traffic they make was to use traffic-flow.
But, is it possible to use Framed-Filter and radius attributes extension to accomplish the sam thing?

For example, when user is connected radius sends framed-ip, framed-protocol etc. to mikrotik. You can also send framed-filter and mikrotik will create dynamic filter for every packet that goes to and from specific user. If we can send arrays of counters in interim-packets and stop-packet we can see exactly local and remote traffic? It realy depend on rules we setup.

array[‘dynamic-rules’]
{
fw_rule[0] = 20MB
fw_rule[1] = 40MB
fw_rule[2] = 60MB
fw_rule[3] = 5MB
}

We would need to take care that rule order is not changing, or in case we change order of rules, we should change billing scripts accordingly, but, it could work?

as far as I remember, you can only setup filtering rules, not mangle rules, so you cannot shape traffic with help of ‘Framed-Filter’

I wasn’t talking about traffic shaping, just traffic counting.

For example, we can have 1 rule/filter that counts local traffic and 1 one rule/counter that counts the rest of the traffic.
When user disconnects we can send those counters inside Stop Packet.

Or we can have counters for port 80 and counters for port 21 etc.

Bottom line is that we can use Framed-Filter-Id for billing, and maybe we can manage to do traffic counting based on src-ip/dst-ip pairs, without need for traffic-flow.

oh, re-read your post… no, you cannot add fields to RADIUS accounting packets - and I think it won’t be possible at all. so you should use NetFlow