Comment 4 for bug 506727

Hi Johan,

I've done the whole sulogin thing -- the 'lo' device might not be brought up correctly.

But that is not the problem here, as 'ifup lo' changes nothing.

Here is what I end up with for 'lo':

eve:[~]% ip addr show lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

This is what should have occurred.

eve:[~]% ifup --no-act --verbose --force lo
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
ip link set dev lo up
ip addr add 127.0.0.2 dev lo
run-parts --verbose /etc/network/if-up.d

So, when I do: 'ifdown lo' and 'ifup lo', I get:

eve:[~]% ifdown lo && ifup lo
RTNETLINK answers: No such process
run-parts: /etc/network/if-down.d/multicast-down exited with return code 2

eve:[~]% ip addr show lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet 127.0.0.2/32 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

Any other suggestions?

Anand