[rbak-nsp] force re-authentication and dhcp max-addrs per circuit-id

[Denis Mikhaylovskiy]

Hi Nikolay

I assume you are using dynamic clips?
In which mode SE is? DHCP Proxy? Please provide more details.
Answering on your first question, in common case you can control this by reducing lease time, let's say to 30 min.

But answer on second question depends on your details again. You say customer = circuit-id/agent-remote-id. Does it mean you have several MACs per access port on your switch? Which network you have L2 or L3 between access switches and SE?


/denis

-----Original Message-----
From: redback-nsp-bounces at puck.nether.net [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Nikolay Abromov
Sent: Wednesday, August 04, 2010 7:32 PM
To: redback-nsp at puck.nether.net
Subject: [rbak-nsp] force re-authentication and dhcp max-addrs per circuit-id

Hello Group,

I have the following questions.

I am using radius to authenticate my subscribers and if a client has
been authenticated once and he/she went offline for couple of ours and
came back online the SmartEdge reply behalf of the radius server
without notifying the radius.I would like to change this behavior and
force the SE to send re-authentication request every 30min.

Another thing I'd like to achieve is the set maximum number of the
subscribers behind a single agent-circuit-id and/or agent-remote-id. I
know how to do it via the radius configurations but I've been asked
can be done with static configurations. With DHCP MAX-ADDR I can limit
the number of the IP addresses given per single MAC address but not
per customer (customer == circuit-id/agent-remote-id).


SEOS Version:  6.1.5.4p3-Release

Thank you in advance


-- 
Nikolay Abromov
Network Engineer
_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp