Bug 1085965

Summary: [RFE] Add ability set permanently the l2tpv3 tunnel from ifcfg
Product: Red Hat Enterprise Linux 7 Reporter: Eric V. Bahmer <bahmer>
Component: initscriptsAssignee: Jan Macku <jamacku>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: iarlyy, itamar, jamacku, jonathan, jscotka, lnykryn, plautrba, volga629, vpavlin
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 895791 Environment:
Last Closed: 2020-05-13 07:59:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric V. Bahmer 2014-04-09 18:28:07 UTC
RHEL 7 public beta has the same issue.

+++ This bug was initially created as a clone of Bug #895791 +++

Add ability  set permanently the  l2tpv3 tunnel from ifcfg.
Right now possible set only gre tunnel with ifcfg-gre1.
Ip route 2 was added option:

[bendersky@laptop ~]$ ip l2tp help
Usage: ip l2tp add tunnel
          remote ADDR local ADDR
          tunnel_id ID peer_tunnel_id ID
          [ encap { ip | udp } ]
          [ udp_sport PORT ] [ udp_dport PORT ]
Usage: ip l2tp add session [ name NAME ]
          tunnel_id ID
          session_id ID peer_session_id ID
          [ cookie HEXSTR ] [ peer_cookie HEXSTR ]
          [ offset OFFSET ] [ peer_offset OFFSET ]
       ip l2tp del tunnel tunnel_id ID
       ip l2tp del session tunnel_id ID session_id ID
       ip l2tp show tunnel [ tunnel_id ID ]
       ip l2tp show session [ tunnel_id ID ] [ session_id ID ]

Where: NAME   := STRING
       ADDR   := { IP_ADDRESS | any }
       PORT   := { 0..65535 }
       ID     := { 1..4294967295 }
       HEXSTR := { 8 or 16 hex digits (4 / 8 bytes) }


When working with pseudowire ifcfg-l2tpeth0 and for vlan ifcfg-l2tpeth0.200 are necessary on boot and on permanent bases.

VLAN=yes should be included in config.

--- Additional comment from Dominik 'Rathann' Mierzejewski on 2013-01-16 15:25:00 EST ---

This has nothing to do sysconftool. I'm guessing this should go against initscripts.

--- Additional comment from Slava on 2013-01-16 20:04:00 EST ---

The main config should in /etc/sysconfig/network-scripts/ifcfg-l2tpeth0 or /etc/sysconfig/network-scripts/ifcfg-l2tpeth0.200 for vlan. And /etc/init.d/network script should know to parse it.

--- Additional comment from Fedora Admin XMLRPC Client on 2013-09-04 10:49:49 EDT ---

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

--- Additional comment from Slava on 2013-10-14 23:54:41 EDT ---

Hello Everyone,
Is any updates ?

Slava.

--- Additional comment from Slava on 2013-10-23 00:11:26 EDT ---

Hello Everyone,
Please download src rpm from my repo for RHEL6 it include all patches for init scripts l2tpv3 implementation.

ftp://ftpsrv01.networklab.ca/centos/6/SRPM/initscripts
9.03.38-1.0.3.el6.2.src.rpm

--- Additional comment from Slava on 2013-10-23 22:06:53 EDT ---

Here working version on RHEL6. Please review it.


ftp://ftpsrv01.networklab.ca/centos/6/SRPM/initscripts-9.03.38-1.0.5.el6.2.src.rpm

--- Additional comment from Lukáš Nykrýn on 2013-10-24 03:01:36 EDT ---

Thanks! I will look at it.

--- Additional comment from Fedora End Of Life on 2013-12-21 10:17:43 EST ---

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 RHEL Program Management 2014-04-17 05:47:24 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Jan Macku 2020-05-13 07:59:01 UTC
Hello Eric,

Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please visit: https://access.redhat.com/support

Jan