Comment 4 for bug 461725

I just came across this bug, wrt ufw. Traditionally, it has been expected that lo would be up before network daemons had started (eg, runlevel 2). It has become common practice to use an ifupdown script to bring up a firewall when lo is brought up. Ufw uses this practice and has the following in its upstart job: 'start on net-device-added INTERFACE=lo'. If this bug is not going to be fixed, then ufw must be adjusted so that firewall rules are in effect before network daemons start.