IPSEC/L2TP VPN causes resolving name server problem with the latest systemd version on 18.04
After upgrading libnss-sysytemd library to the latest version 237-3ubuntu10.12, IPSEC/L2TP VPN connection is established but I cannot connect to outside of LAN. I found out the route table was not the same as the version 237-3ubuntu10.11. The difference is the order of the ip addresses. On 237-3ubuntu10.12, the order of the remote vpn ip address on route table is normal order but the VPN connection doesn't work well. On 237-3ubuntu10.11, the order is reverse order, then VPN connection works well.
But today, it happens again on the Starbacks WIFI even on the version 237-3ubuntu10.11. The route table is below.
237-3ubuntu10.11 on Starbacks WIFI
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
123.234.345.456 _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
237-3ubuntu10.11 on the mobile network tethering.
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
456.345.234.123. _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
I'm sure it's a bug of systemd. Has anybody reported this bug yet?
I'm using strongswan and xl2tp. It doesn't cause this problem anyway.
18.04 systemd bug-reporting ipsec
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
add a comment |
After upgrading libnss-sysytemd library to the latest version 237-3ubuntu10.12, IPSEC/L2TP VPN connection is established but I cannot connect to outside of LAN. I found out the route table was not the same as the version 237-3ubuntu10.11. The difference is the order of the ip addresses. On 237-3ubuntu10.12, the order of the remote vpn ip address on route table is normal order but the VPN connection doesn't work well. On 237-3ubuntu10.11, the order is reverse order, then VPN connection works well.
But today, it happens again on the Starbacks WIFI even on the version 237-3ubuntu10.11. The route table is below.
237-3ubuntu10.11 on Starbacks WIFI
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
123.234.345.456 _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
237-3ubuntu10.11 on the mobile network tethering.
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
456.345.234.123. _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
I'm sure it's a bug of systemd. Has anybody reported this bug yet?
I'm using strongswan and xl2tp. It doesn't cause this problem anyway.
18.04 systemd bug-reporting ipsec
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
add a comment |
After upgrading libnss-sysytemd library to the latest version 237-3ubuntu10.12, IPSEC/L2TP VPN connection is established but I cannot connect to outside of LAN. I found out the route table was not the same as the version 237-3ubuntu10.11. The difference is the order of the ip addresses. On 237-3ubuntu10.12, the order of the remote vpn ip address on route table is normal order but the VPN connection doesn't work well. On 237-3ubuntu10.11, the order is reverse order, then VPN connection works well.
But today, it happens again on the Starbacks WIFI even on the version 237-3ubuntu10.11. The route table is below.
237-3ubuntu10.11 on Starbacks WIFI
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
123.234.345.456 _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
237-3ubuntu10.11 on the mobile network tethering.
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
456.345.234.123. _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
I'm sure it's a bug of systemd. Has anybody reported this bug yet?
I'm using strongswan and xl2tp. It doesn't cause this problem anyway.
18.04 systemd bug-reporting ipsec
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
After upgrading libnss-sysytemd library to the latest version 237-3ubuntu10.12, IPSEC/L2TP VPN connection is established but I cannot connect to outside of LAN. I found out the route table was not the same as the version 237-3ubuntu10.11. The difference is the order of the ip addresses. On 237-3ubuntu10.12, the order of the remote vpn ip address on route table is normal order but the VPN connection doesn't work well. On 237-3ubuntu10.11, the order is reverse order, then VPN connection works well.
But today, it happens again on the Starbacks WIFI even on the version 237-3ubuntu10.11. The route table is below.
237-3ubuntu10.11 on Starbacks WIFI
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
123.234.345.456 _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
237-3ubuntu10.11 on the mobile network tethering.
Destination Gateway Genmask Flags Metric Ref Use Iface
default 0.0.0.0 0.0.0.0 U 0 0 0 ppp0
default _gateway 0.0.0.0 UG 20600 0 0 wlp58s0
10.27.40.0 0.0.0.0 255.255.248.0 U 600 0 0 wlp58s0
456.345.234.123. _gateway 255.255.255.255 UGH 0 0 0 wlp58s0
192.168.10.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
I'm sure it's a bug of systemd. Has anybody reported this bug yet?
I'm using strongswan and xl2tp. It doesn't cause this problem anyway.
18.04 systemd bug-reporting ipsec
18.04 systemd bug-reporting ipsec
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
edited Feb 21 at 13:19
fx-kirin
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
asked Feb 20 at 0:54
fx-kirinfx-kirin
1429
1429
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The IP address with reversed ordering of the octets has a trailing dot, which indicates it is the significant part of a reverse DNS PTR record. See :
- https://unix.stackexchange.com/questions/145665/
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
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%2f1119691%2fipsec-l2tp-vpn-causes-resolving-name-server-problem-with-the-latest-systemd-vers%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
The IP address with reversed ordering of the octets has a trailing dot, which indicates it is the significant part of a reverse DNS PTR record. See :
- https://unix.stackexchange.com/questions/145665/
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
add a comment |
The IP address with reversed ordering of the octets has a trailing dot, which indicates it is the significant part of a reverse DNS PTR record. See :
- https://unix.stackexchange.com/questions/145665/
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
add a comment |
The IP address with reversed ordering of the octets has a trailing dot, which indicates it is the significant part of a reverse DNS PTR record. See :
- https://unix.stackexchange.com/questions/145665/
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
The IP address with reversed ordering of the octets has a trailing dot, which indicates it is the significant part of a reverse DNS PTR record. See :
- https://unix.stackexchange.com/questions/145665/
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
answered Mar 15 at 2:59
Douglas KosovicDouglas Kosovic
33614
33614
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
add a comment |
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
Yes, it must be reversed order in this case. That's why I think there is a bug because it happens with only the latest 18.04. And I'm afraid your answer is not a answer should be a comment.
– fx-kirin
Mar 15 at 4:11
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%2f1119691%2fipsec-l2tp-vpn-causes-resolving-name-server-problem-with-the-latest-systemd-vers%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
