Issue with Wifi Adapter with Docker Windows (Native, HYPER-V)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







15















I just received a brand new work laptop and immediately installed the native version of Docker for Windows.



However I am seeing an issue that everytime the new network adapter for Docker via Hyper-V is enabled (vEthernet DockerNAT) then my Wifi Adapter is disabled and therefore I can not access the internet.



Whenever I try to enable the Wifi Adapter it keeps disabling itself immediately, the only way to get my internet back is by deactivating the DockerNAT HyperV Adapter.



This must surely work otherwise they wouldnt have released the Windows Native version publically?



Has anyone experienced this issue and know how to fix it? (This is my first experience with Hyper-V)










share|improve this question





























    15















    I just received a brand new work laptop and immediately installed the native version of Docker for Windows.



    However I am seeing an issue that everytime the new network adapter for Docker via Hyper-V is enabled (vEthernet DockerNAT) then my Wifi Adapter is disabled and therefore I can not access the internet.



    Whenever I try to enable the Wifi Adapter it keeps disabling itself immediately, the only way to get my internet back is by deactivating the DockerNAT HyperV Adapter.



    This must surely work otherwise they wouldnt have released the Windows Native version publically?



    Has anyone experienced this issue and know how to fix it? (This is my first experience with Hyper-V)










    share|improve this question

























      15












      15








      15


      4






      I just received a brand new work laptop and immediately installed the native version of Docker for Windows.



      However I am seeing an issue that everytime the new network adapter for Docker via Hyper-V is enabled (vEthernet DockerNAT) then my Wifi Adapter is disabled and therefore I can not access the internet.



      Whenever I try to enable the Wifi Adapter it keeps disabling itself immediately, the only way to get my internet back is by deactivating the DockerNAT HyperV Adapter.



      This must surely work otherwise they wouldnt have released the Windows Native version publically?



      Has anyone experienced this issue and know how to fix it? (This is my first experience with Hyper-V)










      share|improve this question














      I just received a brand new work laptop and immediately installed the native version of Docker for Windows.



      However I am seeing an issue that everytime the new network adapter for Docker via Hyper-V is enabled (vEthernet DockerNAT) then my Wifi Adapter is disabled and therefore I can not access the internet.



      Whenever I try to enable the Wifi Adapter it keeps disabling itself immediately, the only way to get my internet back is by deactivating the DockerNAT HyperV Adapter.



      This must surely work otherwise they wouldnt have released the Windows Native version publically?



      Has anyone experienced this issue and know how to fix it? (This is my first experience with Hyper-V)







      networking windows-10 network-adapter hyper-v docker






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 13 '16 at 12:30









      UsainBlootUsainBloot

      78119




      78119






















          5 Answers
          5






          active

          oldest

          votes


















          13





          +100









          As no one has answered yet, I will try to help, but warn that I do not use Docker and do not have your environment. This is all theory.



          My theory is that the problem you are running into is with Windows 10 rather than with Docker or Hyper-V. I see a connection between the fact that on the one hand one cannot have both Ethernet and WiFi connections enabled at the same time, and on the other hand one cannot do NAT with WiFi. Therefore your enabling
          of NAT might cause the enabling of an Ethernet adapter which disables the wireless adapter.



          If I am right, there might be two solutions to the problem :




          1. Connect the computer via wired wired rather than wireless

          2. Create a virtual Ethernet adapter around the wireless adapter:


            • Open Hyper-V manager

            • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.

            • Give a meaningful Name

            • Apply and OK

            • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.

            • On the host machine, in the Network and Sharing Center click on Change Adapter Settings

            • Select your WiFi Adapter and the Internal Virtual Network you created.

            • Right click and select Bridge Network and the bridge is created.

            • Use the Internal Virtual Network that you created initially for Docker NAT.




          If the above does not work for some reason, a software that might be able to help is Connectify Hotspot (shareware/paid), which via its Virtual Router can share WiFi as Ethernet.



          Another which might do the job is SoftEther VPN Open Source, which however requires connecting to a VPN in order to use its Virtual Network Adapter.






          share|improve this answer





















          • 1





            You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

            – Daniel B
            Aug 31 '16 at 12:05











          • What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

            – Jesse
            Jun 27 '18 at 15:44





















          6














          After trying all types of remedies advised here and there, and with none of them fixing the issue, I eventually found that in my case it was 3rd party software (PulseSecure) that was disabling WiFi whenever Hyper-V adapter was active. So, if you have this software installed as well there is a good chance that it is causing the problem.
          You can disable "Pulse Secure Service" service to see if that's indeed the case, and if that solves your issue.






          share|improve this answer





















          • 1





            I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

            – rodey
            Jul 12 '18 at 14:37











          • This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

            – Nick Klauer
            Aug 3 '18 at 19:13



















          1














          Temporary Solution. Disable the vEthernet(DockerNAT) though this will last until your next reboot.



          Goto Control Panel => Network and Sharing Center => Change Adapter Settings => Right click on vEthernet(DockerNAT) and Disable.






          share|improve this answer































            0














            Another temporary solution is just to configure the DockerNAT virtual switch to private though this will last until your next reboot.



            Here is the source: https://forums.docker.com/t/wifi-adapter-disabled-when-hyper-v-network-adapter-enabled-native/18063/5






            share|improve this answer































              0














              I've found that by switching the docketNAT from internal to external solved the problem.



              enter image description here






              share|improve this answer
























                Your Answer








                StackExchange.ready(function() {
                var channelOptions = {
                tags: "".split(" "),
                id: "3"
                };
                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%2fsuperuser.com%2fquestions%2f1100336%2fissue-with-wifi-adapter-with-docker-windows-native-hyper-v%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                5 Answers
                5






                active

                oldest

                votes








                5 Answers
                5






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                13





                +100









                As no one has answered yet, I will try to help, but warn that I do not use Docker and do not have your environment. This is all theory.



                My theory is that the problem you are running into is with Windows 10 rather than with Docker or Hyper-V. I see a connection between the fact that on the one hand one cannot have both Ethernet and WiFi connections enabled at the same time, and on the other hand one cannot do NAT with WiFi. Therefore your enabling
                of NAT might cause the enabling of an Ethernet adapter which disables the wireless adapter.



                If I am right, there might be two solutions to the problem :




                1. Connect the computer via wired wired rather than wireless

                2. Create a virtual Ethernet adapter around the wireless adapter:


                  • Open Hyper-V manager

                  • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.

                  • Give a meaningful Name

                  • Apply and OK

                  • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.

                  • On the host machine, in the Network and Sharing Center click on Change Adapter Settings

                  • Select your WiFi Adapter and the Internal Virtual Network you created.

                  • Right click and select Bridge Network and the bridge is created.

                  • Use the Internal Virtual Network that you created initially for Docker NAT.




                If the above does not work for some reason, a software that might be able to help is Connectify Hotspot (shareware/paid), which via its Virtual Router can share WiFi as Ethernet.



                Another which might do the job is SoftEther VPN Open Source, which however requires connecting to a VPN in order to use its Virtual Network Adapter.






                share|improve this answer





















                • 1





                  You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                  – Daniel B
                  Aug 31 '16 at 12:05











                • What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                  – Jesse
                  Jun 27 '18 at 15:44


















                13





                +100









                As no one has answered yet, I will try to help, but warn that I do not use Docker and do not have your environment. This is all theory.



                My theory is that the problem you are running into is with Windows 10 rather than with Docker or Hyper-V. I see a connection between the fact that on the one hand one cannot have both Ethernet and WiFi connections enabled at the same time, and on the other hand one cannot do NAT with WiFi. Therefore your enabling
                of NAT might cause the enabling of an Ethernet adapter which disables the wireless adapter.



                If I am right, there might be two solutions to the problem :




                1. Connect the computer via wired wired rather than wireless

                2. Create a virtual Ethernet adapter around the wireless adapter:


                  • Open Hyper-V manager

                  • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.

                  • Give a meaningful Name

                  • Apply and OK

                  • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.

                  • On the host machine, in the Network and Sharing Center click on Change Adapter Settings

                  • Select your WiFi Adapter and the Internal Virtual Network you created.

                  • Right click and select Bridge Network and the bridge is created.

                  • Use the Internal Virtual Network that you created initially for Docker NAT.




                If the above does not work for some reason, a software that might be able to help is Connectify Hotspot (shareware/paid), which via its Virtual Router can share WiFi as Ethernet.



                Another which might do the job is SoftEther VPN Open Source, which however requires connecting to a VPN in order to use its Virtual Network Adapter.






                share|improve this answer





















                • 1





                  You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                  – Daniel B
                  Aug 31 '16 at 12:05











                • What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                  – Jesse
                  Jun 27 '18 at 15:44
















                13





                +100







                13





                +100



                13




                +100





                As no one has answered yet, I will try to help, but warn that I do not use Docker and do not have your environment. This is all theory.



                My theory is that the problem you are running into is with Windows 10 rather than with Docker or Hyper-V. I see a connection between the fact that on the one hand one cannot have both Ethernet and WiFi connections enabled at the same time, and on the other hand one cannot do NAT with WiFi. Therefore your enabling
                of NAT might cause the enabling of an Ethernet adapter which disables the wireless adapter.



                If I am right, there might be two solutions to the problem :




                1. Connect the computer via wired wired rather than wireless

                2. Create a virtual Ethernet adapter around the wireless adapter:


                  • Open Hyper-V manager

                  • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.

                  • Give a meaningful Name

                  • Apply and OK

                  • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.

                  • On the host machine, in the Network and Sharing Center click on Change Adapter Settings

                  • Select your WiFi Adapter and the Internal Virtual Network you created.

                  • Right click and select Bridge Network and the bridge is created.

                  • Use the Internal Virtual Network that you created initially for Docker NAT.




                If the above does not work for some reason, a software that might be able to help is Connectify Hotspot (shareware/paid), which via its Virtual Router can share WiFi as Ethernet.



                Another which might do the job is SoftEther VPN Open Source, which however requires connecting to a VPN in order to use its Virtual Network Adapter.






                share|improve this answer















                As no one has answered yet, I will try to help, but warn that I do not use Docker and do not have your environment. This is all theory.



                My theory is that the problem you are running into is with Windows 10 rather than with Docker or Hyper-V. I see a connection between the fact that on the one hand one cannot have both Ethernet and WiFi connections enabled at the same time, and on the other hand one cannot do NAT with WiFi. Therefore your enabling
                of NAT might cause the enabling of an Ethernet adapter which disables the wireless adapter.



                If I am right, there might be two solutions to the problem :




                1. Connect the computer via wired wired rather than wireless

                2. Create a virtual Ethernet adapter around the wireless adapter:


                  • Open Hyper-V manager

                  • Click on the Virtual Network Manager and create an Internal Virtual Network by selecting Internal and clicking Add.

                  • Give a meaningful Name

                  • Apply and OK

                  • Now a Virtual Network has been created which can be associated with 1 or more virtual machines.

                  • On the host machine, in the Network and Sharing Center click on Change Adapter Settings

                  • Select your WiFi Adapter and the Internal Virtual Network you created.

                  • Right click and select Bridge Network and the bridge is created.

                  • Use the Internal Virtual Network that you created initially for Docker NAT.




                If the above does not work for some reason, a software that might be able to help is Connectify Hotspot (shareware/paid), which via its Virtual Router can share WiFi as Ethernet.



                Another which might do the job is SoftEther VPN Open Source, which however requires connecting to a VPN in order to use its Virtual Network Adapter.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 15 '17 at 10:23









                SQB

                542716




                542716










                answered Aug 29 '16 at 8:48









                harrymcharrymc

                265k14274583




                265k14274583








                • 1





                  You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                  – Daniel B
                  Aug 31 '16 at 12:05











                • What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                  – Jesse
                  Jun 27 '18 at 15:44
















                • 1





                  You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                  – Daniel B
                  Aug 31 '16 at 12:05











                • What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                  – Jesse
                  Jun 27 '18 at 15:44










                1




                1





                You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                – Daniel B
                Aug 31 '16 at 12:05





                You can do NAT (or any routing, really) with WiFi upstream no problem. It’s bridging that’s not possible.

                – Daniel B
                Aug 31 '16 at 12:05













                What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                – Jesse
                Jun 27 '18 at 15:44







                What also worked for me, is to edit properties of the wifi adapter, to enable sharing via "vEthernet (DockerNAT)". Also had to disable the other adapter, "vEthernet (Default Switch)".

                – Jesse
                Jun 27 '18 at 15:44















                6














                After trying all types of remedies advised here and there, and with none of them fixing the issue, I eventually found that in my case it was 3rd party software (PulseSecure) that was disabling WiFi whenever Hyper-V adapter was active. So, if you have this software installed as well there is a good chance that it is causing the problem.
                You can disable "Pulse Secure Service" service to see if that's indeed the case, and if that solves your issue.






                share|improve this answer





















                • 1





                  I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                  – rodey
                  Jul 12 '18 at 14:37











                • This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                  – Nick Klauer
                  Aug 3 '18 at 19:13
















                6














                After trying all types of remedies advised here and there, and with none of them fixing the issue, I eventually found that in my case it was 3rd party software (PulseSecure) that was disabling WiFi whenever Hyper-V adapter was active. So, if you have this software installed as well there is a good chance that it is causing the problem.
                You can disable "Pulse Secure Service" service to see if that's indeed the case, and if that solves your issue.






                share|improve this answer





















                • 1





                  I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                  – rodey
                  Jul 12 '18 at 14:37











                • This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                  – Nick Klauer
                  Aug 3 '18 at 19:13














                6












                6








                6







                After trying all types of remedies advised here and there, and with none of them fixing the issue, I eventually found that in my case it was 3rd party software (PulseSecure) that was disabling WiFi whenever Hyper-V adapter was active. So, if you have this software installed as well there is a good chance that it is causing the problem.
                You can disable "Pulse Secure Service" service to see if that's indeed the case, and if that solves your issue.






                share|improve this answer















                After trying all types of remedies advised here and there, and with none of them fixing the issue, I eventually found that in my case it was 3rd party software (PulseSecure) that was disabling WiFi whenever Hyper-V adapter was active. So, if you have this software installed as well there is a good chance that it is causing the problem.
                You can disable "Pulse Secure Service" service to see if that's indeed the case, and if that solves your issue.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 21 '18 at 19:11









                DrMoishe Pippik

                10.5k21432




                10.5k21432










                answered Mar 21 '18 at 18:00









                Gediminas ZukulaGediminas Zukula

                6111




                6111








                • 1





                  I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                  – rodey
                  Jul 12 '18 at 14:37











                • This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                  – Nick Klauer
                  Aug 3 '18 at 19:13














                • 1





                  I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                  – rodey
                  Jul 12 '18 at 14:37











                • This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                  – Nick Klauer
                  Aug 3 '18 at 19:13








                1




                1





                I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                – rodey
                Jul 12 '18 at 14:37





                I suffered from the same issue. Pulse version 5.3.4 (1555) with installer name ps-pulse-win-5.3R4.1HF11-b1555-64bitinstaller.msi seems to solve the issue. I can user Hyper-V and Docker and the wifi adapter stays enabled.

                – rodey
                Jul 12 '18 at 14:37













                This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                – Nick Klauer
                Aug 3 '18 at 19:13





                This is very interesting. Unfortunately, I use Pulse Secure for my company's VPN solution, so I don't know if this is something I can disable, as it would result in me not being able to connect at all to work.

                – Nick Klauer
                Aug 3 '18 at 19:13











                1














                Temporary Solution. Disable the vEthernet(DockerNAT) though this will last until your next reboot.



                Goto Control Panel => Network and Sharing Center => Change Adapter Settings => Right click on vEthernet(DockerNAT) and Disable.






                share|improve this answer




























                  1














                  Temporary Solution. Disable the vEthernet(DockerNAT) though this will last until your next reboot.



                  Goto Control Panel => Network and Sharing Center => Change Adapter Settings => Right click on vEthernet(DockerNAT) and Disable.






                  share|improve this answer


























                    1












                    1








                    1







                    Temporary Solution. Disable the vEthernet(DockerNAT) though this will last until your next reboot.



                    Goto Control Panel => Network and Sharing Center => Change Adapter Settings => Right click on vEthernet(DockerNAT) and Disable.






                    share|improve this answer













                    Temporary Solution. Disable the vEthernet(DockerNAT) though this will last until your next reboot.



                    Goto Control Panel => Network and Sharing Center => Change Adapter Settings => Right click on vEthernet(DockerNAT) and Disable.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 8 at 6:32









                    Namdev KendreNamdev Kendre

                    111




                    111























                        0














                        Another temporary solution is just to configure the DockerNAT virtual switch to private though this will last until your next reboot.



                        Here is the source: https://forums.docker.com/t/wifi-adapter-disabled-when-hyper-v-network-adapter-enabled-native/18063/5






                        share|improve this answer




























                          0














                          Another temporary solution is just to configure the DockerNAT virtual switch to private though this will last until your next reboot.



                          Here is the source: https://forums.docker.com/t/wifi-adapter-disabled-when-hyper-v-network-adapter-enabled-native/18063/5






                          share|improve this answer


























                            0












                            0








                            0







                            Another temporary solution is just to configure the DockerNAT virtual switch to private though this will last until your next reboot.



                            Here is the source: https://forums.docker.com/t/wifi-adapter-disabled-when-hyper-v-network-adapter-enabled-native/18063/5






                            share|improve this answer













                            Another temporary solution is just to configure the DockerNAT virtual switch to private though this will last until your next reboot.



                            Here is the source: https://forums.docker.com/t/wifi-adapter-disabled-when-hyper-v-network-adapter-enabled-native/18063/5







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Aug 16 '17 at 9:23









                            LeoLeo

                            1012




                            1012























                                0














                                I've found that by switching the docketNAT from internal to external solved the problem.



                                enter image description here






                                share|improve this answer




























                                  0














                                  I've found that by switching the docketNAT from internal to external solved the problem.



                                  enter image description here






                                  share|improve this answer


























                                    0












                                    0








                                    0







                                    I've found that by switching the docketNAT from internal to external solved the problem.



                                    enter image description here






                                    share|improve this answer













                                    I've found that by switching the docketNAT from internal to external solved the problem.



                                    enter image description here







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Nov 8 '17 at 12:49









                                    jackdhjackdh

                                    15829




                                    15829






























                                        draft saved

                                        draft discarded




















































                                        Thanks for contributing an answer to Super User!


                                        • 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%2fsuperuser.com%2fquestions%2f1100336%2fissue-with-wifi-adapter-with-docker-windows-native-hyper-v%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

                                        Probability when a professor distributes a quiz and homework assignment to a class of n students.

                                        Aardman Animations

                                        Are they similar matrix