id summary reporter owner description type status priority milestone component version severity resolution keywords cc 649 Changing peer-id due to restart should not trigger ip commands nwf stipa "When running 2.3.8 against a git HEAD server, a client restart (caused by, e.g., ping-restart or SIGUSR1) will often get a different peer-id in its post-restart PUSH_REPLY message than it did at initial bringup. This triggers the ""Pulled options changed on restart, will need to close and reopen TUN/TAP device."" behavior; if privileges have been dropped, the interface configuration commands will fail, causing the OpenVPN process to exit." Bug / Defect closed major release 2.3.13 Generic / unclassified OpenVPN 2.3.8 (Community Ed) Not set (select this one, unless your'e a OpenVPN developer) fixed stipa