netdev - Re: [PATCH 00/10 net-next] l2tp: misc fixes and add L2TPv3 IP encap over IPv6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Apr 2012 13:46:37 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	jchapman@...alix.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 00/10 net-next] l2tp: misc fixes and add L2TPv3 IP
 encap over IPv6

From: James Chapman <jchapman@...alix.com>
Date: Mon, 30 Apr 2012 08:48:45 +0100

> This patch series includes several L2TP fixes / cleanups and adds
> L2TPv3 IP encapsulation support for IPv6, building on the L2TP UDP
> IPv6 support recently added by Ben LaHaise.
> 
>   1. l2tp: fix locking of 64-bit counters for smp
>   2. l2tp: Use ip4_datagram_connect() in l2tp_ip_connect()
>   3. l2tp: remove unused stats from l2tp_ip socket
>   4. pppox: Replace __attribute__((packed)) in if_pppox.h
>   5. l2tp: pppol2tp_connect() handles ipv6 sockaddr variants
>   6. l2tp: show IPv6 addresses in l2tp debugfs file
>   7. l2tp: netlink api for l2tpv3 ipv6 unmanaged tunnels
>   8. ipv6: export ipv6 functions for use by other protocols
>   9. l2tp: introduce L2TPv3 IP encapsulation support for IPv6
>  10. l2tp: let iproute2 create L2TPv3 IP tunnels using IPv6
> 
> Patches 1-4 are fixes / cleanups.
> Patches 5-6 improve on the L2TP UDP IPv6 changes recently added.
> Patches 7-10 add functionality.
> 
> A patch for iproute2 to add support for unmanaged L2TPv3 ethernet
> tunnels over IPv6 will be submitted separately.

Series applied to net-next, thanks James.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html