OpenL2TP

Hi,

After digging through the logs and the debug output, i was able to
track this problem down to the l2tp_statusfile code.

It turned out that openl2tpd did not remeber that it had a pppd
running on that session.

on startup:
sess 14371/18268: spawned pppd pid=826
DEBUG: usl_pid_record_child: pid=826

on session shutdown:

DEBUG: l2tp_session_down_ind: tunl 14371/18268
DEBUG: l2tp_session_inc_use_count: tunl 14371/18268: count now 5
DEBUG: ppp_unix_session_down: 14371/18268: tid=14371 sid=18268
DEBUG: ppp_unix_find_by_id: look for 14371/18268
DEBUG: ppp_unix_find_by_id: at 14371/18268 0x8d97e10
DEBUG: ppp_unix_pppd_terminate: pid=0
^^^^^^^^^ the pid is gone....

However, the real cause is in l2tp_statusfile_session_up_ind():

...
(void) l2tp_statusfile_session_deleted_ind(session, tunnel_id, session_id);
result = l2tp_statusfile_session_created_ind(session, tunnel_id, session_id);

and l2tp_statusfile_session_deleted_ind() calls *suprise* ->
l2tp_old_session_deleted_hook(), which of course is
ppp_unix_session_deleted().
Or as gdb backtrace:

(gdb) bt
#0  ppp_unix_session_deleted (session=0x8a1d0a0, tunnel_id=51784,
session_id=62693) at ppp_unix.c:1057
#1  0x080773a7 in l2tp_statusfile_session_deleted_ind
(session=0x8a1d0a0, tunnel_id=51784, session_id=62693) at
l2tp_statusfile.c:477
#2  0x080775be in l2tp_statusfile_session_up_ind (session=0x8a1d0a0,
tunnel_id=51784, session_id=62693, peer_tunnel_id=45633,
peer_session_id=35)
   at l2tp_statusfile.c:530
#3  0x0806900b in l2tp_session_up_ind (tunnel=0x8a1ca50,
session=0x8a1d0a0) at l2tp_session.c:622
#4  0x0806ab88 in l2tp_session_send_iccn (tun=0x8a1ca50,
sess=0x8a1d0a0) at l2tp_session.c:1655
#5  0x0806b50e in l2tp_session_laic_send_iccn (tunnel=0x8a1ca50,
sess=0x8a1d0a0, arg3=0x0) at l2tp_session.c:2208
#6  0x0807f39d in usl_fsm_handle_event (fsmi=0x8a1d0c0, event=5,
arg1=0x8a1ca50, arg2=0x8a1d0a0, arg3=0x0) at usl_fsm.c:50
#7  0x080686e6 in l2tp_session_handle_event (session=0x8a1d0a0,
event=5) at l2tp_session.c:473
#8  0x0806a23c in l2tp_session_handle_msg_icrp (peer=0x8a1ca28,
tunnel=0x8a1ca50, session_id=62693, avps=0xbfecf5e0) at
l2tp_session.c:1347
#9  0x0805c507 in l2tp_tunnel_recv (tunnel=0x8a1ca50, tunnel_id=51784,
session_id=62693, pkt=0x8a1d448) at l2tp_tunnel.c:2334
#10 0x08064b7c in l2tp_xprt_deliver_up (xprt=0x8a1cca8, pkt=0x8a1d448)
at l2tp_transport.c:281
#11 0x08064e06 in l2tp_xprt_deliver_to_protocol (xprt=0x8a1cca8,
pkt=0x8a1d448) at l2tp_transport.c:322
#12 0x080656bf in l2tp_xprt_recv (xprt=0x8a1cca8, pkt=0x8a1d448) at
l2tp_transport.c:505
#13 0x08056ce5 in l2tp_net_recv_core (fd=14, from=0x0, msg=0xbfecf850,
recv_len=28, ipi=0x0) at l2tp_network.c:371
#14 0x08057473 in l2tp_net_recv (fd=14, arg=0x8a1ca50) at l2tp_network.c:546
#15 0x0807d670 in usl_fd_poll () at usl_fd.c:266
#16 0x0807e340 in usl_main_loop () at usl_signal.c:216
#17 0x0804d978 in main (argc=10, argv=0xbfecfcb4) at l2tp_main.c:205

ppp_unix_session_deleted() clears the ppp context, thus openl2tpd
thinks there is no longer a pppd running on the session.

Regards
Andreas


On Fri, May 22, 2009 at 7:30 PM, Andreas Schultz <aschultz@...> wrote:
> Hi,
>
> It seems that a tunnel shutdown caused by a lost connection (i pulled
> the network cable on the client) does not terminate the pppd daemon on
> top of the tunnel.
> After the connection comes back, openl2tpd will start a new pppd
> instance which creates a new ppp interface. This effectivly leads to
> two active ppp interfaces, both with the same IP and remote peer,
> rendering the connection useless.
>
> kernel 2.6.27.21, openl2tp 1.6
>
> Regards
> Andreas

[...]

Hi Andreas,

Thanks for this report and detailed analysis. You've clearly found a
bug. The statusfile code doesn't get a lot of use because it isn't
enabled by default. I assume you are using it because you've disabled RPC.

Thanks again.

/james

Andreas Schultz wrote:
> Hi,
> 
> After digging through the logs and the debug output, i was able to
> track this problem down to the l2tp_statusfile code.
> 
> It turned out that openl2tpd did not remeber that it had a pppd
> running on that session.
> 
> on startup:
> sess 14371/18268: spawned pppd pid=826
> DEBUG: usl_pid_record_child: pid=826
> 
> on session shutdown:
> 
> DEBUG: l2tp_session_down_ind: tunl 14371/18268
> DEBUG: l2tp_session_inc_use_count: tunl 14371/18268: count now 5
> DEBUG: ppp_unix_session_down: 14371/18268: tid=14371 sid=18268
> DEBUG: ppp_unix_find_by_id: look for 14371/18268
> DEBUG: ppp_unix_find_by_id: at 14371/18268 0x8d97e10
> DEBUG: ppp_unix_pppd_terminate: pid=0
> ^^^^^^^^^ the pid is gone....
> 
> However, the real cause is in l2tp_statusfile_session_up_ind():
> 
> ...
> (void) l2tp_statusfile_session_deleted_ind(session, tunnel_id, session_id);
> result = l2tp_statusfile_session_created_ind(session, tunnel_id, session_id);
> 
> and l2tp_statusfile_session_deleted_ind() calls *suprise* ->
> l2tp_old_session_deleted_hook(), which of course is
> ppp_unix_session_deleted().
> Or as gdb backtrace:
> 
> (gdb) bt
> #0  ppp_unix_session_deleted (session=0x8a1d0a0, tunnel_id=51784,
> session_id=62693) at ppp_unix.c:1057
> #1  0x080773a7 in l2tp_statusfile_session_deleted_ind
> (session=0x8a1d0a0, tunnel_id=51784, session_id=62693) at
> l2tp_statusfile.c:477
> #2  0x080775be in l2tp_statusfile_session_up_ind (session=0x8a1d0a0,
> tunnel_id=51784, session_id=62693, peer_tunnel_id=45633,
> peer_session_id=35)
>    at l2tp_statusfile.c:530
> #3  0x0806900b in l2tp_session_up_ind (tunnel=0x8a1ca50,
> session=0x8a1d0a0) at l2tp_session.c:622
> #4  0x0806ab88 in l2tp_session_send_iccn (tun=0x8a1ca50,
> sess=0x8a1d0a0) at l2tp_session.c:1655
> #5  0x0806b50e in l2tp_session_laic_send_iccn (tunnel=0x8a1ca50,
> sess=0x8a1d0a0, arg3=0x0) at l2tp_session.c:2208
> #6  0x0807f39d in usl_fsm_handle_event (fsmi=0x8a1d0c0, event=5,
> arg1=0x8a1ca50, arg2=0x8a1d0a0, arg3=0x0) at usl_fsm.c:50
> #7  0x080686e6 in l2tp_session_handle_event (session=0x8a1d0a0,
> event=5) at l2tp_session.c:473
> #8  0x0806a23c in l2tp_session_handle_msg_icrp (peer=0x8a1ca28,
> tunnel=0x8a1ca50, session_id=62693, avps=0xbfecf5e0) at
> l2tp_session.c:1347
> #9  0x0805c507 in l2tp_tunnel_recv (tunnel=0x8a1ca50, tunnel_id=51784,
> session_id=62693, pkt=0x8a1d448) at l2tp_tunnel.c:2334
> #10 0x08064b7c in l2tp_xprt_deliver_up (xprt=0x8a1cca8, pkt=0x8a1d448)
> at l2tp_transport.c:281
> #11 0x08064e06 in l2tp_xprt_deliver_to_protocol (xprt=0x8a1cca8,
> pkt=0x8a1d448) at l2tp_transport.c:322
> #12 0x080656bf in l2tp_xprt_recv (xprt=0x8a1cca8, pkt=0x8a1d448) at
> l2tp_transport.c:505
> #13 0x08056ce5 in l2tp_net_recv_core (fd=14, from=0x0, msg=0xbfecf850,
> recv_len=28, ipi=0x0) at l2tp_network.c:371
> #14 0x08057473 in l2tp_net_recv (fd=14, arg=0x8a1ca50) at l2tp_network.c:546
> #15 0x0807d670 in usl_fd_poll () at usl_fd.c:266
> #16 0x0807e340 in usl_main_loop () at usl_signal.c:216
> #17 0x0804d978 in main (argc=10, argv=0xbfecfcb4) at l2tp_main.c:205
> 
> ppp_unix_session_deleted() clears the ppp context, thus openl2tpd
> thinks there is no longer a pppd running on the session.
> 
> Regards
> Andreas
> 
> 
> On Fri, May 22, 2009 at 7:30 PM, Andreas Schultz <aschultz@...> wrote:
>> Hi,
>>
>> It seems that a tunnel shutdown caused by a lost connection (i pulled
>> the network cable on the client) does not terminate the pppd daemon on
>> top of the tunnel.
>> After the connection comes back, openl2tpd will start a new pppd
>> instance which creates a new ppp interface. This effectivly leads to
>> two active ppp interfaces, both with the same IP and remote peer,
>> rendering the connection useless.
>>
>> kernel 2.6.27.21, openl2tp 1.6
>>
>> Regards
>> Andreas
> 
> [...]
> 
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
> _______________________________________________
> Openl2tp-users mailing list
> Openl2tp-users@...
> https://lists.sourceforge.net/lists/listinfo/openl2tp-users
> 


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

Didier Gaudin wrote:
> Hello,
> i have made somme test with l2tpconfig and a little programme, i see that the memory used increases after many rpc calls.
> i user openl2tp-1.6

Interesting. We aren't aware of memory leaks in openl2tpd's rpc code.
Will investigate.

Thanks for the report.

/james

> 
> 
> example with the l2tpconfig :
> start l2tpconfig  :
> VmPeak:     4056 kB
> VmSize:     4052 kB
> VmLck:         0 kB
> VmHWM:      1268 kB
> VmRSS:      1268 kB
> VmData:      292 kB
> VmStk:        84 kB
> VmExe:       128 kB
> VmLib:      1724 kB
> VmPTE:        16 kB
> 
> 
> now 
> "tunnel list" 20 times
> 
> after:
> VmPeak:     4056 kB
> VmSize:     4056 kB
> VmLck:         0 kB
> VmHWM:      1344 kB
> VmRSS:      1344 kB
> VmData:      296 kB
> VmStk:        84 kB
> VmExe:       128 kB
> VmLib:      1724 kB
> VmPTE:        16 kB
> Threads:        1
> 
> 
> 
> 
> now i run the test with a little program inspired by l2tpconfig :
> 
> test.c:   ( gcc test.c l2tp_rpc_client.o l2tp_rpc_xdr.o -o test)
> #include "stdio.h"
> #include  <rpc/rpc.h>
> #include "l2tp_rpc.h"
> #include <unistd.h>
> 
> void boucle()
> {
>         struct l2tp_api_tunnel_list_msg_data clnt_res;
>         int result;
> 
>         int id;
>         CLIENT *cl;
> 
> 
>         //connection RPC
> 
>         cl = clnt_create("localhost", L2TP_PROG, L2TP_VERSION, "tcp");
>         if (cl != NULL)
>         {
>                 memset(&clnt_res, 0, sizeof(clnt_res));
>                 result = l2tp_tunnel_list_1(&clnt_res, cl);
>                 clnt_destroy(cl);
> 
>         }
> 
> }
> 
> 
> int main()
> {
> int i;
>  sleep(30);  // to have time to see /proc/PID/status
>  printf("Start\n");
>  for (i=0;i<20;i++)
>  {
>         boucle();
>  }
>  printf("End\n");
>  sleep(100);  // to have time to see /proc/PID/status
>  return 0;
> }
> 
> 
> 
> at start time
> VmPeak:     1464 kB                                      
> VmSize:     1448 kB                                      
> VmLck:         0 kB                                      
> VmHWM:       268 kB                                      
> VmRSS:       268 kB                                      
> VmData:       20 kB                                      
> VmStk:        84 kB                                      
> VmExe:        52 kB                                      
> VmLib:      1268 kB                                      
> VmPTE:        12 kB                                      
> 
> at the end:
> VmPeak:     1640 kB
> VmSize:     1624 kB
> VmLck:         0 kB
> VmHWM:       580 kB
> VmRSS:       576 kB
> VmData:      156 kB
> VmStk:        84 kB
> VmExe:        52 kB
> VmLib:      1300 kB
> VmPTE:        12 kB
> 
> 
> 
> 
> 
> is it normal, or i do something wrong ?
> 
> 
> Didier Gaudin.

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

Jijo J wrote:
> 
> The OS is opensuse with kernal version 2.6.22.5-31-default
>
> What is the right version of pppol2tp to use with this kernal.

The pppol2tp driver was integrated in 2.6.23. If you are using older
kernels, then you will need to use openl2tp-0.19 and build/install the
pppol2tp kernel module yourself.

Download the pppol2tp-kmod package from
http://sourceforge.net/project/downloading.php?group_id=118353&filename=pppol2tp-kmod-0.17.tar.gz&a=71198301

Bear in mind that the out-of-tree kernel module has some issues and
can't make use of core kernel features that were added by us when we
integrated pppol2tp into the mainline kernel. I recommend updating your
system to a more recent kernel and/or distro.

/james

>  
> Thanks
> Jijo
> 
>     Hi,
>      
>     I'm getting the following error.
>      
>     1. On Creating the PPP Session, error "unable to open pppox socket:
>     Protocol not supported"
>     How do i load the ppox socket?
>      
>     2. Executing the command modprobe pppol2tp, error " FATAL: Module
>     pppol2tp not found"
>      
>     Please let me know how to fix this issue.
>      
>     Thanks
>     Jijo
>      
>     OB01225:/etc # openl2tpd -f -d all -D
>     Loading plugin ppp_unix.so, version V0.16
>     Start, trace_flags=ffffffff (debug enabled)
>     OpenL2TP V0.16, (c) Copyright 2004,2005,2006,2007 Katalix Systems Ltd.
>     FUNC: tunl 16079: allocated context using profile 'default'
>     API: tunl 16079: continuing with no kernel support
>     FSM: CCE(16079) event OPEN_REQ in state IDLE
>     AVP: tunl 16079: building SCCRQ message, 9 AVPs
>     PROTO: tunl 16079: sending SCCRQ
>     XPRT: tunl 16079: queuing tx packet, type 1, len 144, ns/nr 0/0
>     XPRT: tunl 16079: update ns to 1
>     XPRT: tunl 16079: adding packet to ackq, type 1, len 144, ns/nr 0/0
>     DATA: TX: tunl 16079/0: send 144 bytes to peer 10.232.3.90, packet
>     ns/nr 0/0 type 1, retry 0
>     FSM: CCE(16079) state change: IDLE --> WAITCTLREPLY
>     FUNC: tunl 16079 created
>     XPRT: RX: tunl 16079/0: len=144 ns/nr=0/1, our ns/nr=1/0, peer ns/nr=0/0
>     XPRT: tunl 16079: peer ns/nr is 0/1
>     XPRT: tunl 16079: pkt 0/0 is acked by nr 1
>     DATA: RX: tunl 16079/0: rcv 144 bytes from peer 10.232.3.90, packet
>     ns/nr 0/1 type 0
>     XPRT: tunl 16079: update nr from 0 to 1
>     AVP: tunl 16079: SCCRP message decode of 124 bytes started
>     AVPDATA: PROTOCOL_VERSION: ver=1 rev=0
>     AVPDATA: FRAMING_CAP: cap=3
>     AVPDATA: BEARER_CAP: cap=3
>     AVPDATA: FIRMWARE_VERSION: revision=16
>     AVPDATA: HOST_NAME: name=OB-SBC2
>     AVPDATA: VENDOR_NAME: name=Katalix Systems Ltd.
>     Linux-2.6.22.5-31-default (i686)
>     AVPDATA: TUNNEL_ID: id=20033
>     AVPDATA: RX_WINDOW_SIZE: size=10
>     PROTO: tunl 16079: SCCRP received from peer 20033
>     FSM: CCE(16079) event SCCRP_ACCEPT in state WAITCTLREPLY
>     AVP: tunl 16079: building SCCCN message, 1 AVPs
>     PROTO: tunl 16079: sending SCCCN to peer 20033
>     XPRT: tunl 16079: queuing tx packet, type 3, len 20, ns/nr 1/1
>     XPRT: tunl 16079: update ns to 2
>     XPRT: tunl 16079: adding packet to ackq, type 3, len 20, ns/nr 1/1
>     DATA: TX: tunl 16079/0: send 20 bytes to peer 10.232.3.90, packet
>     ns/nr 1/1 type 3, retry 0
>     FUNC: tunl 16079 up
>     FSM: CCE(16079) state change: WAITCTLREPLY --> ESTABLISHED
>     XPRT: RX: tunl 16079/0: len=12 ns/nr=1/2, our ns/nr=2/1, peer ns/nr=0/1
>     XPRT: tunl 16079: zlb ack received: ns/nr=1/2
>     XPRT: tunl 16079: peer ns/nr is 1/2
>     XPRT: tunl 16079: pkt 1/1 is acked by nr 2
>     XPRT: tunl 16079: send zlb ack, ns/nr=2/1
>     AVP: tunl 16079: building HELLO message, 1 AVPs
>     PROTO: tunl 16079: sending HELLO
>     XPRT: tunl 16079: queuing tx packet, type 6, len 20, ns/nr 2/1
>     XPRT: tunl 16079: update ns to 3
>     XPRT: tunl 16079: adding packet to ackq, type 6, len 20, ns/nr 2/1
>     DATA: TX: tunl 16079/0: send 20 bytes to peer 10.232.3.90, packet
>     ns/nr 2/1 type 6, retry 0
>     XPRT: RX: tunl 16079/0: len=12 ns/nr=1/3, our ns/nr=3/1, peer ns/nr=1/2
>     XPRT: tunl 16079: zlb ack received: ns/nr=1/3
>     XPRT: tunl 16079: peer ns/nr is 1/3
>     XPRT: tunl 16079: pkt 2/1 is acked by nr 3
>     FSM: LAIC(16079/29816) event INCALL_IND in state IDLE
>     FSM: LAIC(16079/29816) state change: IDLE --> WAITTUNNEL
>     16079/29816: creating UNIX pppd context
>     FSM: LAIC(16079/29816) event TUNNEL_OPEN_IND in state WAITTUNNEL
>     AVP: tunl 16079: building ICRQ message, 4 AVPs
>     PROTO: tunl 16079/29816: sending ICRQ to peer 20033/0
>     XPRT: tunl 16079: queuing tx packet, type 10, len 48, ns/nr 3/1
>     XPRT: tunl 16079: update ns to 4
>     XPRT: tunl 16079: adding packet to ackq, type 10, len 48, ns/nr 3/1
>     DATA: TX: tunl 16079/0: send 48 bytes to peer 10.232.3.90, packet
>     ns/nr 3/1 type 10, retry 0
>     FSM: LAIC(16079/29816) state change: WAITTUNNEL --> WAITREPLY
>     XPRT: RX: tunl 16079/29816: len=28 ns/nr=1/4, our ns/nr=4/1, peer
>     ns/nr=1/3
>     XPRT: tunl 16079: peer ns/nr is 1/4
>     XPRT: tunl 16079: pkt 3/1 is acked by nr 4
>     DATA: RX: tunl 16079/29816: rcv 28 bytes from peer 10.232.3.90,
>     packet ns/nr 1/4 type 0
>     XPRT: tunl 16079: update nr from 1 to 2
>     AVP: tunl 16079: ICRP message decode of 8 bytes started
>     AVPDATA: SESSION_ID: id=9799
>     PROTO: tunl 16079/29816: ICRP received from peer 20033
>     FSM: LAIC(16079/29816) event ICRP_ACCEPT in state WAITREPLY
>     AVP: tunl 16079: building ICCN message, 3 AVPs
>     PROTO: tunl 16079/29816: sending ICCN to peer 20033/9799
>     XPRT: tunl 16079: queuing tx packet, type 12, len 40, ns/nr 4/2
>     XPRT: tunl 16079: update ns to 5
>     XPRT: tunl 16079: adding packet to ackq, type 12, len 40, ns/nr 4/2
>     DATA: TX: tunl 16079/9799: send 40 bytes to peer 10.232.3.90, packet
>     ns/nr 4/2 type 12, retry 0
>     16079/29816: starting UNIX pppd
>     sess 16079/29816: spawned pppd pid=5506
>     FSM: LAIC(16079/29816) state change: WAITREPLY --> ESTABLISHED
>     sess 16079/29816: unable to open pppox socket: Protocol not supported
>     FSM: LAIC(16079/29816) event CLOSE_REQ in state ESTABLISHED
>     AVP: tunl 16079: building CDN message, 3 AVPs
>     PROTO: tunl 16079/29816: sending CDN to peer 20033/9799
>     XPRT: tunl 16079: queuing tx packet, type 14, len 36, ns/nr 5/2
>     XPRT: tunl 16079: update ns to 6
>     XPRT: tunl 16079: adding packet to ackq, type 14, len 36, ns/nr 5/2
>     DATA: TX: tunl 16079/9799: send 36 bytes to peer 10.232.3.90, packet
>     ns/nr 5/2 type 14, retry 0
>     16079/29816: stopping unix pppd pid 5506
>     16079/29816: cleaning UNIX pppd context
>     FSM: LAIC(16079/29816) state change: ESTABLISHED --> IDLE
>     XPRT: RX: tunl 16079/0: len=12 ns/nr=2/6, our ns/nr=6/2, peer ns/nr=1/4
>     XPRT: tunl 16079: zlb ack received: ns/nr=2/6
>     XPRT: tunl 16079: peer ns/nr is 2/6
>     XPRT: tunl 16079: pkt 4/2 is acked by nr 6
>     XPRT: tunl 16079: pkt 5/2 is acked by nr 6
>     XPRT: RX: tunl 16079/0: len=20 ns/nr=2/6, our ns/nr=6/2, peer ns/nr=2/6
>     XPRT: tunl 16079: peer ns/nr is 2/6
>     DATA: RX: tunl 16079/0: rcv 20 bytes from peer 10.232.3.90, packet
>     ns/nr 2/6 type 0
>     XPRT: tunl 16079: update nr from 2 to 3
>     AVP: tunl 16079: HELLO message decode of 0 bytes started
>     PROTO: tunl 16079: HELLO received from peer 20033
>     XPRT: tunl 16079: send zlb ack, ns/nr=6/3

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

Thanks,
I don't find a correct version of ppol2tp for my kernel
version(2.6.22.5-31). Do you know its available ? or I have to build it??

I have downloaded the version pppol2tp-kmod-0.17-2.6.22.1_32.fc6 but didn't
help. Is it possible to load the ppol2tp module of this version to my kernel
version?

regards
Jijo




On Fri, May 1, 2009 at 5:35 AM, James Chapman <jchapman@...> wrote:

> Jijo J wrote:
> >
> > The OS is opensuse with kernal version 2.6.22.5-31-default
> >
> > What is the right version of pppol2tp to use with this kernal.
>
> The pppol2tp driver was integrated in 2.6.23. If you are using older
> kernels, then you will need to use openl2tp-0.19 and build/install the
> pppol2tp kernel module yourself.
>
> Download the pppol2tp-kmod package from
>
> http://sourceforge.net/project/downloading.php?group_id=118353&filename=pppol2tp-kmod-0.17.tar.gz&a=71198301
>
> Bear in mind that the out-of-tree kernel module has some issues and
> can't make use of core kernel features that were added by us when we
> integrated pppol2tp into the mainline kernel. I recommend updating your
> system to a more recent kernel and/or distro.
>
> /james
>
> >
> > Thanks
> > Jijo
> >
> >     Hi,
> >
> >     I'm getting the following error.
> >
> >     1. On Creating the PPP Session, error "unable to open pppox socket:
> >     Protocol not supported"
> >     How do i load the ppox socket?
> >
> >     2. Executing the command modprobe pppol2tp, error " FATAL: Module
> >     pppol2tp not found"
> >
> >     Please let me know how to fix this issue.
> >
> >     Thanks
> >     Jijo
> >
> >     OB01225:/etc # openl2tpd -f -d all -D
> >     Loading plugin ppp_unix.so, version V0.16
> >     Start, trace_flags=ffffffff (debug enabled)
> >     OpenL2TP V0.16, (c) Copyright 2004,2005,2006,2007 Katalix Systems
> Ltd.
> >     FUNC: tunl 16079: allocated context using profile 'default'
> >     API: tunl 16079: continuing with no kernel support
> >     FSM: CCE(16079) event OPEN_REQ in state IDLE
> >     AVP: tunl 16079: building SCCRQ message, 9 AVPs
> >     PROTO: tunl 16079: sending SCCRQ
> >     XPRT: tunl 16079: queuing tx packet, type 1, len 144, ns/nr 0/0
> >     XPRT: tunl 16079: update ns to 1
> >     XPRT: tunl 16079: adding packet to ackq, type 1, len 144, ns/nr 0/0
> >     DATA: TX: tunl 16079/0: send 144 bytes to peer 10.232.3.90, packet
> >     ns/nr 0/0 type 1, retry 0
> >     FSM: CCE(16079) state change: IDLE --> WAITCTLREPLY
> >     FUNC: tunl 16079 created
> >     XPRT: RX: tunl 16079/0: len=144 ns/nr=0/1, our ns/nr=1/0, peer
> ns/nr=0/0
> >     XPRT: tunl 16079: peer ns/nr is 0/1
> >     XPRT: tunl 16079: pkt 0/0 is acked by nr 1
> >     DATA: RX: tunl 16079/0: rcv 144 bytes from peer 10.232.3.90, packet
> >     ns/nr 0/1 type 0
> >     XPRT: tunl 16079: update nr from 0 to 1
> >     AVP: tunl 16079: SCCRP message decode of 124 bytes started
> >     AVPDATA: PROTOCOL_VERSION: ver=1 rev=0
> >     AVPDATA: FRAMING_CAP: cap=3
> >     AVPDATA: BEARER_CAP: cap=3
> >     AVPDATA: FIRMWARE_VERSION: revision=16
> >     AVPDATA: HOST_NAME: name=OB-SBC2
> >     AVPDATA: VENDOR_NAME: name=Katalix Systems Ltd.
> >     Linux-2.6.22.5-31-default (i686)
> >     AVPDATA: TUNNEL_ID: id=20033
> >     AVPDATA: RX_WINDOW_SIZE: size=10
> >     PROTO: tunl 16079: SCCRP received from peer 20033
> >     FSM: CCE(16079) event SCCRP_ACCEPT in state WAITCTLREPLY
> >     AVP: tunl 16079: building SCCCN message, 1 AVPs
> >     PROTO: tunl 16079: sending SCCCN to peer 20033
> >     XPRT: tunl 16079: queuing tx packet, type 3, len 20, ns/nr 1/1
> >     XPRT: tunl 16079: update ns to 2
> >     XPRT: tunl 16079: adding packet to ackq, type 3, len 20, ns/nr 1/1
> >     DATA: TX: tunl 16079/0: send 20 bytes to peer 10.232.3.90, packet
> >     ns/nr 1/1 type 3, retry 0
> >     FUNC: tunl 16079 up
> >     FSM: CCE(16079) state change: WAITCTLREPLY --> ESTABLISHED
> >     XPRT: RX: tunl 16079/0: len=12 ns/nr=1/2, our ns/nr=2/1, peer
> ns/nr=0/1
> >     XPRT: tunl 16079: zlb ack received: ns/nr=1/2
> >     XPRT: tunl 16079: peer ns/nr is 1/2
> >     XPRT: tunl 16079: pkt 1/1 is acked by nr 2
> >     XPRT: tunl 16079: send zlb ack, ns/nr=2/1
> >     AVP: tunl 16079: building HELLO message, 1 AVPs
> >     PROTO: tunl 16079: sending HELLO
> >     XPRT: tunl 16079: queuing tx packet, type 6, len 20, ns/nr 2/1
> >     XPRT: tunl 16079: update ns to 3
> >     XPRT: tunl 16079: adding packet to ackq, type 6, len 20, ns/nr 2/1
> >     DATA: TX: tunl 16079/0: send 20 bytes to peer 10.232.3.90, packet
> >     ns/nr 2/1 type 6, retry 0
> >     XPRT: RX: tunl 16079/0: len=12 ns/nr=1/3, our ns/nr=3/1, peer
> ns/nr=1/2
> >     XPRT: tunl 16079: zlb ack received: ns/nr=1/3
> >     XPRT: tunl 16079: peer ns/nr is 1/3
> >     XPRT: tunl 16079: pkt 2/1 is acked by nr 3
> >     FSM: LAIC(16079/29816) event INCALL_IND in state IDLE
> >     FSM: LAIC(16079/29816) state change: IDLE --> WAITTUNNEL
> >     16079/29816: creating UNIX pppd context
> >     FSM: LAIC(16079/29816) event TUNNEL_OPEN_IND in state WAITTUNNEL
> >     AVP: tunl 16079: building ICRQ message, 4 AVPs
> >     PROTO: tunl 16079/29816: sending ICRQ to peer 20033/0
> >     XPRT: tunl 16079: queuing tx packet, type 10, len 48, ns/nr 3/1
> >     XPRT: tunl 16079: update ns to 4
> >     XPRT: tunl 16079: adding packet to ackq, type 10, len 48, ns/nr 3/1
> >     DATA: TX: tunl 16079/0: send 48 bytes to peer 10.232.3.90, packet
> >     ns/nr 3/1 type 10, retry 0
> >     FSM: LAIC(16079/29816) state change: WAITTUNNEL --> WAITREPLY
> >     XPRT: RX: tunl 16079/29816: len=28 ns/nr=1/4, our ns/nr=4/1, peer
> >     ns/nr=1/3
> >     XPRT: tunl 16079: peer ns/nr is 1/4
> >     XPRT: tunl 16079: pkt 3/1 is acked by nr 4
> >     DATA: RX: tunl 16079/29816: rcv 28 bytes from peer 10.232.3.90,
> >     packet ns/nr 1/4 type 0
> >     XPRT: tunl 16079: update nr from 1 to 2
> >     AVP: tunl 16079: ICRP message decode of 8 bytes started
> >     AVPDATA: SESSION_ID: id=9799
> >     PROTO: tunl 16079/29816: ICRP received from peer 20033
> >     FSM: LAIC(16079/29816) event ICRP_ACCEPT in state WAITREPLY
> >     AVP: tunl 16079: building ICCN message, 3 AVPs
> >     PROTO: tunl 16079/29816: sending ICCN to peer 20033/9799
> >     XPRT: tunl 16079: queuing tx packet, type 12, len 40, ns/nr 4/2
> >     XPRT: tunl 16079: update ns to 5
> >     XPRT: tunl 16079: adding packet to ackq, type 12, len 40, ns/nr 4/2
> >     DATA: TX: tunl 16079/9799: send 40 bytes to peer 10.232.3.90, packet
> >     ns/nr 4/2 type 12, retry 0
> >     16079/29816: starting UNIX pppd
> >     sess 16079/29816: spawned pppd pid=5506
> >     FSM: LAIC(16079/29816) state change: WAITREPLY --> ESTABLISHED
> >     sess 16079/29816: unable to open pppox socket: Protocol not supported
> >     FSM: LAIC(16079/29816) event CLOSE_REQ in state ESTABLISHED
> >     AVP: tunl 16079: building CDN message, 3 AVPs
> >     PROTO: tunl 16079/29816: sending CDN to peer 20033/9799
> >     XPRT: tunl 16079: queuing tx packet, type 14, len 36, ns/nr 5/2
> >     XPRT: tunl 16079: update ns to 6
> >     XPRT: tunl 16079: adding packet to ackq, type 14, len 36, ns/nr 5/2
> >     DATA: TX: tunl 16079/9799: send 36 bytes to peer 10.232.3.90, packet
> >     ns/nr 5/2 type 14, retry 0
> >     16079/29816: stopping unix pppd pid 5506
> >     16079/29816: cleaning UNIX pppd context
> >     FSM: LAIC(16079/29816) state change: ESTABLISHED --> IDLE
> >     XPRT: RX: tunl 16079/0: len=12 ns/nr=2/6, our ns/nr=6/2, peer
> ns/nr=1/4
> >     XPRT: tunl 16079: zlb ack received: ns/nr=2/6
> >     XPRT: tunl 16079: peer ns/nr is 2/6
> >     XPRT: tunl 16079: pkt 4/2 is acked by nr 6
> >     XPRT: tunl 16079: pkt 5/2 is acked by nr 6
> >     XPRT: RX: tunl 16079/0: len=20 ns/nr=2/6, our ns/nr=6/2, peer
> ns/nr=2/6
> >     XPRT: tunl 16079: peer ns/nr is 2/6
> >     DATA: RX: tunl 16079/0: rcv 20 bytes from peer 10.232.3.90, packet
> >     ns/nr 2/6 type 0
> >     XPRT: tunl 16079: update nr from 2 to 3
> >     AVP: tunl 16079: HELLO message decode of 0 bytes started
> >     PROTO: tunl 16079: HELLO received from peer 20033
> >     XPRT: tunl 16079: send zlb ack, ns/nr=6/3
>
> --
> James Chapman
> Katalix Systems Ltd
> http://www.katalix.com
> Catalysts for your Embedded Linux software development
>
>