[Bug 1203420] New: [At Boot] /etc/sysctl.d/*.conf being ignored
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 Bug ID: 1203420 Summary: [At Boot] /etc/sysctl.d/*.conf being ignored Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: dev.dorrejo@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hello, i am settings some param, including disabling ipv6, but when i boot the system those files are ignored, including the one created by yast, when for example, disable ipv6 using yast2, the param of the 70-yast.conf it change and applied, but when reboot the system, it would not be applied. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c3 --- Comment #3 from Walddys Emmanuel Dorrejo C�spedes <dev.dorrejo@gmail.com> --- (In reply to Franck Bui from comment #2)
Please attach the output of `systemd-analyze cat-config sysctl.d`
Sorry for the late reply. i execute the file and is read, but for example if i apply net.ipv6.conf.all.disable_ipv6=1 using yast2 it will apply immediately, but if i reboot the system the ipv6 will still appear, and the command will show that systemd read the file, but ipv6 still is enabled. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c4 --- Comment #4 from Franck Bui <fbui@suse.com> --- Can you show the output of `systemctl status systemd-sysctl.service` ? What if you restart this service with `systemctl restart systemd-sysctl.service` ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c5 --- Comment #5 from Walddys Emmanuel Dorrejo C��spedes <dev.dorrejo@gmail.com> --- (In reply to Franck Bui from comment #4)
Can you show the output of `systemctl status systemd-sysctl.service` ?
What if you restart this service with `systemctl restart systemd-sysctl.service` ?
it wont apply the changes of the sysctl: ��� ip a 2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 30:9c:23:8f:08:49 brd ff:ff:ff:ff:ff:ff 3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:ec:c5:49:ab:c9 brd ff:ff:ff:ff:ff:ff altname wlp0s20f3 inet 192.168.2.7/24 brd 192.168.2.255 scope global dynamic noprefixroute wlo1 valid_lft 84340sec preferred_lft 84340sec inet6 fe80::368b:877a:a00:807b/64 scope link noprefixroute valid_lft forever preferred_lft forever ��� cat /etc/sysctl.d/70-yast.conf net.ipv4.ip_forward = 0 net.ipv6.conf.all.forwarding = 0 net.ipv6.conf.all.disable_ipv6 = 1 ��� systemctl status systemd-sysctl.service ��� systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static) Drop-In: /usr/lib/systemd/system/systemd-sysctl.service.d ������50-kernel-uname_r.conf Active: active (exited) since Mon 2022-10-17 08:53:23 AST; 5h 23min ago Docs: man:systemd-sysctl.service(8) man:sysctl.d(5) Main PID: 662 (code=exited, status=0/SUCCESS) CPU: 4ms Oct 17 08:53:23 TW-MSI systemd[1]: Starting Apply Kernel Variables... Oct 17 08:53:23 TW-MSI systemd-sysctl[662]: Couldn't write '0' to 'dev/i915/perf_stream_paranoid', ignoring: No such file or directory Oct 17 08:53:23 TW-MSI systemd[1]: Finished Apply Kernel Variables. ��� sudo systemctl restart systemd-sysctl.service ��� systemctl status systemd-sysctl.service ��� systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static) Drop-In: /usr/lib/systemd/system/systemd-sysctl.service.d ������50-kernel-uname_r.conf Active: active (exited) since Mon 2022-10-17 14:17:03 AST; 2s ago Docs: man:systemd-sysctl.service(8) man:sysctl.d(5) Process: 4366 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS) Main PID: 4366 (code=exited, status=0/SUCCESS) CPU: 18ms Oct 17 14:17:03 TW-MSI systemd[1]: Starting Apply Kernel Variables... Oct 17 14:17:03 TW-MSI systemd[1]: Finished Apply Kernel Variables. ��� ip a 2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 30:9c:23:8f:08:49 brd ff:ff:ff:ff:ff:ff 3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:ec:c5:49:ab:c9 brd ff:ff:ff:ff:ff:ff altname wlp0s20f3 inet 192.168.2.7/24 brd 192.168.2.255 scope global dynamic noprefixroute wlo1 valid_lft 84299sec preferred_lft 84299sec inet6 fe80::368b:877a:a00:807b/64 scope link noprefixroute valid_lft forever preferred_lft forever -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c6 --- Comment #6 from Franck Bui <fbui@suse.com> --- Please attach the output of `SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-sysctl` And also the one for `cat /proc/sys/net/ipv6/conf/all/disable_ipv6` -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c7 --- Comment #7 from Walddys Emmanuel Dorrejo C�spedes <dev.dorrejo@gmail.com> --- Created attachment 862244 --> http://bugzilla.opensuse.org/attachment.cgi?id=862244&action=edit SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-sysctl cat /proc/sys/net/ipv6/conf/all/disable_ipv6 1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c8 --- Comment #8 from Franck Bui <fbui@suse.com> --- (In reply to Walddys Emmanuel Dorrejo C�spedes from comment #7)
cat /proc/sys/net/ipv6/conf/all/disable_ipv6 1
So as far as systemd-sysctl is concerned, everything worked just fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c9 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |tiwai@suse.com --- Comment #9 from Franck Bui <fbui@suse.com> --- Takashi, can you please take over ? See the previous comment, systemd-sysctl wrote '1' in /proc/sys/net/ipv6/conf/all/disable_ipv6 but according to Walddys ipv6 is still not disabled. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c10 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tiwai@suse.com |jbohac@suse.com --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- I guess Jiri should have a better clue. Tossed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c21 --- Comment #21 from Walddys Emmanuel Dorrejo C�spedes <dev.dorrejo@gmail.com> --- Hello, Thanks for the hard work and understanding, and the teaching about this kind of information that complement the understanding of the solution/answer given. i understand and found (is) valid the quick response that you found and show me. So to put it simple, if i am using NetworkManager, to disable IPv6 or any related to interface params, have to use NetworkManager, because at boot and in other init, it will overwrite/enforce they configuration. thank you very much for you time team. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c22 --- Comment #22 from Walddys Emmanuel Dorrejo C�spedes <dev.dorrejo@gmail.com> --- last question, if possible, why Tumbleweed change from wicked to NM? and Wicked will stay alive? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203420 http://bugzilla.opensuse.org/show_bug.cgi?id=1203420#c24 --- Comment #24 from Walddys Emmanuel Dorrejo C�spedes <dev.dorrejo@gmail.com> --- (In reply to Jiri Bohac from comment #23)
OK, closing as Invalid, thanks for confirming that disabling IPv6 in NM works!
(In reply to Walddys Emmanuel Dorrejo C�spedes from comment #22)
last question, if possible, why Tumbleweed change from wicked to NM?
and Wicked will stay alive?
I can not give you an authoritative answer. Just that I can see reasons to drop wicked in the long run: SUSE started the wicked project when NM was not nearly capable of managing complicated network setups required by our enterprise customers. Since then NM has evolved. It is quite possible it would be capable enough now. And and then it makes sense to question investing in the SUSE-specific wicked instead of using NM that everyone else uses, with a functional upstream community. I don't know what the decisions will be, but I don't think users need to worry too much: wicked won't be taken away until NM is believed by experts to be a good enough replacement :)
Thank you very much, and appreciate the time you take for enlighten me with wicked and NM. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com