Ubuntu 18.04 VPN L2TP with PSK
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I tried to configure a vpn-connection having an username, a password and a pre-shared-key (psk) from my admin at office.
Over many hours I tried several possibilities and methods (openvpn, openswan, networkmanager-l2tp-gnome, xl2tpd), but I can't establish a connection to my office.
But the given parameters are still working, because I tried using Win7 and on my Android-Phone.
Why is it so heavy to configure such a simple thing like a vpn, where I've only to put in 3 parameters? On my phone, I put the parms in and it works fine.
Please help me to find out the right way to configure the vpn.
Because I want use Linux!!!
Many thanks,
GueBr
vpn
asked Sep 5 '18 at 7:17
GueBrGueBr
612
add a comment |
I tried to configure a vpn-connection having an username, a password and a pre-shared-key (psk) from my admin at office.
Over many hours I tried several possibilities and methods (openvpn, openswan, networkmanager-l2tp-gnome, xl2tpd), but I can't establish a connection to my office.
But the given parameters are still working, because I tried using Win7 and on my Android-Phone.
Why is it so heavy to configure such a simple thing like a vpn, where I've only to put in 3 parameters? On my phone, I put the parms in and it works fine.
Please help me to find out the right way to configure the vpn.
Because I want use Linux!!!
Many thanks,
GueBr
vpn
asked Sep 5 '18 at 7:17
GueBrGueBr
612
add a comment |
I tried to configure a vpn-connection having an username, a password and a pre-shared-key (psk) from my admin at office.
Over many hours I tried several possibilities and methods (openvpn, openswan, networkmanager-l2tp-gnome, xl2tpd), but I can't establish a connection to my office.
But the given parameters are still working, because I tried using Win7 and on my Android-Phone.
Why is it so heavy to configure such a simple thing like a vpn, where I've only to put in 3 parameters? On my phone, I put the parms in and it works fine.
Please help me to find out the right way to configure the vpn.
Because I want use Linux!!!
Many thanks,
GueBr
vpn
asked Sep 5 '18 at 7:17
GueBrGueBr
612
I tried to configure a vpn-connection having an username, a password and a pre-shared-key (psk) from my admin at office.
Over many hours I tried several possibilities and methods (openvpn, openswan, networkmanager-l2tp-gnome, xl2tpd), but I can't establish a connection to my office.
But the given parameters are still working, because I tried using Win7 and on my Android-Phone.
Why is it so heavy to configure such a simple thing like a vpn, where I've only to put in 3 parameters? On my phone, I put the parms in and it works fine.
Please help me to find out the right way to configure the vpn.
Because I want use Linux!!!
Many thanks,
GueBr
vpn
vpn
asked Sep 5 '18 at 7:17
GueBrGueBr
612
asked Sep 5 '18 at 7:17
GueBrGueBr
612
asked Sep 5 '18 at 7:17
GueBrGueBr
612
asked Sep 5 '18 at 7:17
GueBrGueBr
612
asked Sep 5 '18 at 7:17
GueBrGueBr
612
612
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Unfortunately there are many L2TP/IPsec VPN servers out there that are proposing only the IPsec algorithms that were introduced by Microsoft with Windows 2000 Server 18 years ago that are now considered weak or broken.
The L2TP/IPsec client also proposes a set of algorithms. For a connection to happen, the client and server need to have at least one common proposal.
networkmanager-l2tp uses libreswan or strongswan for IPsec support. Linux tends to be more security conscious than other platforms. libreswan and strongswan have dropped the weak algorithms in their default proposals but they still allow weak algorithms if you explicitly specify which weak algorithms you want to use.
But the correct fix is most definitely to configure the L2TP/IPsec server to also propose algorithms that aren't weak.
I would recommend reading the README.md file that comes with the network-manager-l2tp package, you can also find the README.md in the upstream source code here :
- https://github.com/nm-l2tp/network-manager-l2tp/blob/nm-1-2/README.md
In particular have a look at the "Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms" section in that file. It provides details on how to run a ike-scan.sh script that can query the LP2TP/IPsec server for the phase 1 algorithms it uses, it also gives an example on how to specify the most common 3DES, SHA1 and MODP1024 weak algorithms.
Also have a look at the "Issue with not stopping system xl2tpd service" section in that file, you might need stop the system xl2tpd.
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1072252%2fubuntu-18-04-vpn-l2tp-with-psk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Unfortunately there are many L2TP/IPsec VPN servers out there that are proposing only the IPsec algorithms that were introduced by Microsoft with Windows 2000 Server 18 years ago that are now considered weak or broken.
The L2TP/IPsec client also proposes a set of algorithms. For a connection to happen, the client and server need to have at least one common proposal.
networkmanager-l2tp uses libreswan or strongswan for IPsec support. Linux tends to be more security conscious than other platforms. libreswan and strongswan have dropped the weak algorithms in their default proposals but they still allow weak algorithms if you explicitly specify which weak algorithms you want to use.
But the correct fix is most definitely to configure the L2TP/IPsec server to also propose algorithms that aren't weak.
I would recommend reading the README.md file that comes with the network-manager-l2tp package, you can also find the README.md in the upstream source code here :
- https://github.com/nm-l2tp/network-manager-l2tp/blob/nm-1-2/README.md
In particular have a look at the "Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms" section in that file. It provides details on how to run a ike-scan.sh script that can query the LP2TP/IPsec server for the phase 1 algorithms it uses, it also gives an example on how to specify the most common 3DES, SHA1 and MODP1024 weak algorithms.
Also have a look at the "Issue with not stopping system xl2tpd service" section in that file, you might need stop the system xl2tpd.
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
add a comment |
Unfortunately there are many L2TP/IPsec VPN servers out there that are proposing only the IPsec algorithms that were introduced by Microsoft with Windows 2000 Server 18 years ago that are now considered weak or broken.
The L2TP/IPsec client also proposes a set of algorithms. For a connection to happen, the client and server need to have at least one common proposal.
networkmanager-l2tp uses libreswan or strongswan for IPsec support. Linux tends to be more security conscious than other platforms. libreswan and strongswan have dropped the weak algorithms in their default proposals but they still allow weak algorithms if you explicitly specify which weak algorithms you want to use.
But the correct fix is most definitely to configure the L2TP/IPsec server to also propose algorithms that aren't weak.
I would recommend reading the README.md file that comes with the network-manager-l2tp package, you can also find the README.md in the upstream source code here :
- https://github.com/nm-l2tp/network-manager-l2tp/blob/nm-1-2/README.md
In particular have a look at the "Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms" section in that file. It provides details on how to run a ike-scan.sh script that can query the LP2TP/IPsec server for the phase 1 algorithms it uses, it also gives an example on how to specify the most common 3DES, SHA1 and MODP1024 weak algorithms.
Also have a look at the "Issue with not stopping system xl2tpd service" section in that file, you might need stop the system xl2tpd.
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
add a comment |
Unfortunately there are many L2TP/IPsec VPN servers out there that are proposing only the IPsec algorithms that were introduced by Microsoft with Windows 2000 Server 18 years ago that are now considered weak or broken.
The L2TP/IPsec client also proposes a set of algorithms. For a connection to happen, the client and server need to have at least one common proposal.
networkmanager-l2tp uses libreswan or strongswan for IPsec support. Linux tends to be more security conscious than other platforms. libreswan and strongswan have dropped the weak algorithms in their default proposals but they still allow weak algorithms if you explicitly specify which weak algorithms you want to use.
But the correct fix is most definitely to configure the L2TP/IPsec server to also propose algorithms that aren't weak.
I would recommend reading the README.md file that comes with the network-manager-l2tp package, you can also find the README.md in the upstream source code here :
- https://github.com/nm-l2tp/network-manager-l2tp/blob/nm-1-2/README.md
In particular have a look at the "Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms" section in that file. It provides details on how to run a ike-scan.sh script that can query the LP2TP/IPsec server for the phase 1 algorithms it uses, it also gives an example on how to specify the most common 3DES, SHA1 and MODP1024 weak algorithms.
Also have a look at the "Issue with not stopping system xl2tpd service" section in that file, you might need stop the system xl2tpd.
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
Unfortunately there are many L2TP/IPsec VPN servers out there that are proposing only the IPsec algorithms that were introduced by Microsoft with Windows 2000 Server 18 years ago that are now considered weak or broken.
The L2TP/IPsec client also proposes a set of algorithms. For a connection to happen, the client and server need to have at least one common proposal.
networkmanager-l2tp uses libreswan or strongswan for IPsec support. Linux tends to be more security conscious than other platforms. libreswan and strongswan have dropped the weak algorithms in their default proposals but they still allow weak algorithms if you explicitly specify which weak algorithms you want to use.
But the correct fix is most definitely to configure the L2TP/IPsec server to also propose algorithms that aren't weak.
I would recommend reading the README.md file that comes with the network-manager-l2tp package, you can also find the README.md in the upstream source code here :
- https://github.com/nm-l2tp/network-manager-l2tp/blob/nm-1-2/README.md
In particular have a look at the "Issue with VPN servers only proposing IPsec IKEv1 weak legacy algorithms" section in that file. It provides details on how to run a ike-scan.sh script that can query the LP2TP/IPsec server for the phase 1 algorithms it uses, it also gives an example on how to specify the most common 3DES, SHA1 and MODP1024 weak algorithms.
Also have a look at the "Issue with not stopping system xl2tpd service" section in that file, you might need stop the system xl2tpd.
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
answered Sep 7 '18 at 10:30
Douglas KosovicDouglas Kosovic
36114
36114
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1072252%2fubuntu-18-04-vpn-l2tp-with-psk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
