Originally posted here:
https://forum.vyos.io/t/encaplimit-equuleus-ipip6/6763
Hello !
On the crux version the creation of an ipip6 tunnel allows an ipv6 parameter encaplimit to none but on equuleus encaplimit only take integer numbers.
My ISP returns errors (and refuses to respond) when a packet contains an encaplimit in the header. Do you know if it is possible to set a value to encaplimit so that it no longer appears in packets sent by vyOS? A possibility of not sending encaplimit?
VyOS 1.2 (crux) supports specifying none as option to encaplimit https://github.com/vyos/vyatta-cfg-system/blob/crux/templates/interfaces/tunnel/node.tag/parameters/ipv6/encaplimit/node.def, but this is no longer available after the tunnel rewrite to XML and Python.
On VyOS 1.2.7, setting encaplimit to none results in:
10: tun10@NONE: <NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/tunnel6 ::1 brd ::2 promiscuity 0 minmtu 68 maxmtu 65407 ip6tnl ipip6 remote ::2 local ::1 hoplimit 64 encaplimit none tclass 0x00 flowlabel 0x00000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
encaplimit 0:
10: tun10@NONE: <NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/tunnel6 ::1 brd ::2 promiscuity 0 minmtu 68 maxmtu 65407 ip6tnl ipip6 remote ::2 local ::1 hoplimit 64 encaplimit 0 tclass 0x00 flowlabel 0x00000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
encaplimit 255:
10: tun10@NONE: <NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/tunnel6 ::1 brd ::2 promiscuity 0 minmtu 68 maxmtu 65407 ip6tnl ipip6 remote ::2 local ::1 hoplimit 64 encaplimit 255 tclass 0x00 flowlabel 0x00000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535