Forum Debian Users Gang

lewyx84 · 2016-02-18 22:10:03

Czołem,
po którymś restarcie zamiast eth1, pojawił mi się eth2. Dokonałem więc zmian w /etc/udev/rules.d/70-persistent-net.rules, zamieniając eth2, na eth1

Kod:

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:4c:68:05:e3", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x167a (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="F8:D1:11:3F:F5:81", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

strzeliłem sobie restarcik i lipton :) Dalej mam eth2 :)
W sumie nie ma to żadnego znaczenia, ot, takie widzimisię :)

Pzdr

Jacekalex · 2016-02-19 01:22:51

Spróbuj zmienić nazwę pliku na:

Kod:

/etc/udev/rules.d/80-net-setup-link.rules

u mnie na testingu amd64 (Stretch) to pomogło.

Ostatnio edytowany przez Jacekalex (2016-02-19 01:29:55)

yossarian · 2016-02-19 14:03:04

Trzeba było czytać informacje przy aktualizacji udeva:

/usr/share/doc/udev/README.Debian.gz napisał(-a):
Legacy persistent network interface naming
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Debian releases up to 8 ("Jessie") and Ubuntu up to 15.04 had an udev rule
/lib/udev/rules.d/75-persistent-net-generator.rules which fixed the name of a
network interface that it got when its MAC address first appeared in a
dynamically created /etc/udev/rules.d/70-persistent-net.rules file.

This had inherent race conditions (which sometimes caused collisions and
interface names like "rename1"), required having to write state into /etc
(which isn't possible for read-only root), and did not work in virtualized
environments.

This old schema is deprecated in Debian 9 ("Stretch"), and will not
be supported any more in Debian 10.

[…]

Custom net interface naming
~~~~~~~~~~~~~~~~~~~~~~~~~~~
In some cases it is convenient to define your own specific names for network
interfaces. These can be customized in two different ways:

* You can create your own names via udev rules, based on arbitrary attribute
and property matches. See man udev(7) for documentation how to write udev
rules. For example, you can create /etc/udev/rules.d/76-netnames.rules with

------------ snip ----------
# identify device by MAC address
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="11:22:aa:bb:cc:33", NAME="eth-dmz"

# identify by vendor/model ID
SUBSYSTEM=="net", ACTION=="add", ENV{ID_VENDOR_ID}=="0x8086", \
ENV{ID_MODEL_ID}=="0x1502", NAME="eth-intel-gb"

# USB device by path
# get ID_PATH if not present yet
ENV{ID_PATH}=="", IMPORT{builtin}="path_id"
SUBSYSTEM=="net", ACTION=="add", ENV{ID_PATH}=="*-usb-0:3:1*", NAME="eth-blue-hub"
------------ snip ----------

The name of the rules file needs to have a prefix smaller than "80" so that
it runs before /lib/udev/rules.d/80-net-setup-link.rules, and should have a
prefix bigger than "75" so that it runs after 75-net-description.rules and
thus you can use matches on ID_VENDOR and similar properties.

* Unless you disabled net.ifnames, you can change the policy
(kernel/bios/path/MAC based naming) in an /etc/systemd/network/*.link file,
for individual devices or entire device classes. See man systemd.link(5) for
details about this. /lib/systemd/network/99-default.link is the default
policy, and /lib/systemd/network/01-mac-for-usb.link makes it use MAC based
names for USB devices.

Any of the above changes require an initrd update with "update-initramfs -u" to
get effective.

Forum Debian Users Gang

Ogłoszenie

#1 2016-02-18 22:10:03

lewyx84 - Użytkownik

Zmiana w 70-persistent-net.rules - brak reakcji

Kod:

#2 2016-02-19 01:22:51

Jacekalex - Podobno człowiek...;)

Re: Zmiana w 70-persistent-net.rules - brak reakcji

Kod:

#3 2016-02-19 14:03:04

yossarian - Szczawiożerca

Re: Zmiana w 70-persistent-net.rules - brak reakcji

/usr/share/doc/udev/README.Debian.gz napisał(-a):

Stopka forum