ifupdown integration broken

[Soren Hansen]

Binary package hint: ifenslave-2.6

ifupdown integration is broken. /etc/network/{pre-up,post-down}/ifenslave-2.6 looks for ifstate in /etc/network/run, but it's been in /var/run/network for ages.

[Soren Hansen (soren)]

To verify this bug, add this to interfaces:

iface bond0 inet manual
   slaves eth0

You'll see somthing like:
grep: /etc/network/run/ifstate: No such file or directory

After applying the fix, the slaves should be added to the bonding device. (check with "ifenslave-2.6 bond0")

[Martin Pitt (pitti)]

Subscribed motu-sru. Accepted into hardy-proposed, please test.

[Soren Hansen (soren)]

ifenslave-2.6 is not in universe.. I can't unsubscribe motu-sru, though :(

[Martin Pitt (pitti)]

Soren Hansen [2008-04-29 12:00 -0000]:
> ifenslave-2.6 is not in universe.. I can't unsubscribe motu-sru, though

Oh, oops, I should have checked that. It's the first time I hear about
that package :/

[Jesper Krogh (jesper)]

I can confirm both bug and fix.

This is vital, it breaks networking on any server running with bonded network interfaces. .. worked flawless in hardy-1

Another change that seems to be releated.

Symbolik names in /etc/modprobe.d/options doesnt work any more:
May 1 22:02:33 hest kernel: [ 175.644153] bonding: Error: Invalid bonding mode "802.3ad"

options bond0 mode=4 miimon=100
# Apparently 802.3ad doesnt work any more (worked in hardy-1)
# options bond0 mode=802.3ad miimon=100

Jesper

[Martin Pitt (pitti)]

Jesper, does that mean you tried the packages in hardy-proposed, and they fix the bug for you?

[Jesper Krogh (jesper)]

No. I integrated the changes from the diff manually on my system. (They were very trivial).

Jesper

[Martin Pitt (pitti)]

Ah, I just saw that there are binary components in the package. Jesper, would you mind actually trying the package in hardy-proposed (just to be on the safe side)? Thank you!

[Jesper Krogh (jesper)]

I've now tried it from hardy-proposed, and can confirm that it works excellent.

Jesper

[Martin Pitt (pitti)]

Copied to hardy-updates. Thanks for the testing!

[Soren Hansen (soren)]

Also fixed in Intrepid now.

[Marcin Kowalczyk (qrczakmk)]

/etc/network/if-up.d/mountnfs from intrepid's initscripts still refers to /etc/network/run/ifstate.

[Kyle M Weller (kylew)]

root@pc:~# /etc/init.d/networking restart
 * Reconfiguring network interfaces... grep: /etc/network/run/ifstate: No such file or directory
[: 164: 0: unexpected operator
grep: /etc/network/run/ifstate: No such file or directory
[: 164: 0: unexpected operator
                                                                         [ OK ]

[Paul Hoell (hoellp)]

I'm on intrepid kde4 64bit up-to-date and I get this error when bringing wirless up.

$ sudo ifup wlan0
...
grep: /etc/network/run/ifstate: No such file or directory
[: 164: 0: unexpected operator
grep: /etc/network/run/ifstate: No such file or directory
[: 164: 0: unexpected operator
grep: /etc/network/run/ifstate: No such file or directory
[: 164: 0: unexpected operator

Thanks for your attention

[Beojan (beojan2)]

The simple fix would be to symlink /etc/network/run to /var/run/network with

sudo ln -s /var/run/network /etc/network/run

[Soren Hansen (soren)]

On Thu, Aug 28, 2008 at 10:54:09AM -0000, Paul Hoell wrote:
> I'm on intrepid kde4 64bit up-to-date and I get this error when bringing
> wirless up.
>
> $ sudo ifup wlan0
> ...
> grep: /etc/network/run/ifstate: No such file or directory
> [: 164: 0: unexpected operator
> grep: /etc/network/run/ifstate: No such file or directory
> [: 164: 0: unexpected operator
> grep: /etc/network/run/ifstate: No such file or directory
> [: 164: 0: unexpected operator
>
> Thanks for your attention

The error you're seeing is most likely caused by the mountnfs script in
the initscripts package for which I'll upload a fix in a few minutes.
Let me know if the problem persists.