[Bug 1102128] New: values at sysctl.conf don't override default kernel parameter values
http://bugzilla.suse.com/show_bug.cgi?id=1102128 Bug ID: 1102128 Summary: values at sysctl.conf don't override default kernel parameter values Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: denis.polom@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- my sysctl.conf: --- net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 --- after booting: --- # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:a4:71:15:26:71 brd ff:ff:ff:ff:ff:ff inet 192.168.1.237/24 brd 192.168.88.255 scope global dynamic noprefixroute wlp2s0 valid_lft 407sec preferred_lft 407sec inet6 fe80::d74b:c12f:6ad7:879b/64 scope link noprefixroute valid_lft forever preferred_lft forever --- after running command 'sysctl -p' kernel parameters are set vith values from sysctl.conf --- 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e4:a4:71:15:26:71 brd ff:ff:ff:ff:ff:ff inet 192.168.1.237/24 brd 192.168.88.255 scope global dynamic noprefixroute wlp2s0 valid_lft 548sec preferred_lft 548sec --- -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 Denis Polom <denis.polom@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|values at sysctl.conf don't |values at sysctl.conf don't |override default kernel |override default kernel |parameter values |parameter values after | |server boots -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 http://bugzilla.suse.com/show_bug.cgi?id=1102128#c1 Michal Kubeček <mkubecek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek@suse.com --- Comment #1 from Michal Kubeček <mkubecek@suse.com> --- (In reply to Denis Polom from comment #0)
after running command 'sysctl -p' kernel parameters are set vith values from sysctl.conf
This doesn't really look like a kernel issue, rather something else rewriting the sysctl values again on boot. I suggest to check the sysctl values after booting; if they are 0, you should try to find who resets them back to 0. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |denis.polom@suse.com, | |tiwai@suse.com Flags| |needinfo?(denis.polom@suse. | |com) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 http://bugzilla.suse.com/show_bug.cgi?id=1102128#c2 --- Comment #2 from Denis Polom <denis.polom@suse.com> --- (In reply to Michal Kubeček from comment #1)
(In reply to Denis Polom from comment #0)
after running command 'sysctl -p' kernel parameters are set vith values from sysctl.conf
This doesn't really look like a kernel issue, rather something else rewriting the sysctl values again on boot. I suggest to check the sysctl values after booting; if they are 0, you should try to find who resets them back to 0.
tell me what logs you need or what commands outputs you need to troubleshoot it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 http://bugzilla.suse.com/show_bug.cgi?id=1102128#c3 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Reassigned to procps maintainer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 http://bugzilla.suse.com/show_bug.cgi?id=1102128#c4 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com Assignee|werner@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #4 from Dr. Werner Fink <werner@suse.com> --- I do not get the problem. If systemctl is called *afer* all configurations (e.g. at boot) are done then it works ... is this correct? In other words, even if the configurations in /etc/sysctl.conf can be written as the sysctl files /proc/sys/net/ipv6/conf/all/disable_ipv6 /proc/sys/net/ipv6/conf/default/disable_ipv6 /proc/sys/net/ipv6/conf/lo/disable_ipv6 those files will be set by e.g. wicked and/or NetworkManager and/or systemd-networkd *after* systemd-sysctl.service had been called. IMHO this has nothing todo with sysctl nor procps ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102128 http://bugzilla.suse.com/show_bug.cgi?id=1102128#c6 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mt@suse.com Resolution|--- |WORKSFORME Flags|needinfo?(denis.polom@suse. | |com) | --- Comment #6 from Marius Tomaschewski <mt@suse.com> --- Adding of a /etc/sysctl.d/50-ipv6.conf or also /etc/sysctl.conf works fine: net.ipv6.conf.lo.disable_ipv6 = 1 net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com