I had a pre-existing and working config involving a GRE tunnel (called wccp0) prior to the openrc install/upgrade, which no longer works post upgrade to 0.2.2. The config as I have it in /etc/conf.d/net right now is: vlans_eth0="10" config_eth0="null" vconfig_eth0="set_name_type VLAN_PLUS_VID_NO_PAD" vconfig_vlan10="set_flag 1 set_egress_map 2 6" config_vlan10="192.168.10.12/24" routes_vlan10="default via 192.168.10.1" (that above is all fine...) iptunnel_vpn0="mode gre remote 59.167.255.179 key 0xffffffff ttl 255" config_vpn0="1.1.1.1 peer 59.167.255.179" (this seems to not work) The VLAN10 interface works OK, but the tunnel interface for the GRE does not come up on boot. It seems that the config is just ignored. There is no error loged, just no interface. This is using ifconfig. Either: (a) the config for a GRE tunnel is not as well documented as it could be in /usr/share/doc/openrc/net.example (b) it's broked :-) Reproducible: Always Expected Results: I would expect a 'vpn0' interface to come up and have IP address details as above.
Ok with a bit of coaxing it got a little further: tornado init.d # ls -la /etc/init.d/net.vpn0 lrwxrwxrwx 1 root root 6 Apr 18 00:23 /etc/init.d/net.vpn0 -> net.lo tornado init.d # /etc/init.d/net.vpn0 start * Bringing up interface vpn0 * Creating tunnel vpn0 ... cannot determine tunnel mode (ipip, gre or sit) [ !! ] * ERROR: net.vpn0 failed to start tornado init.d # I thought I'd specified the tunnel mode correctly. Whatever the case, the documentation seems unclear as to whether the creation of the init.d/ symlink in step (1) is needed or not - is the case that it is not needed for a VLAN interface but may be for a GRE tunnel?
try adding 'dev vlan10' to the end of iptunnel_vpn0="mode gre remote 59.167.255.179 key 0xffffffff ttl 255" like this iptunnel_vpn0="mode gre remote 59.167.255.179 key 0xffffffff ttl 255 dev vlan10"
No difference even with 'dev vlan10' on the end...
Roy, any input here?
Created attachment 169952 [details, diff] Don't quote tunnel for ifconfig This patch should fix. A present workaround would be to emerge iproute2.
