Hi Lennart/Andrey, Your pointers led me to the right direction thanks a lot. I was indeed using an older version of connman which had a bug that messed this up. It disabled ipv6 functionality as soon as the daemon was kicked and this was happening after my conf modified the kernel var.
Thanks a lot once again. BR, Awais Belal ________________________________________ From: Lennart Poettering [lenn...@poettering.net] Sent: Thursday, June 20, 2013 11:34 PM To: Belal, Awais Cc: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] Modifying kernel vars through sysctl.d On Thu, 20.06.13 12:24, Belal, Awais (awais_be...@mentor.com) wrote: > Hi, > > I am trying to update a kernel variable on boot. So, after reading a bit here > and there I found out that I could simply provide a .conf file under > /etc/sysctl.d/ and have my required configs in it. I placed a file ipv6.conf > under the mentioned directory with the contents: > > net.ipv6.conf.eth0.disable_ipv6=0 > > so I could enable ipv6 on my eth0 interface on boot. Oddly enough this isn't > working as I expected and doing a 'cat > /proc/sys/net/ipv6/conf/eth0/disable_ipv6' still gives me '1'. I checked the > status of the systemd-sysctl.service and it shows up as 'active (exited)'. If > I do a 'systemctl restart systemd-sysctl.service' after boot the > configuration gets through as needed. > > What am I doing wrong? Are there any better ways of achieving the same? This should just work. Maybe you have some other network managing service that overides this again? If you run "strace -e open /usr/lib/systemd/systemd-sysctl" as root, do you see the file opened in /proc/sys? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
