Ubuntu 16.04 Unknown interfaceNot able to connect to local networkConflict between two network interfaces eth0 and eth114.04 no internet connection when I up the bridge interface (for LXC container)IPv6 SLAAC on Ubuntu Server 16.04.Dual NIC not workingNo pings no package locations on server16.04.3: setting eth interface down to get wifi interface workRaspberry Pi 3B with Ubuntu Server(CLI) with No Ethernet Recognition and No Wlan0 ListSeveral websites unreachable on university network (w/o VPN)How to enable wireless on Ubuntu Server 18.04 via CLI?

How to explain what's wrong with this application of the chain rule?

Terse Method to Swap Lowest for Highest?

How do you respond to a colleague from another team when they're wrongly expecting that you'll help them?

copy and scale one figure (wheel)

Why did the Mercure fail?

What was this official D&D 3.5e Lovecraft-flavored rulebook?

Non-trope happy ending?

Longest common substring in linear time

Why Shazam when there is already Superman?

Is it improper etiquette to ask your opponent what his/her rating is before the game?

What should you do when eye contact makes your subordinate uncomfortable?

Are the IPv6 address space and IPv4 address space completely disjoint?

What does chmod -u do?

What is the evidence for the "tyranny of the majority problem" in a direct democracy context?

Where does the bonus feat in the cleric starting package come from?

If infinitesimal transformations commute why dont the generators of the Lorentz group commute?

Creepy dinosaur pc game identification

What should you do if you miss a job interview (deliberately)?

How can "mimic phobia" be cured or prevented?

Lowest total scrabble score

Removing files under particular conditions (number of files, file age)

Why does the Sun have different day lengths, but not the gas giants?

Multiplicative persistence

Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?



Ubuntu 16.04 Unknown interface


Not able to connect to local networkConflict between two network interfaces eth0 and eth114.04 no internet connection when I up the bridge interface (for LXC container)IPv6 SLAAC on Ubuntu Server 16.04.Dual NIC not workingNo pings no package locations on server16.04.3: setting eth interface down to get wifi interface workRaspberry Pi 3B with Ubuntu Server(CLI) with No Ethernet Recognition and No Wlan0 ListSeveral websites unreachable on university network (w/o VPN)How to enable wireless on Ubuntu Server 18.04 via CLI?













0















I have an issue when configuring a second nic for my ubuntu server. Look at this:



root@ubuntubox01:~# lshw -short | grep network
/0/100/15/0 ens160 network VMXNET3 Ethernet Controller
/0/100/16/0 ens192 network VMXNET3 Ethernet Controller


When I look at the IP Addresses:



root@ubuntubox01:~# ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff
inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feb6:5289/64 scope link
valid_lft forever preferred_lft forever
3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff
inet6 fe80::250:56ff:feb6:e22d/64 scope link
valid_lft forever preferred_lft forever


But if I do:



root@ubuntubox01:~# ifup ens192
Unknown interface ens192


Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?



I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.



Greetings,



C.










share|improve this question














bumped to the homepage by Community 49 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















    0















    I have an issue when configuring a second nic for my ubuntu server. Look at this:



    root@ubuntubox01:~# lshw -short | grep network
    /0/100/15/0 ens160 network VMXNET3 Ethernet Controller
    /0/100/16/0 ens192 network VMXNET3 Ethernet Controller


    When I look at the IP Addresses:



    root@ubuntubox01:~# ip addr sh
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff
    inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160
    valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:feb6:5289/64 scope link
    valid_lft forever preferred_lft forever
    3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::250:56ff:feb6:e22d/64 scope link
    valid_lft forever preferred_lft forever


    But if I do:



    root@ubuntubox01:~# ifup ens192
    Unknown interface ens192


    Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?



    I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.



    Greetings,



    C.










    share|improve this question














    bumped to the homepage by Community 49 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      0












      0








      0








      I have an issue when configuring a second nic for my ubuntu server. Look at this:



      root@ubuntubox01:~# lshw -short | grep network
      /0/100/15/0 ens160 network VMXNET3 Ethernet Controller
      /0/100/16/0 ens192 network VMXNET3 Ethernet Controller


      When I look at the IP Addresses:



      root@ubuntubox01:~# ip addr sh
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
      2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff
      inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160
      valid_lft forever preferred_lft forever
      inet6 fe80::250:56ff:feb6:5289/64 scope link
      valid_lft forever preferred_lft forever
      3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff
      inet6 fe80::250:56ff:feb6:e22d/64 scope link
      valid_lft forever preferred_lft forever


      But if I do:



      root@ubuntubox01:~# ifup ens192
      Unknown interface ens192


      Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?



      I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.



      Greetings,



      C.










      share|improve this question














      I have an issue when configuring a second nic for my ubuntu server. Look at this:



      root@ubuntubox01:~# lshw -short | grep network
      /0/100/15/0 ens160 network VMXNET3 Ethernet Controller
      /0/100/16/0 ens192 network VMXNET3 Ethernet Controller


      When I look at the IP Addresses:



      root@ubuntubox01:~# ip addr sh
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
      2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff
      inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160
      valid_lft forever preferred_lft forever
      inet6 fe80::250:56ff:feb6:5289/64 scope link
      valid_lft forever preferred_lft forever
      3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff
      inet6 fe80::250:56ff:feb6:e22d/64 scope link
      valid_lft forever preferred_lft forever


      But if I do:



      root@ubuntubox01:~# ifup ens192
      Unknown interface ens192


      Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?



      I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.



      Greetings,



      C.







      16.04 networking server network-bridge






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 30 '17 at 12:00









      Carlos BravoCarlos Bravo

      112




      112





      bumped to the homepage by Community 49 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 49 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Check your /etc/network/interfaces file,
          it should contain:



          auto ens192 
          iface ens192 inet dhcp


          or for static:



          auto ens192 
          iface ens192 inet static
          #params





          share|improve this answer






























            0














            you can do:



            sudo ip link set dev eth0 down
            sudo dhclient eth0


            replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic



            Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.






            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%2f970878%2fubuntu-16-04-unknown-interface%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Check your /etc/network/interfaces file,
              it should contain:



              auto ens192 
              iface ens192 inet dhcp


              or for static:



              auto ens192 
              iface ens192 inet static
              #params





              share|improve this answer



























                0














                Check your /etc/network/interfaces file,
                it should contain:



                auto ens192 
                iface ens192 inet dhcp


                or for static:



                auto ens192 
                iface ens192 inet static
                #params





                share|improve this answer

























                  0












                  0








                  0







                  Check your /etc/network/interfaces file,
                  it should contain:



                  auto ens192 
                  iface ens192 inet dhcp


                  or for static:



                  auto ens192 
                  iface ens192 inet static
                  #params





                  share|improve this answer













                  Check your /etc/network/interfaces file,
                  it should contain:



                  auto ens192 
                  iface ens192 inet dhcp


                  or for static:



                  auto ens192 
                  iface ens192 inet static
                  #params






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 21 '17 at 4:46









                  Николай РегулярныйНиколай Регулярный

                  1




                  1























                      0














                      you can do:



                      sudo ip link set dev eth0 down
                      sudo dhclient eth0


                      replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic



                      Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.






                      share|improve this answer





























                        0














                        you can do:



                        sudo ip link set dev eth0 down
                        sudo dhclient eth0


                        replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic



                        Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.






                        share|improve this answer



























                          0












                          0








                          0







                          you can do:



                          sudo ip link set dev eth0 down
                          sudo dhclient eth0


                          replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic



                          Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.






                          share|improve this answer















                          you can do:



                          sudo ip link set dev eth0 down
                          sudo dhclient eth0


                          replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic



                          Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Jun 17 '18 at 7:17

























                          answered Jun 17 '18 at 6:55









                          Victor PiousboxVictor Piousbox

                          1013




                          1013



























                              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%2f970878%2fubuntu-16-04-unknown-interface%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

                              Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

                              Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

                              Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org