Setup guide

To enable RADIUS AAA:
[admin@Wandy] ppp aaa> set use-radius=yes
[admin@Wandy] ppp aaa> print
use-radius: yes
accounting: yes
interim-update: 0s
[admin@Wandy] ppp aaa>
Local IP Traffic Accounting
ip accounting
Description
As each packet passes through the router, the packet source and destination addresses are matched
against an IP pair in the accounting table and the traffic for that pair is increased. The traffic of PPP,
PPTP, PPPoE, ISDN and HotSpot clients can be accounted on per-user basis too. Both the number
of packets and the number of bytes are accounted.
If no matching IP or user pair exists, a new entry will be added to the table
Only the packets that enter and leave the router are accounted. Packets that are dropped in the router
are not counted as well as ones that are sent from the router itself. Packets that are NATted on the
router will be accounted for with the actual IP addresses on each side. Packets that are going
through bridged interfaces (i.e. inside the bridge interface) are also accounted correctly.
Property Description
enabled (yes | no; default: no) - whether local IP traffic accounting is enabled
threshold (integer; default: 256) - maximum number of IP pairs in the accounting table (maximal
value is 8192)
Notes
For bidirectional connections two entries will be created.
Each IP pair uses approximately 100 bytes
When the threshold limit is reached, no new IP pairs will be added to the accounting table. Each
packet that is not accounted in the accounting table will then be added to the uncounted counter!
Example
Enable IP accounting:
[admin@Wandy] ip accounting> set enabled=yes
[admin@Wandy] ip accounting> print
enabled: yes
threshold: 256
[admin@Wandy] ip accounting>
Example
See the uncounted packets:
[admin@Wandy] ip accounting uncounted> print
packets: 0
bytes: 0
[admin@Wandy] ip accounting uncounted>