All of lore.kernel.org
 help / color / mirror / Atom feed
* ip l2tp - suspected defect using IPv6 local/remote addresses
@ 2013-09-11 18:52 Jeff Loughridge
  2013-09-12 10:20 ` James Chapman
  0 siblings, 1 reply; 4+ messages in thread
From: Jeff Loughridge @ 2013-09-11 18:52 UTC (permalink / raw)
  To: netdev

Using IPv6 address as L2TPv3 endpoints doesn't seem to work in
iproute2 3.11. I see a cosmetic defect in the output of 'ip l2tp show
tunnel'. In addition, I can't get tunnels to function with UDP or IP
encapsulation.

root@debian:~# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000
encap udp local a::1 remote a::2 udp_sport 5000 udp_dport 6000
root@debian:~# ip l2tp add session tunnel_id 3000 session_id 1000
peer_session_id 2000
root@debian:~# ip l2tp show tunnel
Tunnel 3000, encap UDP
  From 127.0.0.1 to 127.0.0.1
  Peer tunnel 4000
  UDP source / dest ports: 5000/6000
root@debian:~#

See below for more details about my set-up. I have no problems using
IPv4 endpoints.

root@debian:~# ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN group default qlen 1000
    link/ether 00:0c:29:91:cb:3c brd ff:ff:ff:ff:ff:ff
    inet 5.1.0.100/24 scope global eth0
    inet6 a::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe91:cb3c/64 scope link
       valid_lft forever preferred_lft forever
root@debian:~#
root@debian:~# ip -V
ip utility, iproute2-ss130903
root@debian:~# uname -a
Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux
root@debian:~#
root@debian:~# modprobe l2tp_eth
root@debian:~# lsmod | grep l2tp
l2tp_eth               12738  0
l2tp_netlink           17263  1 l2tp_eth
l2tp_core              17486  2 l2tp_netlink,l2tp_eth

Jeff L.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip l2tp - suspected defect using IPv6 local/remote addresses
  2013-09-11 18:52 ip l2tp - suspected defect using IPv6 local/remote addresses Jeff Loughridge
@ 2013-09-12 10:20 ` James Chapman
  2013-09-12 13:19   ` Ben Hutchings
  0 siblings, 1 reply; 4+ messages in thread
From: James Chapman @ 2013-09-12 10:20 UTC (permalink / raw)
  To: Jeff Loughridge; +Cc: netdev

On 11 September 2013 19:52, Jeff Loughridge <jeffl@alumni.duke.edu> wrote:
>
> Using IPv6 address as L2TPv3 endpoints doesn't seem to work in
> iproute2 3.11. I see a cosmetic defect in the output of 'ip l2tp show
> tunnel'. In addition, I can't get tunnels to function with UDP or IP
> encapsulation.
>
> root@debian:~# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000
> encap udp local a::1 remote a::2 udp_sport 5000 udp_dport 6000
> root@debian:~# ip l2tp add session tunnel_id 3000 session_id 1000
> peer_session_id 2000
> root@debian:~# ip l2tp show tunnel
> Tunnel 3000, encap UDP
>   From 127.0.0.1 to 127.0.0.1
>   Peer tunnel 4000
>   UDP source / dest ports: 5000/6000
> root@debian:~#

You'll need a 3.5 or later kernel for L2TP over IPv6. I see you are
using 3.2. Are you using a version of iproute2 which is not matched to
your kernel?

> See below for more details about my set-up. I have no problems using
> IPv4 endpoints.
>
> root@debian:~# ip addr show eth0
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UNKNOWN group default qlen 1000
>     link/ether 00:0c:29:91:cb:3c brd ff:ff:ff:ff:ff:ff
>     inet 5.1.0.100/24 scope global eth0
>     inet6 a::1/64 scope global
>        valid_lft forever preferred_lft forever
>     inet6 fe80::20c:29ff:fe91:cb3c/64 scope link
>        valid_lft forever preferred_lft forever
> root@debian:~#
> root@debian:~# ip -V
> ip utility, iproute2-ss130903
> root@debian:~# uname -a
> Linux debian 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux
> root@debian:~#
> root@debian:~# modprobe l2tp_eth
> root@debian:~# lsmod | grep l2tp
> l2tp_eth               12738  0
> l2tp_netlink           17263  1 l2tp_eth
> l2tp_core              17486  2 l2tp_netlink,l2tp_eth
>
> Jeff L.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip l2tp - suspected defect using IPv6 local/remote addresses
  2013-09-12 10:20 ` James Chapman
@ 2013-09-12 13:19   ` Ben Hutchings
  2013-09-13  0:46     ` Jeff Loughridge
  0 siblings, 1 reply; 4+ messages in thread
From: Ben Hutchings @ 2013-09-12 13:19 UTC (permalink / raw)
  To: James Chapman; +Cc: Jeff Loughridge, netdev

On Thu, 2013-09-12 at 11:20 +0100, James Chapman wrote:
> On 11 September 2013 19:52, Jeff Loughridge <jeffl@alumni.duke.edu> wrote:
> >
> > Using IPv6 address as L2TPv3 endpoints doesn't seem to work in
> > iproute2 3.11. I see a cosmetic defect in the output of 'ip l2tp show
> > tunnel'. In addition, I can't get tunnels to function with UDP or IP
> > encapsulation.
> >
> > root@debian:~# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000
> > encap udp local a::1 remote a::2 udp_sport 5000 udp_dport 6000
> > root@debian:~# ip l2tp add session tunnel_id 3000 session_id 1000
> > peer_session_id 2000
> > root@debian:~# ip l2tp show tunnel
> > Tunnel 3000, encap UDP
> >   From 127.0.0.1 to 127.0.0.1
> >   Peer tunnel 4000
> >   UDP source / dest ports: 5000/6000
> > root@debian:~#
> 
> You'll need a 3.5 or later kernel for L2TP over IPv6. I see you are
> using 3.2. Are you using a version of iproute2 which is not matched to
> your kernel?
[...]

The iproute2 version number only indicates which kernel features it
supports; it is supposed to be backward-compatible.  And it really
should not silently fail like this, although this may well be a bug in
the API that can't be fixed in userland...

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip l2tp - suspected defect using IPv6 local/remote addresses
  2013-09-12 13:19   ` Ben Hutchings
@ 2013-09-13  0:46     ` Jeff Loughridge
  0 siblings, 0 replies; 4+ messages in thread
From: Jeff Loughridge @ 2013-09-13  0:46 UTC (permalink / raw)
  To: Ben Hutchings; +Cc: James Chapman, netdev

I confirmed IPv6 endpoints work using a 3.5 kernel. Thanks, guys.

On Thu, Sep 12, 2013 at 9:19 AM, Ben Hutchings
<bhutchings@solarflare.com> wrote:
> On Thu, 2013-09-12 at 11:20 +0100, James Chapman wrote:
>> On 11 September 2013 19:52, Jeff Loughridge <jeffl@alumni.duke.edu> wrote:
>> >
>> > Using IPv6 address as L2TPv3 endpoints doesn't seem to work in
>> > iproute2 3.11. I see a cosmetic defect in the output of 'ip l2tp show
>> > tunnel'. In addition, I can't get tunnels to function with UDP or IP
>> > encapsulation.
>> >
>> > root@debian:~# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000
>> > encap udp local a::1 remote a::2 udp_sport 5000 udp_dport 6000
>> > root@debian:~# ip l2tp add session tunnel_id 3000 session_id 1000
>> > peer_session_id 2000
>> > root@debian:~# ip l2tp show tunnel
>> > Tunnel 3000, encap UDP
>> >   From 127.0.0.1 to 127.0.0.1
>> >   Peer tunnel 4000
>> >   UDP source / dest ports: 5000/6000
>> > root@debian:~#
>>
>> You'll need a 3.5 or later kernel for L2TP over IPv6. I see you are
>> using 3.2. Are you using a version of iproute2 which is not matched to
>> your kernel?
> [...]
>
> The iproute2 version number only indicates which kernel features it
> supports; it is supposed to be backward-compatible.  And it really
> should not silently fail like this, although this may well be a bug in
> the API that can't be fixed in userland...
>
> Ben.
>
> --
> Ben Hutchings, Staff Engineer, Solarflare
> Not speaking for my employer; that's the marketing department's job.
> They asked us to note that Solarflare product names are trademarked.
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-09-13  0:47 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-11 18:52 ip l2tp - suspected defect using IPv6 local/remote addresses Jeff Loughridge
2013-09-12 10:20 ` James Chapman
2013-09-12 13:19   ` Ben Hutchings
2013-09-13  0:46     ` Jeff Loughridge

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.