[Bug 1073658] [NEW] procps runs before network is properly initialized

Simon Déziel 1073658 at bugs.launchpad.net
Wed Oct 31 17:25:19 UTC 2012


Public bug reported:

Disabling rp_filter on an interface that is subject to eth renaming
during boot will end up disabling rp_filter on the wrong interface.

On my specific system, I want to turn off rp_filter on eth2:

root at fw2:~# cat /etc/sysctl.d/60-partly-disable-rp-filter.conf 
net.ipv4.conf.all.rp_filter=0
net.ipv4.conf.eth2.rp_filter=0

but on reboot I get this:

root at fw2:~# sysctl net.ipv4.conf| grep -F .rp_filter
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.eth2.rp_filter = 1
net.ipv4.conf.eth4.rp_filter = 1
net.ipv4.conf.eth5.rp_filter = 1
net.ipv4.conf.eth3.rp_filter = 1
net.ipv4.conf.eth0.rp_filter = 0
net.ipv4.conf.eth1.rp_filter = 1
net.ipv4.conf.eth1/29.rp_filter = 1
net.ipv4.conf.eth1/23.rp_filter = 1
net.ipv4.conf.eth1/30.rp_filter = 1

This seems to be caused by eth renaming that happens after procps ran:

root at fw2:~# dmesg | grep rename
[    5.697133] udevd[492]: renamed network interface eth5 to rename7
[    5.720664] udevd[490]: renamed network interface eth2 to rename4
[    5.752559] udevd[494]: renamed network interface eth3 to eth2
[    5.792480] udevd[491]: renamed network interface eth4 to rename6
[    5.820484] udevd[462]: renamed network interface eth0 to eth4
[    5.864355] udevd[463]: renamed network interface eth1 to eth5
[    5.940202] udevd[492]: renamed network interface rename7 to eth3
[    5.960133] udevd[490]: renamed network interface rename4 to eth0
[    5.984130] udevd[491]: renamed network interface rename6 to eth1

During the boot up, "eth2" has the rp_filter disabled as expected but it
is later renamed to "rename4" then "eth0". The disabled rp_filter ends
up on "eth0" which is obviously not what was expected.

** Affects: procps (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1073658

Title:
  procps runs before network is properly initialized

Status in “procps” package in Ubuntu:
  New

Bug description:
  Disabling rp_filter on an interface that is subject to eth renaming
  during boot will end up disabling rp_filter on the wrong interface.

  On my specific system, I want to turn off rp_filter on eth2:

  root at fw2:~# cat /etc/sysctl.d/60-partly-disable-rp-filter.conf 
  net.ipv4.conf.all.rp_filter=0
  net.ipv4.conf.eth2.rp_filter=0

  but on reboot I get this:

  root at fw2:~# sysctl net.ipv4.conf| grep -F .rp_filter
  net.ipv4.conf.all.rp_filter = 0
  net.ipv4.conf.default.rp_filter = 1
  net.ipv4.conf.lo.rp_filter = 1
  net.ipv4.conf.eth2.rp_filter = 1
  net.ipv4.conf.eth4.rp_filter = 1
  net.ipv4.conf.eth5.rp_filter = 1
  net.ipv4.conf.eth3.rp_filter = 1
  net.ipv4.conf.eth0.rp_filter = 0
  net.ipv4.conf.eth1.rp_filter = 1
  net.ipv4.conf.eth1/29.rp_filter = 1
  net.ipv4.conf.eth1/23.rp_filter = 1
  net.ipv4.conf.eth1/30.rp_filter = 1

  This seems to be caused by eth renaming that happens after procps ran:

  root at fw2:~# dmesg | grep rename
  [    5.697133] udevd[492]: renamed network interface eth5 to rename7
  [    5.720664] udevd[490]: renamed network interface eth2 to rename4
  [    5.752559] udevd[494]: renamed network interface eth3 to eth2
  [    5.792480] udevd[491]: renamed network interface eth4 to rename6
  [    5.820484] udevd[462]: renamed network interface eth0 to eth4
  [    5.864355] udevd[463]: renamed network interface eth1 to eth5
  [    5.940202] udevd[492]: renamed network interface rename7 to eth3
  [    5.960133] udevd[490]: renamed network interface rename4 to eth0
  [    5.984130] udevd[491]: renamed network interface rename6 to eth1

  During the boot up, "eth2" has the rp_filter disabled as expected but
  it is later renamed to "rename4" then "eth0". The disabled rp_filter
  ends up on "eth0" which is obviously not what was expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1073658/+subscriptions




More information about the foundations-bugs mailing list