Ubuntu Server 18.04 no IPV4 after resume












1














I fail to get ipv4 working on an ubuntu server 18.04 after it was suspended and resumed. The only way I get ipv4 running again is reboot. The system is installed as a guest in a vmware virtual machine.



before resume:



ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.0.96 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
RX packets 4554 bytes 1079672 (1.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 917 bytes 77010 (77.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


lshw -C network tells me amongst other things:



driver=e1000


after resume:



ens33: flags=4098<BROADCAST,MULTICAST>  mtu 1500
ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
RX packets 4632 bytes 1087029 (1.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 919 bytes 77160 (77.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


after ifconfig ens33 up:



ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
RX packets 4666 bytes 1090488 (1.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 924 bytes 77606 (77.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


I see no IP v4 address. After googling I tried



# modprobe -r e1000
# modprobe -i e1000


but it does not change anything in the output of ifconfig. The only thing that seems to help is shutdown -r...



Any advice what else I could try?










share|improve this question



























    1














    I fail to get ipv4 working on an ubuntu server 18.04 after it was suspended and resumed. The only way I get ipv4 running again is reboot. The system is installed as a guest in a vmware virtual machine.



    before resume:



    ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.0.96 netmask 255.255.255.0 broadcast 192.168.0.255
    inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
    ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
    RX packets 4554 bytes 1079672 (1.0 MB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 917 bytes 77010 (77.0 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    lshw -C network tells me amongst other things:



    driver=e1000


    after resume:



    ens33: flags=4098<BROADCAST,MULTICAST>  mtu 1500
    ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
    RX packets 4632 bytes 1087029 (1.0 MB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 919 bytes 77160 (77.1 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    after ifconfig ens33 up:



    ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
    ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
    RX packets 4666 bytes 1090488 (1.0 MB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 924 bytes 77606 (77.6 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    I see no IP v4 address. After googling I tried



    # modprobe -r e1000
    # modprobe -i e1000


    but it does not change anything in the output of ifconfig. The only thing that seems to help is shutdown -r...



    Any advice what else I could try?










    share|improve this question

























      1












      1








      1







      I fail to get ipv4 working on an ubuntu server 18.04 after it was suspended and resumed. The only way I get ipv4 running again is reboot. The system is installed as a guest in a vmware virtual machine.



      before resume:



      ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
      inet 192.168.0.96 netmask 255.255.255.0 broadcast 192.168.0.255
      inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4554 bytes 1079672 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 917 bytes 77010 (77.0 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      lshw -C network tells me amongst other things:



      driver=e1000


      after resume:



      ens33: flags=4098<BROADCAST,MULTICAST>  mtu 1500
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4632 bytes 1087029 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 919 bytes 77160 (77.1 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      after ifconfig ens33 up:



      ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
      inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4666 bytes 1090488 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 924 bytes 77606 (77.6 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      I see no IP v4 address. After googling I tried



      # modprobe -r e1000
      # modprobe -i e1000


      but it does not change anything in the output of ifconfig. The only thing that seems to help is shutdown -r...



      Any advice what else I could try?










      share|improve this question













      I fail to get ipv4 working on an ubuntu server 18.04 after it was suspended and resumed. The only way I get ipv4 running again is reboot. The system is installed as a guest in a vmware virtual machine.



      before resume:



      ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
      inet 192.168.0.96 netmask 255.255.255.0 broadcast 192.168.0.255
      inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4554 bytes 1079672 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 917 bytes 77010 (77.0 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      lshw -C network tells me amongst other things:



      driver=e1000


      after resume:



      ens33: flags=4098<BROADCAST,MULTICAST>  mtu 1500
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4632 bytes 1087029 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 919 bytes 77160 (77.1 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      after ifconfig ens33 up:



      ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
      inet6 fe80::20c:29ff:fe1c:7d22 prefixlen 64 scopeid 0x20<link>
      ether 00:0c:29:1c:7d:22 txqueuelen 1000 (Ethernet)
      RX packets 4666 bytes 1090488 (1.0 MB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 924 bytes 77606 (77.6 KB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      I see no IP v4 address. After googling I tried



      # modprobe -r e1000
      # modprobe -i e1000


      but it does not change anything in the output of ifconfig. The only thing that seems to help is shutdown -r...



      Any advice what else I could try?







      18.04 netplan resume ipv4






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 10 at 16:42









      Dietmar F

      61




      61



























          active

          oldest

          votes











          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%2f1099837%2fubuntu-server-18-04-no-ipv4-after-resume%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f1099837%2fubuntu-server-18-04-no-ipv4-after-resume%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕