[SOLVED] suddenly no more l2tpd connection are allowed, but ipsec tunnel is still up
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Fedora, OpenSuse, Ubuntu, Mint and Debian
Posts: 22
Rep:
suddenly no more l2tpd connection are allowed, but ipsec tunnel is still up
Hello,
i cannot connect from winxp l2tp-client to l2tpoveripsec in linux.
the ipsec tunnel is established!
my log says, that the client is unauthorized, although he has
the right username and password. in addition, if it is not the correct
password, i get the same message.
I have followed steps from jacco.
Logs of xl2tpd says :-
xl2tpd[6828]: Listening on IP address 0.0.0.0, port 1701
xl2tpd[6828]: handle_avps: no handler for atribute 5 (Tie Breaker).
xl2tpd[6828]: control_finish: Denied connection to unauthorized peer 192.168.151.138
xl2tpd[6828]: Connection 10 closed to 192.168.151.138, port 1701 (No Authorization)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.