empty 70-persistent-net.rules on SuSe 13.1 and ethernet device called eno1












2















openSuse 13.1 configured my network controller as eno1 during installation.



Also eno1 device can not be configured by KDE Network Connection tool, it doesn't allow you to add a connection for this device.



When i check the 70-persistent-net.rules it's blank. I would like to rename it as eth0 but also i couldn't. I have to find a way to enable KDE Network Connection tool configuration because i will not use the machine.










share|improve this question














bumped to the homepage by Community 2 hours ago


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






migrated from serverfault.com Jan 2 '15 at 23:03


This question came from our site for system and network administrators.



















  • What do you mean you couldn't? What did you try?

    – Andrew Schulman
    Jan 2 '15 at 18:47











  • @AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

    – yet
    Jan 2 '15 at 18:49
















2















openSuse 13.1 configured my network controller as eno1 during installation.



Also eno1 device can not be configured by KDE Network Connection tool, it doesn't allow you to add a connection for this device.



When i check the 70-persistent-net.rules it's blank. I would like to rename it as eth0 but also i couldn't. I have to find a way to enable KDE Network Connection tool configuration because i will not use the machine.










share|improve this question














bumped to the homepage by Community 2 hours ago


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






migrated from serverfault.com Jan 2 '15 at 23:03


This question came from our site for system and network administrators.



















  • What do you mean you couldn't? What did you try?

    – Andrew Schulman
    Jan 2 '15 at 18:47











  • @AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

    – yet
    Jan 2 '15 at 18:49














2












2








2








openSuse 13.1 configured my network controller as eno1 during installation.



Also eno1 device can not be configured by KDE Network Connection tool, it doesn't allow you to add a connection for this device.



When i check the 70-persistent-net.rules it's blank. I would like to rename it as eth0 but also i couldn't. I have to find a way to enable KDE Network Connection tool configuration because i will not use the machine.










share|improve this question














openSuse 13.1 configured my network controller as eno1 during installation.



Also eno1 device can not be configured by KDE Network Connection tool, it doesn't allow you to add a connection for this device.



When i check the 70-persistent-net.rules it's blank. I would like to rename it as eth0 but also i couldn't. I have to find a way to enable KDE Network Connection tool configuration because i will not use the machine.







networking ethernet opensuse kde






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 2 '15 at 18:26







yet












bumped to the homepage by Community 2 hours 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 2 hours ago


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






migrated from serverfault.com Jan 2 '15 at 23:03


This question came from our site for system and network administrators.









migrated from serverfault.com Jan 2 '15 at 23:03


This question came from our site for system and network administrators.















  • What do you mean you couldn't? What did you try?

    – Andrew Schulman
    Jan 2 '15 at 18:47











  • @AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

    – yet
    Jan 2 '15 at 18:49



















  • What do you mean you couldn't? What did you try?

    – Andrew Schulman
    Jan 2 '15 at 18:47











  • @AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

    – yet
    Jan 2 '15 at 18:49

















What do you mean you couldn't? What did you try?

– Andrew Schulman
Jan 2 '15 at 18:47





What do you mean you couldn't? What did you try?

– Andrew Schulman
Jan 2 '15 at 18:47













@AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

– yet
Jan 2 '15 at 18:49





@AndrewSchulman i think it's my fault it's written properly when i configured it via YaST ->NetworkDevices->NetworkSettings.

– yet
Jan 2 '15 at 18:49










1 Answer
1






active

oldest

votes


















0














I managed to do it via YaST2->Network Devices->Network Settings->overview tab :



you can rename the device.



Also if you want to enable KDE or Gnome network configuration applet, you need to enable



YaST2->Network Devices->Network Settings->Global Options: Control by applet.






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%2f177120%2fempty-70-persistent-net-rules-on-suse-13-1-and-ethernet-device-called-eno1%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














    I managed to do it via YaST2->Network Devices->Network Settings->overview tab :



    you can rename the device.



    Also if you want to enable KDE or Gnome network configuration applet, you need to enable



    YaST2->Network Devices->Network Settings->Global Options: Control by applet.






    share|improve this answer




























      0














      I managed to do it via YaST2->Network Devices->Network Settings->overview tab :



      you can rename the device.



      Also if you want to enable KDE or Gnome network configuration applet, you need to enable



      YaST2->Network Devices->Network Settings->Global Options: Control by applet.






      share|improve this answer


























        0












        0








        0







        I managed to do it via YaST2->Network Devices->Network Settings->overview tab :



        you can rename the device.



        Also if you want to enable KDE or Gnome network configuration applet, you need to enable



        YaST2->Network Devices->Network Settings->Global Options: Control by applet.






        share|improve this answer













        I managed to do it via YaST2->Network Devices->Network Settings->overview tab :



        you can rename the device.



        Also if you want to enable KDE or Gnome network configuration applet, you need to enable



        YaST2->Network Devices->Network Settings->Global Options: Control by applet.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 2 '15 at 18:48







        yet





































            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%2f177120%2fempty-70-persistent-net-rules-on-suse-13-1-and-ethernet-device-called-eno1%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

            CARDNET

            Boot-repair Failure: Unable to locate package grub-common:i386

            Aws NAT - Aws IGW- Aws router