Appendix
C.
RADIUS
Accounting
This
section
will
briefly
introduce
the
basic
configuration
of
RADIUS
server
to
work
with
VSA
for
controlling
the
maximum
client
volume
usage
(upload;
download
or
upload
+
download
traffic).
This
VSA
will
be
sent
from
the
RADIUS
server
to
the
gateway
along
with
an
Access
‐
Accept
packet.
In
other
words,
when
the
external
RADIUS
server
accepts
the
request,
it
will
reply
not
only
an
Access
‐
Accept
but
also
a
maximum
value
in
bytes
each
user
is
allowed
to
transfer.
This
value
can
be
the
maximum
upload
traffic,
the
maximum
download
traffic,
or
the
sum
of
the
download
and
upload
traffics
in
bytes
per
user.
The
gateway
will
check
this
value
every
minute;
if
the
user
traffic
reaches
this
value,
the
gateway
will
stop
the
session
of
this
user
and
send
a
“Stop”
to
RADIUS
server.
1.
Description
VSA
is
designed
to
allow
vendors
to
support
their
own
extended
Attributes
which
are
not
covered
in
common
attributes.
It
MUST
not
affect
the
operation
of
the
RADIUS
protocol.
“
Attribute
Number
”
and
“
Attribute
Value
”
can
then
be
designed
to
provide
additional
control
over
RADIUS.
If
the
amount
of
traffic
is
larger
than
4
GB,
the
attributes
of
“XXXX
‐
4GB”
will
be
used.
On
the
other
hand,
when
the
administrator
fills
in
all
attributes,
the
user
will
be
kicked
out
from
the
system
if
any
condition
is
reached.
2.
VSA
configuration
in
RADIUS
server
(IAS
Server)
This
section
will
guide
you
through
a
VSA
configuration
in
your
external
RADIUS
server.
Before
getting
started,
please
directly
or
remotely
access
your
external
RADIUS
server’s
desktop
from
other
PC.
Step
1
Confirm
the
following
key
elements
in
the
RADIUS
server:
users,
groups,
and
policies.
Verify
whether
there
are
already
users
in
the
RADIUS
Server.
Verify
whether
there
are
already
Groups
and
assigned
users
belonging
to
these
Groups
in
the
RADIUS
Server.
Verify
whether
there
are
already
Policies
and
assigned
Groups
belonging
to
these
Policies
in
the
RADIUS
Server.
115
