On Mon, Nov 10, 2014, at 04:29 PM, Jan Engelhardt wrote:
In Linux and other systems, 0.0.0.0 is not assigned. You will never see it in `ip addr`. To specify "unset", the empty set rather than the 1-element set {0.0.0.0}, in both display and configuration files, because that makes a lot more sense.
Changing to unset /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" +++ IPADDR='' does eliminate the error (Still, odd that 0.0.0.0's so widely referenced; it's been in use as the initial IP 'address' for pre-vpn-up-state on dozens of machines here, in use with no issues for years ...) Nov 10 16:41:17 net03 systemd[1]: Starting wicked AutoIPv4 supplicant service... Nov 10 16:41:17 net03 systemd[1]: Starting wicked DHCPv6 supplicant service... Nov 10 16:41:17 net03 systemd[1]: Starting wicked DHCPv4 supplicant service... Nov 10 16:41:18 net03 systemd[1]: Started wicked AutoIPv4 supplicant service. Nov 10 16:41:18 net03 systemd[1]: Started wicked DHCPv6 supplicant service. Nov 10 16:41:18 net03 systemd[1]: Started wicked DHCPv4 supplicant service. Nov 10 16:41:18 net03 systemd[1]: Starting wicked network management service daemon... Nov 10 16:41:18 net03 systemd[1]: Started wicked network management service daemon. Nov 10 16:41:18 net03 systemd[1]: Starting wicked network nanny service... Nov 10 16:41:19 net03 systemd[1]: Started wicked network nanny service. Nov 10 16:41:19 net03 systemd[1]: Starting wicked managed network interfaces... Nov 10 16:41:20 net03 wickedd[927]: lo: address 127.0.0.1 covered by a static lease Nov 10 16:41:20 net03 wickedd[927]: lo: address ::1 covered by a static lease Nov 10 16:41:34 net03 wicked[967]: device tun1 failed: operation timed out Nov 10 16:41:34 net03 wicked[967]: lo up Nov 10 16:41:34 net03 wicked[967]: eth0 up Nov 10 16:41:34 net03 wicked[967]: eth1 setup-in-progress Nov 10 16:41:34 net03 wicked[967]: tun1 setup-in-progress Nov 10 16:41:34 net03 systemd[1]: Started wicked managed network interfaces. Nov 10 16:41:56 net03 wicked[1653]: device tun1 failed: operation timed out but reports the "device tun1 failed". checking wicked ifstatus tun1 tun1 setup-in-progress link: #7, state device-up, mtu 1500 type: tun config: compat:/etc/sysconfig/network/ifcfg-tun1 and ifconfig tun1 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, if I (re)start openvpn as I always have pre 13.2, systemctl restart openvpn-custom Job for openvpn-custom.service failed. See "systemctl status openvpn-custom.service" and "journalctl -xn" for details. /var/log/messages Nov 10 16:50:30 net03 systemd[1]: Stopping OpenVPN Server... Nov 10 16:50:30 net03 systemd[1]: Starting OpenVPN Server... Nov 10 16:50:45 net03 up.script[3578]: wicked: device tun1 failed: operation timed out Nov 10 16:50:46 net03 up.script[3578]: tun1 setup-in-progress Nov 10 16:50:46 net03 systemd[1]: openvpn-custom.service: control process exited, code=exited status=162 Nov 10 16:50:46 net03 systemd[1]: Failed to start OpenVPN Server. Nov 10 16:50:46 net03 systemd[1]: Unit openvpn-custom.service entered failed state. This used to work flawlessly prior to the 13.1 -> 13.2 upgrade. Something's changed as a result ... tun1 is not being seen :-/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org