#37 Networking problems (increment network adpters on boot)

open
nobody
5
2014-08-15
2008-03-23
Anonymous
No

colinux: 0.7.3
kernel: 2.6.22.18

I have a dual boot WinXP Pro SP2 and OpenSUSE 10.2. I try to use Colinux with SUSE. I created file settings.txt:

mem=512
root=/dev/cobd4
kernel=vmlinux
cobd3=\Device\Harddisk0\Partition3
cobd4=\Device\Harddisk0\Partition4
eth0=tuntap
eth1=slirp

At this time of my works, I have a device eth47 and eth48. After boot, the eth device appear to be increase by one or two or any number, base to the number of network device in the file settings.txt. I can add manually eth0 and eth1, but I can't ifup it. eth45 and eth46 appear automatically, no ifup
necessary,when I use ifconfig -a.

Thanks for help

Discussion

  • Henry N.
    Henry N.
    2008-03-24

    Logged In: YES
    user_id=579204
    Originator: NO

    It's the same as in https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063

    Without MAC, SuSE detects *new* cards on every boot.

    You needs to set unique MAC for every ethX device.
    Than search for saved networks in files under /etc. I don't know where it is. But, SuSE also save every new MAC in one file.

     
  • Henry N.
    Henry N.
    2008-03-24

    Logged In: YES
    user_id=579204
    Originator: NO

    In the file /etc/udev/rules.d/70-persistent-net.rules needs to remove all such lines:
    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:22:33:44:55", NAME="eth0"
    After the next reboot should have eth0 and eth1 and no increasing any more.

    But, I not understand why a change in the 0.7.3 doesn't fix the increasing networks.
    Version 0.7.3 build after 2008-03-02 (SVN r932) should fix it. Please check this registry key:
    [HKEY_CURRENT_USER\Software\coLinux\monitor\M\ethX] "mac"="00:ff:XX:XX:XX:XX"
    (M=Monitor number, X=network device number)
    Exist such registry key?
    Or do you used an older build? (please version check with "uname -a")

     
  • Logged In: NO

    In file /etc/udev/rules.d/30-net_persistent_names.rules, I founded more than 40 lines like this: SUBSYSTEM=="net",ACTION=="add",... I deleted all lines.

    In file /etc/udev/rules.d/31-network.rules I commented the lines:
    SUBSYSTEM=="net",ACTION=="add",ENV(RENAMED)!= "yes",IMPORT="/lib/udev/rename_netiface %k"

    This two things fix my problems.

    Thanks.

     
  • Henry N.
    Henry N.
    2008-03-29

    • summary: Nerworking problems --> Nerworking problems (increment network adpters on boot)
     
  • Henry N.
    Henry N.
    2009-06-29

    To allow dual boot you can bypass the rename only for coLinux by adding a line with DRIVER "conet" to the file net_persistent_names.rules some there in top of file where other skips exist:

    # ignore "conet" interfaces
    DRIVERS=="conet" GOTO="persistent_net_generator_end"

    For Debian 4.0 insert the '+' marked lines into file /etc/udev/rules.d/z45_persistent-net-generator.rules near line 15:

    `
    # ignore "secondary" raw interfaces of the madwifi driver
    KERNEL=="ath*", ATTRS{type}=="802", GOTO="persistent_net_generator_end"
    +
    +# ignore "conet" interfaces
    +DRIVERS=="conet", GOTO="persistent_net_generator_end"
    +
    # provide nice comments for the generated rules
    SUBSYSTEMS=="pci", \ ENV{COMMENT}="PCI device $attr{vendor}:$attr{device}"
    `

    For Ubuntu 8.1 insert '+' marked lines into file /etc/udev/rules.d/75-persistent-net-generator.rules at line 26:

    `
    # ignore Xen virtual interfaces
    SUBSYSTEMS=="xen", GOTO="persistent_net_generator_end"
    +
    +# Do not rename coLinux network devices
    +DRIVERS=="conet", GOTO="persistent_net_generator_end"
    +
    # read MAC address
    ENV{MATCHADDR}="$attr{address}"
    `

     
  • Henry N.
    Henry N.
    2009-06-29

    • summary: Nerworking problems (increment network adpters on boot) --> Networking problems (increment network adpters on boot)