{% extends "radius/base.html" %} {% load crispy_forms_tags %} {% load radius %} {% block content %}
Username | Framed IP Address | NAS IP Address | Session start | Session stop | Duration | Info |
---|---|---|---|---|---|---|
{{ row.username }} | {{ row.framedipaddress|default:"" }} | {{ row.nasipaddress|default:"" }} | {{ row.acctstarttime }} | {{ row.acctstoptime }} | {{ row.acctsessiontime|time_from_seconds }} | Details |
No results found |
Total online time: | {{ total_time|time_from_seconds }} |
---|---|
Total data sent: | {{ total_sent|filesizeformat }} |
Total received data: | {{ total_received|filesizeformat }} |
Total traffic: | {{ total_sent|add:total_received|filesizeformat }} |
No results
{% endif %} {% endif %} {% endif %} {% block radius-helper %}When choosing timestamp as time filter, the slack is the number of minutes relative to the timestamp that will be used as interval. A timestamp of 2011-03-16 08:57|2 will search between 2011-03-16 08:55 and 2011-03-16 08:59
Username search allows wildcard searching, e.g. you can search for
dat3*
. Please note that the more letters of the username you
include, the faster the search will be. A search for *
, for
example, will probably be very slow.
You can search for switch port on any particular switch by typing the switch hostname/ip address followed by a colon and the name of the switch port. Eg. switch.domain.com:FastEther0/2
Some search results do not contain a timestamp in the Stop field. This occurs when
Stop
message has been received by freeradiusSometimes the displayed session duration does not equal the difference between stop and start time. This occurs if the registered start time was actually not an explicit Start message, but the first sign of life (an Alive message) we got for this session. The Stop message always, as far as I know, contain the length of the session, and so when we have a Stop message this session length is being used during a search for a specific time interval.
We only know the amount of data transferred for sessions where an explicit Stop message has been received. Transfer statistics may therefore be inaccurate because the numbers don't include currently active sessions and because we have no way of making sure at which point in the session the transfers took place.