Bug #8443
closed
DHCP relay not starting after ovpnc interface is unchecked - vm 2.4.3
100%
Description
Assigned ovpnc interface was chosen as relay interface, config was saved. DHCP relay claimed this interface to be not supported. Then ovpnc was unchecked, service restarted, system rebooted, but DHCP relay still didn't start showing this log:
/status_services.php: The command '/usr/local/sbin/dhcrelay -i vmx1 -i ovpnc1 10.0.13.1' returned exit code '1', the output was 'Requesting: vmx1 as upstream: Y downstream: Y Requesting: ovpnc1 as upstream: Y downstream: Y Internet Systems Consortium DHCP Relay Agent 4.3.6-P1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Unsupported device type 23 for "ovpnc1" If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'
Updated by Vladimir Lind about 6 years ago
DHCP relay started only with disabled openvpn client. Wit enabled openvpn client dhcp relay doesn't start. But after dhcp relay is started starting openvpn doesn't break dhpc relay.
Updated by Anonymous
Updated by Jim Pingle over 4 years ago
- Assignee set to Jim Pingle
Probably need to at least prevent the OpenVPN interfaces from showing as choices for DHCP relay then if it won't run on them. The other issue won't matter once that has been done.
Updated by Jim Pingle over 4 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset c3667958a9e34dd0a4e4b736beb934ca55a0f82f.
Updated by Jim Pingle over 4 years ago
- Target version changed from 2.5.0 to 2.4.5
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Resolved
As expected, OpenVPN interfaces are not available for selection in DHCP Relay on 2.4.5.a.20191218.2354