From: pgnd <pgnd@dev-mail.net>
To: linux-hotplug@vger.kernel.org
Subject: udev rule in /etc/udev/rules.d/ FAILS to exec on boot; but OK exec @ shell after boot ?
Date: Wed, 20 Dec 2023 19:33:06 -0500 [thread overview]
Message-ID: <fb9f85b9-cb79-427c-862f-bd33afe2fcbf@dev-mail.net> (raw)
hi,
on
lsb_release -rd
Description: Fedora release 39 (Thirty Nine)
Release: 39
uname -rm
6.6.6-200.fc39.x86_64 x86_64
i have this net device
lspci | grep Ethernet | grep 05:00
05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
i enable persistent naming; in kernel cmdline,
"... net.ifnames=1 ..."
the interface is renamed/created during boot
dmesg | grep "renamed from eth"
[ 6.945108] igb 0000:05:00.0 enp5s0: renamed from eth0
i've created a udev rule to set IPv6 params
cat /etc/udev/rules.d/01-enp5s0-sysctl.rules
ACTION=="add|bind|change", SUBSYSTEM=="net", KERNEL=="enp5s0", \
RUN+="/sbin/sysctl -qw \
net.ipv6.conf.enp5s0.forwarding=0 \
net.ipv6.conf.enp5s0.accept_ra=1 \
net.ipv6.conf.enp5s0.use_tempaddr=1 \
"
but, immediately after boot, exec
sysctl \
net.ipv6.conf.enp5s0.forwarding \
net.ipv6.conf.enp5s0.accept_ra \
net.ipv6.conf.enp5s0.use_tempaddr
returns the values, unchanged,
net.ipv6.conf.enp5s0.forwarding = 0
net.ipv6.conf.enp5s0.accept_ra = 0
net.ipv6.conf.enp5s0.use_tempaddr = 0
otoh, if i exec at shell,
udevadm trigger
sysctl \
net.ipv6.conf.enp5s0.forwarding \
net.ipv6.conf.enp5s0.accept_ra \
net.ipv6.conf.enp5s0.use_tempaddr
the values are changed
net.ipv6.conf.enp5s0.forwarding = 0
net.ipv6.conf.enp5s0.accept_ra = 1
net.ipv6.conf.enp5s0.use_tempaddr = 1
what's keeping my udev rule from setting up the interface sysctls on boot?
-pgnd
next reply other threads:[~2023-12-21 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 0:33 pgnd [this message]
2023-12-21 8:17 ` udev rule in /etc/udev/rules.d/ FAILS to exec on boot; but OK exec @ shell after boot ? Greg KH
2023-12-21 12:25 ` pgnd
2023-12-21 13:21 ` pgnd
2023-12-21 13:22 ` Andrei Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb9f85b9-cb79-427c-862f-bd33afe2fcbf@dev-mail.net \
--to=pgnd@dev-mail.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.