Public Wifi in Ubuntu 18.04












2















I recently update my Ubuntu version from 16.04 to 18.04 and since that I've not been able to connect to any public WiFi. I' ve tried with several browsers and it didn't work out. I can connect to the login page but after write my credentials (the WiFi is for a library) Firefox show me a message like




"Connection could not be donde with .... Try to review your internet connection or your proxy"




The WiFi was right on my mobile anyway










share|improve this question





























    2















    I recently update my Ubuntu version from 16.04 to 18.04 and since that I've not been able to connect to any public WiFi. I' ve tried with several browsers and it didn't work out. I can connect to the login page but after write my credentials (the WiFi is for a library) Firefox show me a message like




    "Connection could not be donde with .... Try to review your internet connection or your proxy"




    The WiFi was right on my mobile anyway










    share|improve this question



























      2












      2








      2








      I recently update my Ubuntu version from 16.04 to 18.04 and since that I've not been able to connect to any public WiFi. I' ve tried with several browsers and it didn't work out. I can connect to the login page but after write my credentials (the WiFi is for a library) Firefox show me a message like




      "Connection could not be donde with .... Try to review your internet connection or your proxy"




      The WiFi was right on my mobile anyway










      share|improve this question
















      I recently update my Ubuntu version from 16.04 to 18.04 and since that I've not been able to connect to any public WiFi. I' ve tried with several browsers and it didn't work out. I can connect to the login page but after write my credentials (the WiFi is for a library) Firefox show me a message like




      "Connection could not be donde with .... Try to review your internet connection or your proxy"




      The WiFi was right on my mobile anyway







      networking 18.04






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 14 mins ago









      Pablo Bianchi

      2,96021535




      2,96021535










      asked May 11 '18 at 14:27









      Javier CorreaJavier Correa

      112




      112






















          1 Answer
          1






          active

          oldest

          votes


















          1














          I have just experienced same answer. Problem traces back to redirects and security frameworks. If you use Network-manager, here is easiest fix.




          1. Click the NM applet

          2. Choose edit connections

          3. Find the WiFi site where you are having trouble.

          4. Choose the little gear on bottom to open config editor.

          5. Choose tab IPv4 Settings


          6. Find the box "Additional DNS Servers" and type in these Google DNS servers:



            8.8.8.8,8.8.4.4



            Or probably better 1.1.1.1, 1.0.0.1 regarding privacy:



            screenshot



            those are 2 comma separated DNS servers that can be tried when an address is not available from the DNS server provided by login site.



          7. Hit the save button


          After that, the login process works as the site administrator intends.



          I have tested this at McDonalds and in a tire store. It works.



          Why does it work? The login server offers a DNS address for a very limited name server, to get full name lookup, you need access to other name servers. 8.8.8.8 is the google name server, we have it as a "last change" lookup location on almost all of our computers.



          Why is it a problem in the first place? The Ubuntu security framework is trying to protect you from security attacks that put 3rd party DNS servers in the middle of your workflow. Suppose the login server was allowed to do that. Then when you browse "nytimes.com" and give your password, then an attacker may be between you and nytimes, trying to steal your password.



          I think other users here will have better technical explanation, but the manual insertion of trusted DNS servers is a solution that worked for me.






          share|improve this answer

























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


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034941%2fpublic-wifi-in-ubuntu-18-04%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









            1














            I have just experienced same answer. Problem traces back to redirects and security frameworks. If you use Network-manager, here is easiest fix.




            1. Click the NM applet

            2. Choose edit connections

            3. Find the WiFi site where you are having trouble.

            4. Choose the little gear on bottom to open config editor.

            5. Choose tab IPv4 Settings


            6. Find the box "Additional DNS Servers" and type in these Google DNS servers:



              8.8.8.8,8.8.4.4



              Or probably better 1.1.1.1, 1.0.0.1 regarding privacy:



              screenshot



              those are 2 comma separated DNS servers that can be tried when an address is not available from the DNS server provided by login site.



            7. Hit the save button


            After that, the login process works as the site administrator intends.



            I have tested this at McDonalds and in a tire store. It works.



            Why does it work? The login server offers a DNS address for a very limited name server, to get full name lookup, you need access to other name servers. 8.8.8.8 is the google name server, we have it as a "last change" lookup location on almost all of our computers.



            Why is it a problem in the first place? The Ubuntu security framework is trying to protect you from security attacks that put 3rd party DNS servers in the middle of your workflow. Suppose the login server was allowed to do that. Then when you browse "nytimes.com" and give your password, then an attacker may be between you and nytimes, trying to steal your password.



            I think other users here will have better technical explanation, but the manual insertion of trusted DNS servers is a solution that worked for me.






            share|improve this answer






























              1














              I have just experienced same answer. Problem traces back to redirects and security frameworks. If you use Network-manager, here is easiest fix.




              1. Click the NM applet

              2. Choose edit connections

              3. Find the WiFi site where you are having trouble.

              4. Choose the little gear on bottom to open config editor.

              5. Choose tab IPv4 Settings


              6. Find the box "Additional DNS Servers" and type in these Google DNS servers:



                8.8.8.8,8.8.4.4



                Or probably better 1.1.1.1, 1.0.0.1 regarding privacy:



                screenshot



                those are 2 comma separated DNS servers that can be tried when an address is not available from the DNS server provided by login site.



              7. Hit the save button


              After that, the login process works as the site administrator intends.



              I have tested this at McDonalds and in a tire store. It works.



              Why does it work? The login server offers a DNS address for a very limited name server, to get full name lookup, you need access to other name servers. 8.8.8.8 is the google name server, we have it as a "last change" lookup location on almost all of our computers.



              Why is it a problem in the first place? The Ubuntu security framework is trying to protect you from security attacks that put 3rd party DNS servers in the middle of your workflow. Suppose the login server was allowed to do that. Then when you browse "nytimes.com" and give your password, then an attacker may be between you and nytimes, trying to steal your password.



              I think other users here will have better technical explanation, but the manual insertion of trusted DNS servers is a solution that worked for me.






              share|improve this answer




























                1












                1








                1







                I have just experienced same answer. Problem traces back to redirects and security frameworks. If you use Network-manager, here is easiest fix.




                1. Click the NM applet

                2. Choose edit connections

                3. Find the WiFi site where you are having trouble.

                4. Choose the little gear on bottom to open config editor.

                5. Choose tab IPv4 Settings


                6. Find the box "Additional DNS Servers" and type in these Google DNS servers:



                  8.8.8.8,8.8.4.4



                  Or probably better 1.1.1.1, 1.0.0.1 regarding privacy:



                  screenshot



                  those are 2 comma separated DNS servers that can be tried when an address is not available from the DNS server provided by login site.



                7. Hit the save button


                After that, the login process works as the site administrator intends.



                I have tested this at McDonalds and in a tire store. It works.



                Why does it work? The login server offers a DNS address for a very limited name server, to get full name lookup, you need access to other name servers. 8.8.8.8 is the google name server, we have it as a "last change" lookup location on almost all of our computers.



                Why is it a problem in the first place? The Ubuntu security framework is trying to protect you from security attacks that put 3rd party DNS servers in the middle of your workflow. Suppose the login server was allowed to do that. Then when you browse "nytimes.com" and give your password, then an attacker may be between you and nytimes, trying to steal your password.



                I think other users here will have better technical explanation, but the manual insertion of trusted DNS servers is a solution that worked for me.






                share|improve this answer















                I have just experienced same answer. Problem traces back to redirects and security frameworks. If you use Network-manager, here is easiest fix.




                1. Click the NM applet

                2. Choose edit connections

                3. Find the WiFi site where you are having trouble.

                4. Choose the little gear on bottom to open config editor.

                5. Choose tab IPv4 Settings


                6. Find the box "Additional DNS Servers" and type in these Google DNS servers:



                  8.8.8.8,8.8.4.4



                  Or probably better 1.1.1.1, 1.0.0.1 regarding privacy:



                  screenshot



                  those are 2 comma separated DNS servers that can be tried when an address is not available from the DNS server provided by login site.



                7. Hit the save button


                After that, the login process works as the site administrator intends.



                I have tested this at McDonalds and in a tire store. It works.



                Why does it work? The login server offers a DNS address for a very limited name server, to get full name lookup, you need access to other name servers. 8.8.8.8 is the google name server, we have it as a "last change" lookup location on almost all of our computers.



                Why is it a problem in the first place? The Ubuntu security framework is trying to protect you from security attacks that put 3rd party DNS servers in the middle of your workflow. Suppose the login server was allowed to do that. Then when you browse "nytimes.com" and give your password, then an attacker may be between you and nytimes, trying to steal your password.



                I think other users here will have better technical explanation, but the manual insertion of trusted DNS servers is a solution that worked for me.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 6 mins ago









                Pablo Bianchi

                2,96021535




                2,96021535










                answered Oct 17 '18 at 15:23









                pauljohn32pauljohn32

                2,404924




                2,404924






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034941%2fpublic-wifi-in-ubuntu-18-04%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

                    GameSpot

                    日野市

                    Tu-95轟炸機