Ubuntu 16.04 How to use Ethernet captive portals

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I'm running 16.04 still and need to connect via internet to my campus network. However they use a captive portal login that works fine in windows, but Ubuntu doesn't like. Every browser I try gives me an error when the portal is trying to redirect me to itself. Historically I never have been able to get a captive portal to work on Linux - anyone have any ideas?







share|improve this question
























    up vote
    0
    down vote

    favorite












    I'm running 16.04 still and need to connect via internet to my campus network. However they use a captive portal login that works fine in windows, but Ubuntu doesn't like. Every browser I try gives me an error when the portal is trying to redirect me to itself. Historically I never have been able to get a captive portal to work on Linux - anyone have any ideas?







    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm running 16.04 still and need to connect via internet to my campus network. However they use a captive portal login that works fine in windows, but Ubuntu doesn't like. Every browser I try gives me an error when the portal is trying to redirect me to itself. Historically I never have been able to get a captive portal to work on Linux - anyone have any ideas?







      share|improve this question












      I'm running 16.04 still and need to connect via internet to my campus network. However they use a captive portal login that works fine in windows, but Ubuntu doesn't like. Every browser I try gives me an error when the portal is trying to redirect me to itself. Historically I never have been able to get a captive portal to work on Linux - anyone have any ideas?









      share|improve this question











      share|improve this question




      share|improve this question










      asked May 27 at 21:36









      Luke Bordonaro

      111




      111




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          This seems to be a known issue with 16.04 and Linux-unfriendly captive portals, possibly fixed since 17.10 but I'm unsure and can't test it. Meanwhile, if you can't upgrade or try with the latests Ubuntu versions, use the route command in terminal.



          $ sudo route


          You should see something like:



          Kernel IP routing table

          Destination Gateway Genmask Flags Metric Ref Use Iface
          default 10.0.2.2 0.0.0.0 UG 600 0 0 wlan0
          10.0.2.2 * 255.255.248.0 U 600 0 0 wlan0
          link-local * 255.255.0.0 U 1000 0 0 wlan0


          Type the gateway adress in your browser (here: 10.0.2.2), this should get you to the captive portal page. Try with different browsers if necessary.






          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',
            convertImagesToLinks: true,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            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%2f1041005%2fubuntu-16-04-how-to-use-ethernet-captive-portals%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            This seems to be a known issue with 16.04 and Linux-unfriendly captive portals, possibly fixed since 17.10 but I'm unsure and can't test it. Meanwhile, if you can't upgrade or try with the latests Ubuntu versions, use the route command in terminal.



            $ sudo route


            You should see something like:



            Kernel IP routing table

            Destination Gateway Genmask Flags Metric Ref Use Iface
            default 10.0.2.2 0.0.0.0 UG 600 0 0 wlan0
            10.0.2.2 * 255.255.248.0 U 600 0 0 wlan0
            link-local * 255.255.0.0 U 1000 0 0 wlan0


            Type the gateway adress in your browser (here: 10.0.2.2), this should get you to the captive portal page. Try with different browsers if necessary.






            share|improve this answer
























              up vote
              0
              down vote













              This seems to be a known issue with 16.04 and Linux-unfriendly captive portals, possibly fixed since 17.10 but I'm unsure and can't test it. Meanwhile, if you can't upgrade or try with the latests Ubuntu versions, use the route command in terminal.



              $ sudo route


              You should see something like:



              Kernel IP routing table

              Destination Gateway Genmask Flags Metric Ref Use Iface
              default 10.0.2.2 0.0.0.0 UG 600 0 0 wlan0
              10.0.2.2 * 255.255.248.0 U 600 0 0 wlan0
              link-local * 255.255.0.0 U 1000 0 0 wlan0


              Type the gateway adress in your browser (here: 10.0.2.2), this should get you to the captive portal page. Try with different browsers if necessary.






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                This seems to be a known issue with 16.04 and Linux-unfriendly captive portals, possibly fixed since 17.10 but I'm unsure and can't test it. Meanwhile, if you can't upgrade or try with the latests Ubuntu versions, use the route command in terminal.



                $ sudo route


                You should see something like:



                Kernel IP routing table

                Destination Gateway Genmask Flags Metric Ref Use Iface
                default 10.0.2.2 0.0.0.0 UG 600 0 0 wlan0
                10.0.2.2 * 255.255.248.0 U 600 0 0 wlan0
                link-local * 255.255.0.0 U 1000 0 0 wlan0


                Type the gateway adress in your browser (here: 10.0.2.2), this should get you to the captive portal page. Try with different browsers if necessary.






                share|improve this answer












                This seems to be a known issue with 16.04 and Linux-unfriendly captive portals, possibly fixed since 17.10 but I'm unsure and can't test it. Meanwhile, if you can't upgrade or try with the latests Ubuntu versions, use the route command in terminal.



                $ sudo route


                You should see something like:



                Kernel IP routing table

                Destination Gateway Genmask Flags Metric Ref Use Iface
                default 10.0.2.2 0.0.0.0 UG 600 0 0 wlan0
                10.0.2.2 * 255.255.248.0 U 600 0 0 wlan0
                link-local * 255.255.0.0 U 1000 0 0 wlan0


                Type the gateway adress in your browser (here: 10.0.2.2), this should get you to the captive portal page. Try with different browsers if necessary.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered May 28 at 7:25









                ChuckMaurice

                362




                362






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1041005%2fubuntu-16-04-how-to-use-ethernet-captive-portals%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    pylint3 and pip3 broken

                    Missing snmpget and snmpwalk

                    How to enroll fingerprints to Ubuntu 17.10 with VFS491