Hello Laurent! I'm looking at the bug you reported against ifupdown, http://bugs.debian.org/448138. I can't really comment on the underlying problem, but thought I might just chime in on one thing.
> As seeing the post-up hooks are run before ifenslave script, so I > cannot do the arp trick as interface does not exists, and even if I > force it deleted when interface come up. > This is maybe a wanted thing but It does not seems intuitive to me. > (/etc/network/if-up.d/ should maybe > renamed /etc/network/if-post-up.d/ ?) Or I just miss something... While pre-up is it's own command, post-up is just an alias for up! I don't know if you can determine in which order the if-up.d scripts and the (post-)up commands are run. You seems to have found out that the scripts are run before the commands for you (but I don't know if this is something to rely on always happening). Maybe ifupdown should be modified to make the post-up it's own command where you can be sure it runs after the if-up.d scripts, so we have pre-up -> configure -> up (scripts) -> post-up. That way you'll have reliable order and it would hopefully solve your problem. Just an idea.... For now you can probably work around your problem by sticking the commands in scripts in if-up.d and name them to be run after the other if-up.d scripts.... -- Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
