Can't access internet after connecting to L2TP IPsec VPN












1















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?










share|improve this question





























    1















    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?










    share|improve this question



























      1












      1








      1


      1






      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?










      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 14 '12 at 8:18









      Mat

      39.3k8120127




      39.3k8120127










      asked Jan 13 '12 at 17:34









      IkbearIkbear

      10613




      10613






















          3 Answers
          3






          active

          oldest

          votes


















          1














          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:




          1. 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.


          2. 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.






          share|improve this answer































            0














            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.






            share|improve this answer

































              0














              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!





              share








              New contributor




              jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.




















                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
                });


                }
                });














                draft saved

                draft discarded


















                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









                1














                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:




                1. 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.


                2. 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.






                share|improve this answer




























                  1














                  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:




                  1. 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.


                  2. 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.






                  share|improve this answer


























                    1












                    1








                    1







                    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:




                    1. 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.


                    2. 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.






                    share|improve this answer













                    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:




                    1. 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.


                    2. 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.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jan 14 '12 at 15:26









                    Patkos CsabaPatkos Csaba

                    2,05211315




                    2,05211315

























                        0














                        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.






                        share|improve this answer






























                          0














                          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.






                          share|improve this answer




























                            0












                            0








                            0







                            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.






                            share|improve this answer















                            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.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Mar 26 '13 at 13:51









                            nozimica

                            709519




                            709519










                            answered Mar 26 '13 at 12:12









                            itconloritconlor

                            10317




                            10317























                                0














                                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!





                                share








                                New contributor




                                jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.

























                                  0














                                  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!





                                  share








                                  New contributor




                                  jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                  Check out our Code of Conduct.























                                    0












                                    0








                                    0







                                    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!





                                    share








                                    New contributor




                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.










                                    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!






                                    share








                                    New contributor




                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.








                                    share


                                    share






                                    New contributor




                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.









                                    answered 5 mins ago









                                    jasonmarquettejasonmarquette

                                    1




                                    1




                                    New contributor




                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.





                                    New contributor





                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.






                                    jasonmarquette is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.






























                                        draft saved

                                        draft discarded




















































                                        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.




                                        draft saved


                                        draft discarded














                                        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





















































                                        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







                                        Popular posts from this blog

                                        Accessing regular linux commands in Huawei's Dopra Linux

                                        Can't connect RFCOMM socket: Host is down

                                        Kernel panic - not syncing: Fatal Exception in Interrupt