Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: OS13.1 Network detection does not work

  1. #1
    Join Date
    Apr 2013
    Location
    Frankfurt, Germany
    Posts
    54

    Default OS13.1 Network detection does not work

    Hello,
    i tried to install openSUSE 13.1 with command line
    splash=0 vga=0x317 net.ifnames=0 ipv6.disable_ipv6=0 nomodeset

    The network is configured during installation, access is possible.
    After a reboot ifconfig shows interfaces, but access is not possible.
    /etc/udev/rules.d/70-persistent-net.rules is empty, but in
    /etc/sysconfig/network there are the ifcfg-files.

    What can i do?

    Host is openSUSE 12.2 with Virtualbox 4.3.6

    Best regards

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: OS13.1 Network detection does not work

    Predictable naming is now being used with systemd/udev enabled and
    persistent naming has been dropped. Explained here
    https://bugzilla.novell.com/show_bug.cgi?id=845649

    However, you can reinstate the persistent network naming if you prefer.

  3. #3
    Join Date
    Apr 2013
    Location
    Frankfurt, Germany
    Posts
    54

    Default Re: OS13.1 Network detection does not work

    Thanks for your answer.

    I read this about persistent naming:
    http://www.freedesktop.org/wiki/Soft...nterfaceNames/
    https://fedoraproject.org/wiki/Talk:...rkDeviceNaming

    But i tried to use the old style with kernel-commmand-line:
    splash=0 vga=0x317 net.ifnames=0 ipv6.disable_ipv6=0 nomodeset
    at boot time / minimal installation.

    Where the names stored?
    ntop, for example, looks for the eth devices.
    And what about smb.conf:
    interfaces = eth* lo
    ?

    Best regards

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: OS13.1 Network detection does not work

    I don't think that openSUSE is using /etc/udev/rules.d/70-persistent-net.rules anymore in 13.1.

    Recommend if you're able to do a non-network install (You ought to still be able to access source in your LAN if necessary by providing a working pre-boot that supports networking)
    The network connection should then be set up automatically. If it's not, then you should be able to use YAST to modify.

    Also, since you're using Virtualbox, aren't you going about this wrong?
    If this is a new install, you should be pointing the install source in the Guest properties, not in the command line to install

    IMO,
    TSU

  5. #5
    Join Date
    Apr 2013
    Location
    Frankfurt, Germany
    Posts
    54

    Default Re: OS13.1 Network detection does not work

    Quote Originally Posted by tsu2 View Post
    I don't think that openSUSE is using /etc/udev/rules.d/70-persistent-net.rules anymore in 13.1.

    Recommend if you're able to do a non-network install (You ought to still be able to access source in your LAN if necessary by providing a working pre-boot that supports networking)
    The network connection should then be set up automatically. If it's not, then you should be able to use YAST to modify.

    Also, since you're using Virtualbox, aren't you going about this wrong?
    If this is a new install, you should be pointing the install source in the Guest properties, not in the command line to install

    IMO,
    TSU
    ok guys, what's the problem?
    I try to install openSUSE 13.1 inside Virtualbox.
    Network connections are available during installation, but after the last boot
    they are not.
    Again: older version don't have this problem.
    I installed openSUSE 13.1 yesterday on real hardware with old naming scheme,
    this worked for a while, samba-performance on copy was very good.
    I tried to change the names to the new naming scheme, so the names are not
    predictable! On 3 attempts i got 3 differrent names.
    Also the samba performance wehre very bad.
    Therefor i want to have the old naming scheme with stable funtionality.

    Best regards

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: OS13.1 Network detection does not work

    Quote Originally Posted by AchimKl View Post
    ok guys, what's the problem?
    I try to install openSUSE 13.1 inside Virtualbox.
    Network connections are available during installation, but after the last boot
    they are not.
    Again: older version don't have this problem.
    I installed openSUSE 13.1 yesterday on real hardware with old naming scheme,
    this worked for a while, samba-performance on copy was very good.
    I tried to change the names to the new naming scheme, so the names are not
    predictable! On 3 attempts i got 3 differrent names.
    Also the samba performance wehre very bad.
    Therefor i want to have the old naming scheme with stable funtionality.

    Best regards
    They sound like separate issues to me, but perhaps someone else may offer clues.

    Anyway, to answer your question about re-instating persistent naming, you need

    1)The kernel parameter (as you already mentioned)
    Code:
    net.ifnames=0
    2) A valid rules file (eg /etc/udev/rules.d/70-persistent-net.rules), with interfaces uniquely identified by the hardware MAC address. For example, I tested my wired interface with the following rule

    Code:
    SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:1C:C4:CF:63:7A", NAME="eth0"
    When I booted, I now have the following reported
    Code:
    # ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:1C:C4:CF:63:7A  
              inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:815 errors:0 dropped:0 overruns:0 frame:0
              TX packets:897 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:301364 (294.3 Kb)  TX bytes:156937 (153.2 Kb)
              Interrupt:18 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:74 errors:0 dropped:0 overruns:0 frame:0
              TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:6676 (6.5 Kb)  TX bytes:6676 (6.5 Kb)
    I'm using network manager, so the changes work seamlessly. Now I will revert to predictable names again (as I only did this to help you).
    Last edited by deano_ferrari; 07-Feb-2014 at 00:20.

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: OS13.1 Network detection does not work

    Interesting you created an entry in "70-persistent-net.rules" file and got it to work, when I looked at that file awhile back and found it empty, it surprised me (it's been populated in earlier openSUSE and is still used in other distros) but I didn't have the courage then to move ahead and test a configuration like you did.

    When I saw it empty, I found what I thought would be relevant entries in
    /etc/sysconfig/network/config

    But, when I looked closer at the settings, they aren't necessarily consistent with what exists.
    So, it's still unknown to me where these kinds of networking configurations are being made(maybe more clues would be in the network.service Unit file)

    So, if someone who knows what is changing in the network subsystem configuration, it would be nice to know.

    TSU

  8. #8

    Default Re: OS13.1 Network detection does not work

    Quote Originally Posted by tsu2 View Post
    Interesting you created an entry in "70-persistent-net.rules" file and got it to work, when I looked at that file awhile back and found it empty, it surprised me (it's been populated in earlier openSUSE and is still used in other distros) but I didn't have the courage then to move ahead and test a configuration like you did.
    If you change the interface name in YaST->Network Devices->Network Settings, this is stored in "70-persistent-net.rules". You don't have to create the rules yourself.
    To do this, select the interface on the "Overview" tab, click on "Edit", switch to the "Hardware" tab and click on "Change" next to the device name.

    And no, "70-persistent-net.rules" DOES NOT contain any configuration. The configurations are in /etc/sysconfig/network/. "70-persistent-net.rules" only contains rules for the naming of the interfaces.

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: OS13.1 Network detection does not work

    Quote Originally Posted by tsu2 View Post
    Interesting you created an entry in "70-persistent-net.rules" file and got it to work, when I looked at that file awhile back and found it empty, it surprised me (it's been populated in earlier openSUSE and is still used in other distros) but I didn't have the courage then to move ahead and test a configuration like you did.

    When I saw it empty, I found what I thought would be relevant entries in
    /etc/sysconfig/network/config

    But, when I looked closer at the settings, they aren't necessarily consistent with what exists.
    So, it's still unknown to me where these kinds of networking configurations are being made(maybe more clues would be in the network.service Unit file)

    So, if someone who knows what is changing in the network subsystem configuration, it would be nice to know.

    TSU
    It's well explained here

    http://www.freedesktop.org/wiki/Soft...nterfaceNames/

    What precisely has changed in v197?

    With systemd 197 we have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's (but generally more powerful, and closer to kernel-internal device identification schemes) the default. The following different naming schemes for network interfaces are now supported by udev natively:



    1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
    2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
    3. Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
    4. Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
    5. Classic, unpredictable kernel-native ethX naming (example: eth0)

    By default, systemd v197 will now name interfaces following policy 1) if that information from the firmware is applicable and available, falling back to 2) if that information from the firmware is applicable and available, falling back to 3) if applicable, falling back to 5) in all other cases. Policy 4) is not used by default, but is available if the user chooses so.
    This combined policy is only applied as last resort. That means, if the system has biosdevname installed, it will take precedence. If the user has added udev rules which change the name of the kernel devices these will take precedence too. Also, any distribution specific naming schemes generally take precedence.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,710
    Blog Entries
    1

    Default Re: OS13.1 Network detection does not work

    If you change the interface name in YaST->Network Devices->Network Settings, this is stored in "70-persistent-net.rules". You don't have to create the rules yourself.
    That, I didn't realise.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •