Re: [j-nsp] Subscriber DHCPv6 lease time for IA_NA from Radius Server

Maybe liveness-detection method layer2-liveness-detection and/or overrides client-negotiation-match incoming-interface so the binding just disappears quicker on the MX side? > Le 11 mars 2020 à 11:29, Sebastian Wiesinger a écrit : > > I'm currently testing IPv6 subscriber termination (PPP/L2TP)

Re: [j-nsp] Subscriber DHCPv6 lease time for IA_NA from Radius Server

* Wojciech Janiszewski [2020-03-11 11:43]: > Hi Sebastian, > > If I remember correctly, DHCP Lease Time can be adjusted by using Radius > Session-Timeout attribute. Hi Wojciech, I saw that parameter, but that would at the same time disconnect the PPP Session as a whole as I understand it. It on

Re: [j-nsp] Subscriber DHCPv6 lease time for IA_NA from Radius Server

Hi Sebastian, If I remember correctly, DHCP Lease Time can be adjusted by using Radius Session-Timeout attribute. Regards, Wojciech śr., 11 mar 2020 o 11:32 Sebastian Wiesinger napisał(a): > Hi, > > I'm currently testing IPv6 subscriber termination (PPP/L2TP) on an > MX204 (18.4R2) and I have

[j-nsp] Subscriber DHCPv6 lease time for IA_NA from Radius Server

Hi, I'm currently testing IPv6 subscriber termination (PPP/L2TP) on an MX204 (18.4R2) and I have a bit of a problem with DHCPv6 IA_NA address allocation. By default the lease time for the address is one day (86400 seconds) when the address is received by Radius. The Cisco CPE configures this add