netdev - RFC: L2TPv3 implementation: some questions

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>] [day] [month] [year] [list]

Message-ID: <484F07D0.5050907@katalix.com>
Date:	Wed, 11 Jun 2008 00:01:36 +0100
From:	James Chapman <jchapman@...alix.com>
To:	netdev <netdev@...r.kernel.org>
Subject: RFC: L2TPv3 implementation: some questions

I'm working on adding L2TPv3 support and would like feedback on a few 
things.

L2TP is currently implemented in one C file, drivers/net/pppol2tp.c and 
provides only L2TPv2 functionality. L2TPv2 carries only PPP, L2TPv3 
carries other types of frame, so this work splits the existing driver to 
separate L2TP from PPP code and adds new drivers for other frame types, 
sitting on top of the common L2TP core. There are now 5 modules, with 
another 3 or more to come later. Should this stuff go in a separate 
subdirectory, say, net/l2tp? This would be in line with pppoatm which 
lives in net/atm.

Are there implications of the pppol2tp module moving from drivers/net to 
net/l2tp?

For L2TPv3, the existing sockaddr_pppol2tp structure can't be used 
because some 16 bit fields are 32 bits in L2TPv3. So I've created a new 
struct sockaddr_pppol2tpv3. Is it ok that one socket family shares these 
two sockaddr structs? (I can have the kernel code derive which one to 
use using the sockaddr length param that is passed in connect() and 
getname() calls.)

In adding support for L2TP over IP, I'm implementing a new L2TPIP socket 
family for the tunnel, which is really just raw IP using IP protocol 
115. There can be only one such socket between a given IP address pair. 
The tunnel socket is how userspace sends and receives L2TP control 
frames, but it is also used by the kernel datapath for data packets. 
Using raw sockets would be possible but I think (unless I'm mistaken) 
raw sockets are always delivered all packets that match the socket's 
protocol. If support were added for raw encapsulation sockets, similar 
to the UDP encapsulation sockets which are used for L2TP over UDP, data 
frames could be consumed by an encapsulation func. However, I think this 
breaks the raw socket semantics which were intended for userspace 
protocol implementations handling both control and user data frames. In 
L2TP/IP's case, the datapath is implemented in the kernel. So is a new 
L2TPIP socket family the right way?

The patch series is already 10+ patches and it is getting increasingly 
difficult to make changes to an early patch in the series (which is 
where the change should have been done in the first place) without 
causing patch conflicts in later patches. To reduce this churn, is it 
acceptable to put such changes in incremental patches in chronological 
order as the work is done?

Thanks!

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development

--
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