Tested with Ubuntu 12.04.3 LTS, procps/precise-updates uptodate 1:3.2.8-11ubuntu6.2:
In /etc/sysctl.d/10-network-security.conf: net.ipv4.conf.default.rp_filter=0 net.ipv4.conf.all.rp_filter=0
$ sudo service procps start start: Job failed to start
After commenting out the lines in /etc/sysctl.d/10-network-security.conf: # net.ipv4.conf.default.rp_filter=0 # net.ipv4.conf.all.rp_filter=0
$ sudo service procps start procps stop/waiting
That is, the bug is still there and -- regardless of the value of the rp_filter setting (0 or 1) -- it is not working.
Tested with Ubuntu 12.04.3 LTS, procps/ precise- updates uptodate 1:3.2.8- 11ubuntu6. 2:
In /etc/sysctl. d/10-network- security. conf: conf.default. rp_filter= 0 conf.all. rp_filter= 0
net.ipv4.
net.ipv4.
$ sudo service procps start
start: Job failed to start
After commenting out the lines in /etc/sysctl. d/10-network- security. conf: conf.default. rp_filter= 0 conf.all. rp_filter= 0
# net.ipv4.
# net.ipv4.
$ sudo service procps start
procps stop/waiting
That is, the bug is still there and -- regardless of the value of the rp_filter setting (0 or 1) -- it is not working.