RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1105438 - ip tunnel help and ip-tunnel manpage have inconsistent list of modes
Summary: ip tunnel help and ip-tunnel manpage have inconsistent list of modes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iproute
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Phil Sutter
QA Contact: Marek Marusic
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-06 06:49 UTC by David Spurek
Modified: 2016-11-03 23:32 UTC (History)
4 users (show)

Fixed In Version: iproute-3.10.0-60.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 23:32:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2162 0 normal SHIPPED_LIVE iproute bug fix and enhancement update 2016-11-03 13:14:33 UTC

Description David Spurek 2014-06-06 06:49:32 UTC 
Description of problem:
ip tunnel help and ip-tunnel manpage have inconsistent list of modes.

ip tunnel help has following list of modes:
[ mode { ipip | gre | sit | isatap | vti } ]

man ip-tunnel has following modes:
MODE :=  { ipip | gre | sit | isatap | ip6ip6 | ipip6 | any }


Version-Release number of selected component (if applicable):
iproute-3.10.0-13.el7

How reproducible:


Steps to Reproduce:
1.ip tunnel help
2.man ip-tunnel
3.

Actual results:
Mode lists are inconsistent

Expected results:
ip tunnel help should show ip6ip6, ipip6, any
mode list in ip-tunnel should show 'vti' in mode list


Additional info:
Comment 3 Pavel Šimerda (pavlix) 2014-11-06 10:27:48 UTC 
Using upstream iproute:

# ip tunnel add help
Usage: ip tunnel { add | change | del | show | prl | 6rd } [ NAME ]
          [ mode { ipip | gre | sit | isatap | vti } ] [ remote ADDR ] [ local ADDR ]
...

# ip -6 tunnel add help
Usage: ip -f inet6 tunnel { add | change | del | show } [ NAME ]
          [ mode { ip6ip6 | ipip6 | ip6gre | vti6 | any } ]
...


This should fix the inconsistency.

diff --git a/man/man8/ip-tunnel.8 b/man/man8/ip-tunnel.8
index fc2d6bd..d22d210 100644
--- a/man/man8/ip-tunnel.8
+++ b/man/man8/ip-tunnel.8
@@ -50,7 +50,7 @@ ip-tunnel - tunnel configuration
 
 .ti -8
 .IR MODE " := "
-.RB " { " ipip " | " gre " | " sit " | " isatap " | " ip6ip6 " | " ipip6 " | " ip6gre " | " any " }"
+.RB " { " ipip " | " gre " | " sit " | " isatap " | " vti " | " ip6ip6 " | " ipip6 " | " ip6gre " | " vti6 " | " any " }"
 
 .ti -8
 .IR ADDR " := { " IP_ADDRESS " |"
@@ -107,10 +107,10 @@ select the tunnel device name.
 set the tunnel mode. Available modes depend on the encapsulating address family.
 .br
 Modes for IPv4 encapsulation available:
-.BR ipip ", " sit ", " isatap " and " gre "."
+.BR ipip ", " gre ", " sit ", " isatap " and " vti "."
 .br
 Modes for IPv6 encapsulation available:
-.BR ip6ip6 ", " ipip6 ", " ip6gre ", and " any "."
+.BR ip6ip6 ", " ipip6 ", " ip6gre ", " vti6 " and " any "."
 
 .TP
 .BI remote " ADDRESS"

On the other hand, it doesn't seem to be very convenient to have to give '-6' for all IPv6 specific types. Instead, in my opinion, the ip command should accept all the types without '-6' and select the address family accordingly. This would be consistent with other ip subcommands that try to do their best in not requiring the user to set the address family when it is implied by other data on the command line. Let me know if you want to extend the bug report to also cover this.

I'm also curious why ipip/ipip6/ip6ip6 are different modes at all and why ip6ip doesn't seem to be supported. I would think that a generic ipip with IPv4 transport addresses could serve as current ipip and ipip6, while a generic ipip with IPv6 transport addresses could serve as missing ip6ip as well as current ip6ip6. The concept of IP-in-IP encapsulation is fairly trivial and I don't see a reason to complicate it that much. I don't know the implementation details on the kernel side, though.
Comment 4 David Spurek 2014-11-06 10:48:01 UTC 
Your fix looks good. I don't have a problem with 'extending' functionality where iproute will accept all types and will choose address family based on given type.

I don't have so much information about ipip/ipip6/ip6ip6 modes. Maybe someone from kernel or previous maintainer can help us.
Comment 6 Pavel Šimerda (pavlix) 2015-04-13 15:36:50 UTC 
Posted upstream with other docs changes.
Comment 9 Mike McCune 2016-03-28 23:23:30 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 10 Phil Sutter 2016-05-30 17:35:57 UTC 
The necessary man page enhancements to resolve this ticket have already been backported during my first attempt at resolving bug 1251186.
Comment 11 Phil Sutter 2016-07-22 09:28:02 UTC 
Reopening this ticket so it can be tested for in QA.
Comment 15 errata-xmlrpc 2016-11-03 23:32:19 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2162.html
Note You need to log in before you can comment on or make changes to this bug.