Bug #11662
closed
QinQ using OpenVPN ``ovpn`` interface as a parent is not configured at boot time
Added by jo ko over 3 years ago.
Updated almost 3 years ago.
Plus Target Version:
22.01
Description
QinQ interfaces created on top of ovpns or ovpnc disappears after reboot.
(for example ovpns1.100.2000 or ovpnc2.100.2000)
- Log message : Mar 8 14:47:17 hostname php398: rc.bootup: interface_qinq_configure called with invalid if.
- Category changed from OpenVPN to Interfaces
- Assignee deleted (
jo ko)
- Subject changed from QinQ interface over ovpns and ovpnc to QinQ using OpenVPN ``ovpn`` interface as a parent is not configured at boot time
- Target version set to CE-Next
- Status changed from New to Pull Request Review
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
- Target version changed from CE-Next to 2.6.0
- Plus Target Version set to 21.09
PR has been merged. Thanks!
- % Done changed from 0 to 100
- Plus Target Version changed from 21.09 to 22.01
I replicated the issue on the following:
2.5.2-RELEASE (amd64)
built on Fri Jul 02 15:33:00 EDT 2021
FreeBSD 12.2-STABLE
At the latest dev release:
2.6.0-BETA (amd64)
built on Thu Dec 16 06:22:38 UTC 2021
FreeBSD 12.3-STABLE
The OpenVPN interface was not listed as a Parrent interface option when creating QinQ. If that's expected, then feel free to mark this ticket resolved.
Otherwise, please check again.
- Status changed from Feedback to Resolved
I have overseen the fact that OpenVPN must be in TAP mode.
Tested QinQ with OpenVPN in TAP mode as a parent interface, and the interface didn't disappear after reboot. Ticket resolved.
Also available in: Atom
PDF
Updated by 
Updated by Viktor Gurov 
Updated by 
Updated by