27 Aug, 2011

1 commit

• bcb949b88   headers, net: Use __kernel_sa_family_t in more definitions shared with userland ... Browse Code »

  Complete the work started with commit
  6602a4baf4d1a73cc4685a39ef859e1c5ddf654c ('net: Make userland include
  of netlink.h more sane').

  Signed-off-by: Ben Hutchings
  Signed-off-by: David S. Miller

  Ben Hutchings

  2011-08-27 00:02:50 +0800  

04 Apr, 2010

2 commits

• 309795f4b   l2tp: Add netlink control API for L2TP ... Browse Code »

  In L2TPv3, we need to create/delete/modify/query L2TP tunnel and
  session contexts. The number of parameters is significant. So let's
  use netlink. Userspace uses this API to control L2TP tunnel/session
  contexts in the kernel.

  The previous pppol2tp driver was managed using [gs]etsockopt(). This
  API is retained for backwards compatibility. Unlike L2TPv2 which
  carries only PPP frames, L2TPv3 can carry raw ethernet frames or other
  frame types and these do not always have an associated socket
  family. Therefore, we need a way to use L2TP sessions that doesn't
  require a socket type for each supported frame type. Hence netlink is
  used.

  Signed-off-by: James Chapman
  Reviewed-by: Randy Dunlap
  Signed-off-by: David S. Miller

  James Chapman

  2010-04-04 05:56:05 +0800  
• 0d76751fa   l2tp: Add L2TPv3 IP encapsulation (no UDP) support ... Browse Code »

  This patch adds a new L2TPIP socket family and modifies the core to
  handle the case where there is no UDP header in the L2TP
  packet. L2TP/IP uses IP protocol 115. Since L2TP/UDP and L2TP/IP
  packets differ in layout, the datapath packet handling code needs
  changes too. Userspace uses an L2TPIP socket instead of a UDP socket
  when IP encapsulation is required.

  We can't use raw sockets for this because the semantics of raw sockets
  don't lend themselves to the socket-per-tunnel model - we need to

  Signed-off-by: David S. Miller

  James Chapman

  2010-04-04 05:56:04 +0800