Ticket #2772 (reopened defect)
VPN-settings save error if external interface is selected and goes down.
|Reported by:||trym@…||Owned by:||jamor@…|
|Milestone:||nice to have someday||Component:||openvpn|
If a VPN-server is set to listen on a specific external interface, and the interface goes from a working condition to non-working (for example PPPoE losing DSL-connection), then saving settings produces the error:
"VPN server <name> couldn't be configured, no IP address found for interface eth<x>."
I also suspect that if the connection changes address (again, a DSL-line which has gone down, then comes back up), that the VPN-server does not get re-configured, but continues to listen on the old address, requiring a restart of the VPN-server.
To simulate a DSL-connection going down:
Configure a working external interface, as for example DHCP. Configure VPN-server to listen on that interface. Change the interface to PPPoE with a non-working connection. Save changes: the error will appear.
If changing the VPN-server to listen on all interfaces, the error goes away.
When a DSL-connection goes down, the very first thing an administrator will try is to refresh PPPoE-interface, and will be unable to completely save changes (as after refreshing the interface, settings for 8 modules are saved.) This can make any admin nervous.
- Owner changed from jsoriano@… to jamor@…
- Status changed from new to assigned
- Status changed from assigned to closed
- Resolution set to wontfix
- Status changed from closed to reopened
- Resolution wontfix deleted