Auto-connect VPN in Kali Linux?Connect to a VPN from a Linux Virtual MachineIs there a VPN client for...

Why does the painters tape have to be blue?

Did significant numbers of Japanese officers escape prosecution during the Tokyo Trials?

Status of proof by contradiction and excluded middle throughout the history of mathematics?

ifconfig shows UP while ip link shows DOWN

Why does the hash of infinity have the digits of π?

Is superuser the same as root?

Is there an idiom that means "accepting a bad business deal out of desperation"?

How to write numbers and percentage?

Why did it take so long for Germany to allow electric scooters / e-rollers on the roads?

Why isn't Tyrion mentioned in 'A song of Ice and Fire'?

Count all vowels in string

Is this homebrew "Cactus Grenade" cantrip balanced?

The disk image is 497GB smaller than the target device

Is there a simple example that empirical evidence is misleading?

Why A=2 and B=1 in the call signs for Spirit and Opportunity?

Cisco 3750X Power Cable

Are cells guaranteed to get at least one mitochondrion when they divide?

Ribbon Cable Cross Talk - Is there a fix after the fact?

Possibility of faking someone's public key

Question about Shemot, locusts

Time complexity of an algorithm: Is it important to state the base of the logarithm?

What would prevent living skin from being a good conductor for magic?

Navigating a quick return to previous employer

To exponential digit growth and beyond!



Auto-connect VPN in Kali Linux?


Connect to a VPN from a Linux Virtual MachineIs there a VPN client for Kali?Running HMA Pro VPN on Kali LinuxSetting up a VPN in Kali Linux 2.0Auto connect and reconnect to VPN on Debian 8firmware failed to load iwlwifi - an AMD specific problemHow to bring up ethernet networking upon cable connection without network manager (on CentOS 7)Can't connect to vpn with Network-managerReconfigure network-manager on Kali Linux after installing openvpn or vpn-unlimited






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I current have a working VPN on my Kali Linux box however I feel uncomfortable with the fact that sometimes I forget to manually connect it in the network manager.



After digging around everywhere in the gnome-control-center network I can't seem to find anyway to initiate the VPN connection automatically.



Is there something I am missing or perhaps an alternative for a network manager GUI? If not, how could I add the terminal commands to execute during the boot process?










share|improve this question





























    0















    I current have a working VPN on my Kali Linux box however I feel uncomfortable with the fact that sometimes I forget to manually connect it in the network manager.



    After digging around everywhere in the gnome-control-center network I can't seem to find anyway to initiate the VPN connection automatically.



    Is there something I am missing or perhaps an alternative for a network manager GUI? If not, how could I add the terminal commands to execute during the boot process?










    share|improve this question

























      0












      0








      0








      I current have a working VPN on my Kali Linux box however I feel uncomfortable with the fact that sometimes I forget to manually connect it in the network manager.



      After digging around everywhere in the gnome-control-center network I can't seem to find anyway to initiate the VPN connection automatically.



      Is there something I am missing or perhaps an alternative for a network manager GUI? If not, how could I add the terminal commands to execute during the boot process?










      share|improve this question














      I current have a working VPN on my Kali Linux box however I feel uncomfortable with the fact that sometimes I forget to manually connect it in the network manager.



      After digging around everywhere in the gnome-control-center network I can't seem to find anyway to initiate the VPN connection automatically.



      Is there something I am missing or perhaps an alternative for a network manager GUI? If not, how could I add the terminal commands to execute during the boot process?







      kali-linux networkmanager vpn autostart boot-process






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jun 8 '17 at 2:26









      NorrNorr

      66119




      66119






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Does your system have a /etc/NetworkManager/system-connections directory populated with connection profiles?



          I've a kali-rolling build which is very much like setting up as described in an Ubuntu related answer I posted about configuring such things for a particular interface. The TLDR version is as follows...



          /etc/NetworkManager/system-connections/WiFI_AP



          [connection]
          id=WiFI_AP
          uuid=aaaa-0000-aaaa-0000
          type=wifi
          autoconnect=true
          autoconnect-priority=9000
          permissions=
          secondaries=deadbeef-d3ad-b33f-dead-be33e3f;
          autoconnect-slaves=1
          vpn.timeout=120
          # ... more connection config blocks...


          /etc/NetworkManager/system-connections/VPN_Client



          [connection]
          id=VPN_Client
          uuid=deadbeef-d3ad-b33f-dead-be33e3f
          type=vpn
          permissions=
          secondaries=
          # ... more connection config blocks...



          Note if you're roaming about then ya may instead want just the following...




          /etc/NetworkManager/system-connections/VPN_Client



          [connection]
          id=VPN_Client
          uuid=deadbeef-d3ad-b33f-dead-be33e3f
          type=vpn
          permissions=
          secondaries=
          autoconnect=true
          autoconnect-priority=8999
          # ... more connection config blocks...



          ... but for me that caused things to barf so use at your own risk.




          The secondaries=deadbeef-d3ad-b33f-dead-be33e3f; line within WiFI_AP is a space separated list of uuids of slave connections that should also be hooked the WiFi_AP network, in this case the uuid from the VPN_Client config; side note, these lists (from what I've gathered) must end with a semicolon ;



          The autoconnect-slaves=1 line within WiFI_AP is what enables this fancy hooking of one network with another. And the vpn.timeout=120 line may need a longer wait time if you've got VPN certs within an encrypted home directory.



          Related manuals maybe found via man NetworkManager, man NetworkManager.conf, and man nm-settings.



          Personally I found rebooting to be safer than things like systemctl reload NetworkManager when testing various combos of connection profile modifications.






          share|improve this answer
























            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%2f369876%2fauto-connect-vpn-in-kali-linux%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









            0














            Does your system have a /etc/NetworkManager/system-connections directory populated with connection profiles?



            I've a kali-rolling build which is very much like setting up as described in an Ubuntu related answer I posted about configuring such things for a particular interface. The TLDR version is as follows...



            /etc/NetworkManager/system-connections/WiFI_AP



            [connection]
            id=WiFI_AP
            uuid=aaaa-0000-aaaa-0000
            type=wifi
            autoconnect=true
            autoconnect-priority=9000
            permissions=
            secondaries=deadbeef-d3ad-b33f-dead-be33e3f;
            autoconnect-slaves=1
            vpn.timeout=120
            # ... more connection config blocks...


            /etc/NetworkManager/system-connections/VPN_Client



            [connection]
            id=VPN_Client
            uuid=deadbeef-d3ad-b33f-dead-be33e3f
            type=vpn
            permissions=
            secondaries=
            # ... more connection config blocks...



            Note if you're roaming about then ya may instead want just the following...




            /etc/NetworkManager/system-connections/VPN_Client



            [connection]
            id=VPN_Client
            uuid=deadbeef-d3ad-b33f-dead-be33e3f
            type=vpn
            permissions=
            secondaries=
            autoconnect=true
            autoconnect-priority=8999
            # ... more connection config blocks...



            ... but for me that caused things to barf so use at your own risk.




            The secondaries=deadbeef-d3ad-b33f-dead-be33e3f; line within WiFI_AP is a space separated list of uuids of slave connections that should also be hooked the WiFi_AP network, in this case the uuid from the VPN_Client config; side note, these lists (from what I've gathered) must end with a semicolon ;



            The autoconnect-slaves=1 line within WiFI_AP is what enables this fancy hooking of one network with another. And the vpn.timeout=120 line may need a longer wait time if you've got VPN certs within an encrypted home directory.



            Related manuals maybe found via man NetworkManager, man NetworkManager.conf, and man nm-settings.



            Personally I found rebooting to be safer than things like systemctl reload NetworkManager when testing various combos of connection profile modifications.






            share|improve this answer




























              0














              Does your system have a /etc/NetworkManager/system-connections directory populated with connection profiles?



              I've a kali-rolling build which is very much like setting up as described in an Ubuntu related answer I posted about configuring such things for a particular interface. The TLDR version is as follows...



              /etc/NetworkManager/system-connections/WiFI_AP



              [connection]
              id=WiFI_AP
              uuid=aaaa-0000-aaaa-0000
              type=wifi
              autoconnect=true
              autoconnect-priority=9000
              permissions=
              secondaries=deadbeef-d3ad-b33f-dead-be33e3f;
              autoconnect-slaves=1
              vpn.timeout=120
              # ... more connection config blocks...


              /etc/NetworkManager/system-connections/VPN_Client



              [connection]
              id=VPN_Client
              uuid=deadbeef-d3ad-b33f-dead-be33e3f
              type=vpn
              permissions=
              secondaries=
              # ... more connection config blocks...



              Note if you're roaming about then ya may instead want just the following...




              /etc/NetworkManager/system-connections/VPN_Client



              [connection]
              id=VPN_Client
              uuid=deadbeef-d3ad-b33f-dead-be33e3f
              type=vpn
              permissions=
              secondaries=
              autoconnect=true
              autoconnect-priority=8999
              # ... more connection config blocks...



              ... but for me that caused things to barf so use at your own risk.




              The secondaries=deadbeef-d3ad-b33f-dead-be33e3f; line within WiFI_AP is a space separated list of uuids of slave connections that should also be hooked the WiFi_AP network, in this case the uuid from the VPN_Client config; side note, these lists (from what I've gathered) must end with a semicolon ;



              The autoconnect-slaves=1 line within WiFI_AP is what enables this fancy hooking of one network with another. And the vpn.timeout=120 line may need a longer wait time if you've got VPN certs within an encrypted home directory.



              Related manuals maybe found via man NetworkManager, man NetworkManager.conf, and man nm-settings.



              Personally I found rebooting to be safer than things like systemctl reload NetworkManager when testing various combos of connection profile modifications.






              share|improve this answer


























                0












                0








                0







                Does your system have a /etc/NetworkManager/system-connections directory populated with connection profiles?



                I've a kali-rolling build which is very much like setting up as described in an Ubuntu related answer I posted about configuring such things for a particular interface. The TLDR version is as follows...



                /etc/NetworkManager/system-connections/WiFI_AP



                [connection]
                id=WiFI_AP
                uuid=aaaa-0000-aaaa-0000
                type=wifi
                autoconnect=true
                autoconnect-priority=9000
                permissions=
                secondaries=deadbeef-d3ad-b33f-dead-be33e3f;
                autoconnect-slaves=1
                vpn.timeout=120
                # ... more connection config blocks...


                /etc/NetworkManager/system-connections/VPN_Client



                [connection]
                id=VPN_Client
                uuid=deadbeef-d3ad-b33f-dead-be33e3f
                type=vpn
                permissions=
                secondaries=
                # ... more connection config blocks...



                Note if you're roaming about then ya may instead want just the following...




                /etc/NetworkManager/system-connections/VPN_Client



                [connection]
                id=VPN_Client
                uuid=deadbeef-d3ad-b33f-dead-be33e3f
                type=vpn
                permissions=
                secondaries=
                autoconnect=true
                autoconnect-priority=8999
                # ... more connection config blocks...



                ... but for me that caused things to barf so use at your own risk.




                The secondaries=deadbeef-d3ad-b33f-dead-be33e3f; line within WiFI_AP is a space separated list of uuids of slave connections that should also be hooked the WiFi_AP network, in this case the uuid from the VPN_Client config; side note, these lists (from what I've gathered) must end with a semicolon ;



                The autoconnect-slaves=1 line within WiFI_AP is what enables this fancy hooking of one network with another. And the vpn.timeout=120 line may need a longer wait time if you've got VPN certs within an encrypted home directory.



                Related manuals maybe found via man NetworkManager, man NetworkManager.conf, and man nm-settings.



                Personally I found rebooting to be safer than things like systemctl reload NetworkManager when testing various combos of connection profile modifications.






                share|improve this answer













                Does your system have a /etc/NetworkManager/system-connections directory populated with connection profiles?



                I've a kali-rolling build which is very much like setting up as described in an Ubuntu related answer I posted about configuring such things for a particular interface. The TLDR version is as follows...



                /etc/NetworkManager/system-connections/WiFI_AP



                [connection]
                id=WiFI_AP
                uuid=aaaa-0000-aaaa-0000
                type=wifi
                autoconnect=true
                autoconnect-priority=9000
                permissions=
                secondaries=deadbeef-d3ad-b33f-dead-be33e3f;
                autoconnect-slaves=1
                vpn.timeout=120
                # ... more connection config blocks...


                /etc/NetworkManager/system-connections/VPN_Client



                [connection]
                id=VPN_Client
                uuid=deadbeef-d3ad-b33f-dead-be33e3f
                type=vpn
                permissions=
                secondaries=
                # ... more connection config blocks...



                Note if you're roaming about then ya may instead want just the following...




                /etc/NetworkManager/system-connections/VPN_Client



                [connection]
                id=VPN_Client
                uuid=deadbeef-d3ad-b33f-dead-be33e3f
                type=vpn
                permissions=
                secondaries=
                autoconnect=true
                autoconnect-priority=8999
                # ... more connection config blocks...



                ... but for me that caused things to barf so use at your own risk.




                The secondaries=deadbeef-d3ad-b33f-dead-be33e3f; line within WiFI_AP is a space separated list of uuids of slave connections that should also be hooked the WiFi_AP network, in this case the uuid from the VPN_Client config; side note, these lists (from what I've gathered) must end with a semicolon ;



                The autoconnect-slaves=1 line within WiFI_AP is what enables this fancy hooking of one network with another. And the vpn.timeout=120 line may need a longer wait time if you've got VPN certs within an encrypted home directory.



                Related manuals maybe found via man NetworkManager, man NetworkManager.conf, and man nm-settings.



                Personally I found rebooting to be safer than things like systemctl reload NetworkManager when testing various combos of connection profile modifications.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 hours ago









                S0AndS0S0AndS0

                1967




                1967






























                    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%2f369876%2fauto-connect-vpn-in-kali-linux%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

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...