on boot of an upgrade 13.2 system, with a working tun1 interface config migrated from 13.1,
cat /etc/sysconfig/network/ifcfg-tun1 BOOTPROTO='static' STARTMODE='auto' TUNNEL='tun' TUNNEL_SET_GROUP='openvpn' TUNNEL_SET_OWNER='openvpn' TUNNEL_SET_PERSISTENT='yes' IPV6INIT='no' IPADDR="0.0.0.0"
the system boots to state
tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
but I no longer have my usual tun1 connection to remote vpns.
checking interface toggle returns
ifdown tun1 tun1 device-down
ifup tun1 wicked: ifcfg-tun1: ignoring unspecified ip address 0.0.0.0 wicked: device tun1 failed: operation timed out tun1 setup-in-progress
and
/var/log/messages Nov 10 13:22:24 edge03 wicked: ifcfg-tun1: ignoring unspecified ip address 0.0.0.0 Nov 10 13:22:32 edge03 wicked: device tun1 failed: operation timed out Nov 10 13:22:39 edge03 wicked: device tun1 failed: operation timed out
"0.0.0.0" has been clearly appropriate prior to wicked/13.2.
How's this interface to be properly configured? Or, is this likely a bug?