Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 28425 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

xl2tpd is not listen on the system

Behzad Azarmehr

Hi

I recently buy a sophos xg 230. It's OS version is 16.01.1

I configure L2TP service.

- Enable L2TP - checked

  - Define a range

  - define dns

and so on....

but the l2tp is not start correctly.
i try to trouble shoot and I login in advanced shell. i review the log and I see this messages :


XG230_SFOS 16.01.1# tail -f /log/l2tpd.log
xl2tpd[14158]: Listening on IP address 0.0.0.0, port 1701
xl2tpd[14158]: death_handler: Fatal signal 15 received
xl2tpd[14259]: setsockopt recvref[22]: Protocol not available
xl2tpd[14259]: This binary does not support kernel L2TP.
xl2tpd[14259]: xl2tpd version xl2tpd-1.2.4 started on localhost PID:14259
xl2tpd[14259]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc.
xl2tpd[14259]: Forked by Scott Balmos and David Stipp, (C) 2001
xl2tpd[14259]: Inherited by Jeff McAdams, (C) 2002
xl2tpd[14259]: Forked again by Xelerance (www.xelerance.com) (C) 2006
xl2tpd[14259]: Listening on IP address 0.0.0.0, port 1701


and when i use netstat command, i found the xl2tpd is not listen on 1701.

my firewall rule for vpn like this :

how can i solve this problem ?

is it a bug ? how can i fix it ?



This thread was automatically locked due to age.
Parents
  • 0

    Hi Behzad,

    Show us the L2TP dialer settings for each tab from your machine. Check whether IPSec client service is running on your machine by navigating to Start -> Run -> services.msc -> IPsec.

    On XG, login to console and execute: set vpn l2tp authentication ANY

    Make sure the VPN authentication Method is selected in Identity-> Authentication - >VPN->VPN Authentication Method

    L2TP VPN encapsulates the data over IPSec tunnel, whenever the user tries to connect via L2TP VPN, first IPSec tunnel will be established and then the L2TP connection. Show us the IPSec logs if the the issue persists after taking the above steps. Execute in the console:  show vpn IPSec-logs

    Thanks

  • 0 in reply to sachingurung

    I'm having the same issues. I'm behind a router and I've opened all the needed ports, but when I try to connect from outside network ( with a pubblic IP ), I can see IPSec logs but no L2TP logs.

    The same client machine connected directly to the router with a private ip works fine. It seems that it won't estabilish an ipsec tunnel when the requesting machines are using a pubblic IP.

     

    Here's a diagram:

     

     

    Thanks 

Reply
  • 0 in reply to sachingurung

    I'm having the same issues. I'm behind a router and I've opened all the needed ports, but when I try to connect from outside network ( with a pubblic IP ), I can see IPSec logs but no L2TP logs.

    The same client machine connected directly to the router with a private ip works fine. It seems that it won't estabilish an ipsec tunnel when the requesting machines are using a pubblic IP.

     

    Here's a diagram:

     

     

    Thanks 

Children
No Data