Bug #4146
closedOpenVPN tap interfaces are down after boot
100%
Description
Setup:
1. Latest snapshot
2. 2 ovpn servers on parent WAN (PPPoE);
3. 1 ovpn server on LAN;
After reboot:
1. All ovpn server ifaces are DOWN;
2. All ovpn server services are UP;
3. All ovpn server processes are RUNNING;
OpenVPN log has nothing to say but "Initialization sequence completed";
System log is "clean";
Bug was introduced in one of December snapshots;
Updated by Chris Buechler over 9 years ago
- Subject changed from OpenVPN server interfaces are down after reboot to Assigned OpenVPN interfaces are down after boot
- Status changed from New to Confirmed
updated subject to actual issue
Updated by Chris Buechler over 9 years ago
- Subject changed from Assigned OpenVPN interfaces are down after boot to OpenVPN tap interfaces are down after boot
corrected specific issue
Updated by Chris Buechler over 9 years ago
It appears it's more than just after boot, tap interfaces seem to always end up missing "UP". Will attempt to further quantify later.
Dmitriy: which type(s) of OpenVPN instances are those?
Updated by Chris Buechler over 9 years ago
- Priority changed from Normal to Very High
Updated by Dmitriy K over 9 years ago
Same issue for openvpn tap clients! everything is UP and RUNNING but iface is DOWN.
Updated by Chris Buechler over 9 years ago
there is a test case for this on 22vpntest. The tap interfaces are missing "UP" in flags.
# ifconfig ovpns10 ovpns10: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> ether 00:bd:b1:06:00:0a nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect status: active Opened by PID 32872 # ifconfig ovpns10 up # ifconfig ovpns10 ovpns10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> ether 00:bd:b1:06:00:0a inet6 fe80::2bd:b1ff:fe06:a%ovpns10 prefixlen 64 scopeid 0x14 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> media: Ethernet autoselect status: active Opened by PID 32872
it works after the "ifconfig up"
Updated by Chris Buechler over 9 years ago
- Assignee changed from Ermal Luçi to Renato Botelho
Updated by Renato Botelho over 9 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset d4e894f6a6f464fd00e39356a23586f8420b31af.
Updated by Renato Botelho over 9 years ago
Applied in changeset 4ab1ffa0b042e4fda87d66de2fd74a1e6db48272.
Updated by Dmitriy K over 9 years ago
I repeat myself: bridged tap client doesn't work after reboot!
Yes, latest commit brought the UP flag to the interface but there is no traffic between sites until instance restart.
before instance restart/after reboot:
ovpnc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
ether 00:bd:ac:6d:00:01
inet6 fe80::2bd:acff:fe6d:1%ovpnc1 prefixlen 64 scopeid 0x9
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
Opened by PID 14515
after instance restart:
ovpnc1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=80000<LINKSTATE>
ether 00:bd:ac:6d:00:01
inet6 fe80::2bd:acff:fe6d:1%ovpnc1 prefixlen 64 scopeid 0x9
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
Opened by PID 31233
Latest snapshot.
Updated by Dmitriy K over 9 years ago
same goes for bridged tap server: everything is UP and RUNNING but no traffic after reboot. Restarting server fixes the problem.
Updated by Kill Bill over 9 years ago
Yes, of course. Since this bridged/TAP OpenVPN nonsense needs PROMISC on both the ovpn and other bridged interfaces -- which is apparently not set.