Can't access internet after connecting to L2TP IPsec VPN
I have configured a L2TP VPN on Ubuntu server 11.04, and I can connect to it with a Mac client.
But after connecting successfully to this L2TP VPN, my Mac cannot access the internet. To access the internet, I have to disconnect from the VPN. My local IP address on Mac is 192.168.1.105, after connecting to VPN, I use this IP: 10.1.2.2.
How can I fix this?
vpn ipsec
add a comment |
I have configured a L2TP VPN on Ubuntu server 11.04, and I can connect to it with a Mac client.
But after connecting successfully to this L2TP VPN, my Mac cannot access the internet. To access the internet, I have to disconnect from the VPN. My local IP address on Mac is 192.168.1.105, after connecting to VPN, I use this IP: 10.1.2.2.
How can I fix this?
vpn ipsec
add a comment |
I have configured a L2TP VPN on Ubuntu server 11.04, and I can connect to it with a Mac client.
But after connecting successfully to this L2TP VPN, my Mac cannot access the internet. To access the internet, I have to disconnect from the VPN. My local IP address on Mac is 192.168.1.105, after connecting to VPN, I use this IP: 10.1.2.2.
How can I fix this?
vpn ipsec
I have configured a L2TP VPN on Ubuntu server 11.04, and I can connect to it with a Mac client.
But after connecting successfully to this L2TP VPN, my Mac cannot access the internet. To access the internet, I have to disconnect from the VPN. My local IP address on Mac is 192.168.1.105, after connecting to VPN, I use this IP: 10.1.2.2.
How can I fix this?
vpn ipsec
vpn ipsec
edited Jan 14 '12 at 8:18
Mat
39.3k8120127
39.3k8120127
asked Jan 13 '12 at 17:34
IkbearIkbear
10613
10613
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
You have 2 possibilities here. I can tell them to you, but you will have to find the specific settings for each one. I don't have mac at hand right now:
On the mac, when you are connected to the VPN you should also have your old IP (192..). On the VPN settings window there should be an option for using the Internet over the VPN or over the default gateway. The problem is that you gateway is changed from 192... to the VPN pear 10... This solution will let you navigate on the Internet over the 192 network and access the VPN stuff over 10 network.
On the VPN server, you could allow traffic forwarding (Internet access) from connected clients. This solution will allow the mac to navigate on the Internet over the VPN, the 10 network.
Hope this helps, maybe someone can give more specific answer with configuration examples.
add a comment |
The Problem is that your VPN-CLient sets the default route to the VPN-connection.
In Windows you can address this issue by unchecking "Use remote network as default gateway" in "Advanced Settings for IPv4".
KDE-Network-Manager works somewhat similar.
Open the Connection, Tab IPv4 Address, switch from "Basic" Settings to "Routes" and check "Use only for Ressources of this Connection".
In MacOS there should be something similar. The point is to tell the VPN-Client to not redirect all traffic via the tunnel, only the traffic that has the remote tunnel end as destination.
add a comment |
I stumbled upon this thread, and I know its old. However, @itconlor's answer saved my day. I was so excited to have my connection established with l2tp, I failed to verify external traffic. I am using Mint Linux 19. The network-Manager hasn't changed much. Thank you!
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f29047%2fcant-access-internet-after-connecting-to-l2tp-ipsec-vpn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You have 2 possibilities here. I can tell them to you, but you will have to find the specific settings for each one. I don't have mac at hand right now:
On the mac, when you are connected to the VPN you should also have your old IP (192..). On the VPN settings window there should be an option for using the Internet over the VPN or over the default gateway. The problem is that you gateway is changed from 192... to the VPN pear 10... This solution will let you navigate on the Internet over the 192 network and access the VPN stuff over 10 network.
On the VPN server, you could allow traffic forwarding (Internet access) from connected clients. This solution will allow the mac to navigate on the Internet over the VPN, the 10 network.
Hope this helps, maybe someone can give more specific answer with configuration examples.
add a comment |
You have 2 possibilities here. I can tell them to you, but you will have to find the specific settings for each one. I don't have mac at hand right now:
On the mac, when you are connected to the VPN you should also have your old IP (192..). On the VPN settings window there should be an option for using the Internet over the VPN or over the default gateway. The problem is that you gateway is changed from 192... to the VPN pear 10... This solution will let you navigate on the Internet over the 192 network and access the VPN stuff over 10 network.
On the VPN server, you could allow traffic forwarding (Internet access) from connected clients. This solution will allow the mac to navigate on the Internet over the VPN, the 10 network.
Hope this helps, maybe someone can give more specific answer with configuration examples.
add a comment |
You have 2 possibilities here. I can tell them to you, but you will have to find the specific settings for each one. I don't have mac at hand right now:
On the mac, when you are connected to the VPN you should also have your old IP (192..). On the VPN settings window there should be an option for using the Internet over the VPN or over the default gateway. The problem is that you gateway is changed from 192... to the VPN pear 10... This solution will let you navigate on the Internet over the 192 network and access the VPN stuff over 10 network.
On the VPN server, you could allow traffic forwarding (Internet access) from connected clients. This solution will allow the mac to navigate on the Internet over the VPN, the 10 network.
Hope this helps, maybe someone can give more specific answer with configuration examples.
You have 2 possibilities here. I can tell them to you, but you will have to find the specific settings for each one. I don't have mac at hand right now:
On the mac, when you are connected to the VPN you should also have your old IP (192..). On the VPN settings window there should be an option for using the Internet over the VPN or over the default gateway. The problem is that you gateway is changed from 192... to the VPN pear 10... This solution will let you navigate on the Internet over the 192 network and access the VPN stuff over 10 network.
On the VPN server, you could allow traffic forwarding (Internet access) from connected clients. This solution will allow the mac to navigate on the Internet over the VPN, the 10 network.
Hope this helps, maybe someone can give more specific answer with configuration examples.
answered Jan 14 '12 at 15:26
Patkos CsabaPatkos Csaba
2,05211315
2,05211315
add a comment |
add a comment |
The Problem is that your VPN-CLient sets the default route to the VPN-connection.
In Windows you can address this issue by unchecking "Use remote network as default gateway" in "Advanced Settings for IPv4".
KDE-Network-Manager works somewhat similar.
Open the Connection, Tab IPv4 Address, switch from "Basic" Settings to "Routes" and check "Use only for Ressources of this Connection".
In MacOS there should be something similar. The point is to tell the VPN-Client to not redirect all traffic via the tunnel, only the traffic that has the remote tunnel end as destination.
add a comment |
The Problem is that your VPN-CLient sets the default route to the VPN-connection.
In Windows you can address this issue by unchecking "Use remote network as default gateway" in "Advanced Settings for IPv4".
KDE-Network-Manager works somewhat similar.
Open the Connection, Tab IPv4 Address, switch from "Basic" Settings to "Routes" and check "Use only for Ressources of this Connection".
In MacOS there should be something similar. The point is to tell the VPN-Client to not redirect all traffic via the tunnel, only the traffic that has the remote tunnel end as destination.
add a comment |
The Problem is that your VPN-CLient sets the default route to the VPN-connection.
In Windows you can address this issue by unchecking "Use remote network as default gateway" in "Advanced Settings for IPv4".
KDE-Network-Manager works somewhat similar.
Open the Connection, Tab IPv4 Address, switch from "Basic" Settings to "Routes" and check "Use only for Ressources of this Connection".
In MacOS there should be something similar. The point is to tell the VPN-Client to not redirect all traffic via the tunnel, only the traffic that has the remote tunnel end as destination.
The Problem is that your VPN-CLient sets the default route to the VPN-connection.
In Windows you can address this issue by unchecking "Use remote network as default gateway" in "Advanced Settings for IPv4".
KDE-Network-Manager works somewhat similar.
Open the Connection, Tab IPv4 Address, switch from "Basic" Settings to "Routes" and check "Use only for Ressources of this Connection".
In MacOS there should be something similar. The point is to tell the VPN-Client to not redirect all traffic via the tunnel, only the traffic that has the remote tunnel end as destination.
edited Mar 26 '13 at 13:51
nozimica
709519
709519
answered Mar 26 '13 at 12:12
itconloritconlor
10317
10317
add a comment |
add a comment |
I stumbled upon this thread, and I know its old. However, @itconlor's answer saved my day. I was so excited to have my connection established with l2tp, I failed to verify external traffic. I am using Mint Linux 19. The network-Manager hasn't changed much. Thank you!
New contributor
add a comment |
I stumbled upon this thread, and I know its old. However, @itconlor's answer saved my day. I was so excited to have my connection established with l2tp, I failed to verify external traffic. I am using Mint Linux 19. The network-Manager hasn't changed much. Thank you!
New contributor
add a comment |
I stumbled upon this thread, and I know its old. However, @itconlor's answer saved my day. I was so excited to have my connection established with l2tp, I failed to verify external traffic. I am using Mint Linux 19. The network-Manager hasn't changed much. Thank you!
New contributor
I stumbled upon this thread, and I know its old. However, @itconlor's answer saved my day. I was so excited to have my connection established with l2tp, I failed to verify external traffic. I am using Mint Linux 19. The network-Manager hasn't changed much. Thank you!
New contributor
New contributor
answered 5 mins ago
jasonmarquettejasonmarquette
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f29047%2fcant-access-internet-after-connecting-to-l2tp-ipsec-vpn%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