From: James Chapman <jchapman@katalix•com>
To: Tomas Agartz <tlund@nxs•se>
Cc: netdev@vger•kernel.org
Subject: Re: unmanaged L2TPv3 ethernet pseudowire Cisco <=> Linux
Date: Wed, 27 Mar 2013 20:56:54 +0000 [thread overview]
Message-ID: <51535D16.4080207@katalix.com> (raw)
In-Reply-To: <Pine.LNX.4.61.1303272104470.20041@envy.nxs.se>
On 27/03/13 20:08, Tomas Agartz wrote:
> On Tue, 26 Mar 2013, James Chapman wrote:
>
>> The issue is that Linux and Cisco use a different default for the
>> L2SpecificSublayer header setting and neither implementation provides
>> a config option to change its setting. :-( The Linux default is to use
>> the Default L2SpecificSublayer as defined in the RFC. Unfortunately
>> the Cisco default is to use no L2SpecificSublayer.
>>
>> The kernel already has an API to allow the L2SpecificSublayer setting
>> to be configured. The missing piece is an iproute2 l2tp config option
>> to configure it. I'll work on an iproute2 patch now to allow this
>> setting to be configured.
>
> I patched my iproute2 with your patch and now my tunnel is working.
> Thank you! :)
Great. Thanks for reporting back.
>> For unmanaged tunnels, these parameters must be manually configured
>> consistently at each side. Both Cisco and Linux default to use no
>> cookies and both already have config parameters to set cookie
>> parameters, if needed. However, for L2SpecificSublayer this isn't the
>> case. We need to add a config option on the Linux side to force the
>> same setting as Cisco is using.
>
> Does the API in the kernel allow you to set the cookie? In that case it
> seems like a good idea to add that to iproute2 as well?
It is already supported. See the cookie and peer_cookie parameters of ip
l2tp add session.
ip l2tp help
or
man ip-l2tp
James
next prev parent reply other threads:[~2013-03-27 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.1303241153000.20041@envy.nxs.se>
2013-03-26 16:26 ` unmanaged L2TPv3 ethernet pseudowire Cisco <=> Linux James Chapman
2013-03-27 20:08 ` Tomas Agartz
2013-03-27 20:56 ` James Chapman [this message]
2013-10-21 15:08 ` Pierre Desvaux
2013-10-21 15:50 ` Stale IPv6 address accumulation on linux 3.2.17 Templin, Fred L
2013-10-22 10:18 ` Hannes Frederic Sowa
2014-04-29 17:49 ` unmanaged L2TPv3 ethernet pseudowire Cisco <=> Linux Esteban Lopez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51535D16.4080207@katalix.com \
--to=jchapman@katalix$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tlund@nxs$(echo .)se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox