Prevent Fedora 29 from creating fake network device












0














I upgraded to Fedora 29 recently, and it keeps creating a fake network device wlp4s0 with a different fake macaddress every time:



> ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
ether <TRUE MAC ADDRESS OF MY CARD> txqueuelen 1000 (Ethernet)
RX packets 375891 bytes 523426707 (499.1 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 145987 bytes 12280970 (11.7 MiB)
TX errors 1 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 1167 bytes 190105 (185.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1167 bytes 190105 (185.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 26:d2:a7:1b:7f:2b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Even after issuing a ifconfig wlp4s0 down, after a minute or so it is created again. Commands ls /etc/sysconfig/network-scripts | grep wlp4s0 and grep wlp4s0 /etc/sysconfig/network-scripts/* give nothing.



I rename the network card with the following /etc/udev/rules.d/70-persistent-net.rules file:



SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="78:2B:CB:ED:14:07", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


What should I do to prevent this from happening? Why is it creating a new network device?










share|improve this question



























    0














    I upgraded to Fedora 29 recently, and it keeps creating a fake network device wlp4s0 with a different fake macaddress every time:



    > ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
    ether <TRUE MAC ADDRESS OF MY CARD> txqueuelen 1000 (Ethernet)
    RX packets 375891 bytes 523426707 (499.1 MiB)
    RX errors 0 dropped 3 overruns 0 frame 0
    TX packets 145987 bytes 12280970 (11.7 MiB)
    TX errors 1 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    loop txqueuelen 1000 (Local Loopback)
    RX packets 1167 bytes 190105 (185.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1167 bytes 190105 (185.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether 26:d2:a7:1b:7f:2b txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    Even after issuing a ifconfig wlp4s0 down, after a minute or so it is created again. Commands ls /etc/sysconfig/network-scripts | grep wlp4s0 and grep wlp4s0 /etc/sysconfig/network-scripts/* give nothing.



    I rename the network card with the following /etc/udev/rules.d/70-persistent-net.rules file:



    SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="78:2B:CB:ED:14:07", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


    What should I do to prevent this from happening? Why is it creating a new network device?










    share|improve this question

























      0












      0








      0







      I upgraded to Fedora 29 recently, and it keeps creating a fake network device wlp4s0 with a different fake macaddress every time:



      > ifconfig
      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
      ether <TRUE MAC ADDRESS OF MY CARD> txqueuelen 1000 (Ethernet)
      RX packets 375891 bytes 523426707 (499.1 MiB)
      RX errors 0 dropped 3 overruns 0 frame 0
      TX packets 145987 bytes 12280970 (11.7 MiB)
      TX errors 1 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      loop txqueuelen 1000 (Local Loopback)
      RX packets 1167 bytes 190105 (185.6 KiB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 1167 bytes 190105 (185.6 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      wlp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
      ether 26:d2:a7:1b:7f:2b txqueuelen 1000 (Ethernet)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 0 bytes 0 (0.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      Even after issuing a ifconfig wlp4s0 down, after a minute or so it is created again. Commands ls /etc/sysconfig/network-scripts | grep wlp4s0 and grep wlp4s0 /etc/sysconfig/network-scripts/* give nothing.



      I rename the network card with the following /etc/udev/rules.d/70-persistent-net.rules file:



      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="78:2B:CB:ED:14:07", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


      What should I do to prevent this from happening? Why is it creating a new network device?










      share|improve this question













      I upgraded to Fedora 29 recently, and it keeps creating a fake network device wlp4s0 with a different fake macaddress every time:



      > ifconfig
      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
      ether <TRUE MAC ADDRESS OF MY CARD> txqueuelen 1000 (Ethernet)
      RX packets 375891 bytes 523426707 (499.1 MiB)
      RX errors 0 dropped 3 overruns 0 frame 0
      TX packets 145987 bytes 12280970 (11.7 MiB)
      TX errors 1 dropped 0 overruns 0 carrier 0 collisions 0

      lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      inet 127.0.0.1 netmask 255.0.0.0
      loop txqueuelen 1000 (Local Loopback)
      RX packets 1167 bytes 190105 (185.6 KiB)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 1167 bytes 190105 (185.6 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      wlp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
      ether 26:d2:a7:1b:7f:2b txqueuelen 1000 (Ethernet)
      RX packets 0 bytes 0 (0.0 B)
      RX errors 0 dropped 0 overruns 0 frame 0
      TX packets 0 bytes 0 (0.0 B)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      Even after issuing a ifconfig wlp4s0 down, after a minute or so it is created again. Commands ls /etc/sysconfig/network-scripts | grep wlp4s0 and grep wlp4s0 /etc/sysconfig/network-scripts/* give nothing.



      I rename the network card with the following /etc/udev/rules.d/70-persistent-net.rules file:



      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="78:2B:CB:ED:14:07", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


      What should I do to prevent this from happening? Why is it creating a new network device?







      linux networking fedora






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 11 hours ago









      Luis A. Florit

      1436




      1436



























          active

          oldest

          votes











          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%2f490505%2fprevent-fedora-29-from-creating-fake-network-device%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 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.





          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%2funix.stackexchange.com%2fquestions%2f490505%2fprevent-fedora-29-from-creating-fake-network-device%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

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt