Menu

l2tpns / News: Recent posts

Release 2.1.21 of L2TPNS

Security [CVE-2006-5873]: Rhys Kidd identified a vulnerability in the handling of heartbeat packets. Drop oversize heartbeat packets.

Note: If clustering is not being used, simply dropping packets to UDP port 32792 on the server is recommended and will avoid the vulnerability.

Posted by Brendan O'Dea 2006-12-18

Release 2.1.0 of L2TPNS

l2tpns is a layer 2 tunneling protocol network server (LNS). It supports up to 65535 concurrent sessions per server/cluster plus ISP features such as rate limiting, walled garden, usage accounting, and more.

New features in 2.1 include support for IPv6, CHAP, interim accounting and gigawords in accounting packets.

Posted by Brendan O'Dea 2005-06-07

Release 2.0.13 of L2TPNS

l2tpns is a layer 2 tunneling protocol network server (LNS). It supports up to 65535 concurrent sessions per server/cluster plus ISP features such as rate limiting, walled garden, usage accounting, and more.

The most significant change since 1.1.0 is a new clustering mechanism, allowing multiple servers to operate as a single end-point.

http://sf.net/projects/l2tpns

Posted by Brendan O'Dea 2004-12-17

Release 1.1.0 of L2TPNS

Release 1.1.0 of L2TPS has just been completed. This release is a huge improvement over the previous release in terms of configurability and stability.

It's now possible to configure almost everything in a running instance by the command-line interface, so it should almost never require dropping any connections.

Also a number of stability bugs have been fixed, after seeing some higher load in the last few months.

Posted by David Parrish 2004-03-05

Initial Public release of L2TPNS

I'm pleased to announce the first public release of L2TPNS.

L2TPNS is a LNS endpoint for L2TP tunnels. It handles the L2TP protocol internally, as well as the PPP protocol. It is very fast and can handle thousands of simultaneous users, and multiple megabytes/second of traffic.

Also supported is RADIUS for user authentication, a walled garden for users who fail authentication, speed throttling, traffic interception, usage accounting and hot-standby clustering capability.... read more

Posted by David Parrish 2003-12-16