DHCP expiration/renew issue
Posted: Mon Mar 23, 2015 2:09 pm
Hi,
I have the following issue. I'm using the Virtual DHCP to give clients addresses in a Local Bridge setup. The expiration is set to 3600. While some clients renew successfully the lease when the expiration time is over, some do not, according to the logs. Thus users can be connected and use the VPN even after their DHCP lease is expired and not renewed. Now the issue is, if a new user connects, it can get the IP originally leased to the first one. This results in IP addresses leased to userA to be leased to userB too, while both are connected.
After some experimentation it seems the softether client and openvpn tap can and will renew expired DHCP lease, but others do not (neither openvpn tun, l2tp, sstp). Is this some limitation of the clients? Could softether retain the DHCP re-lease until the session is open?
This is a serious issue in terms of legal, and a nightmare for maintenance.
Using latest 9529 server on Windows.
I have the following issue. I'm using the Virtual DHCP to give clients addresses in a Local Bridge setup. The expiration is set to 3600. While some clients renew successfully the lease when the expiration time is over, some do not, according to the logs. Thus users can be connected and use the VPN even after their DHCP lease is expired and not renewed. Now the issue is, if a new user connects, it can get the IP originally leased to the first one. This results in IP addresses leased to userA to be leased to userB too, while both are connected.
After some experimentation it seems the softether client and openvpn tap can and will renew expired DHCP lease, but others do not (neither openvpn tun, l2tp, sstp). Is this some limitation of the clients? Could softether retain the DHCP re-lease until the session is open?
This is a serious issue in terms of legal, and a nightmare for maintenance.
Using latest 9529 server on Windows.