Re: kern/39236: Network interface order problem: /etc/ifconfig.bridge* is started too early

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR kern/39236; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/39236: Network interface order problem:  
/etc/ifconfig.bridge* is started too early
Date: Mon, 28 Jul 2008 12:47:30 +0200

 --ibTvN161/egqYuK8
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 First the easy workaround with -current means: set auto_ifconfig=NO
 and set net_interfaces to the interfaces you want to configure, in the
 order you prefer.
 
 Second: the current order by default is just alphabetic.
 
 Finaly: I like the idea to introduce optional dependencies, and implementation
 should be extremely simple (like attached untested patch) by reusing
 rcorder and support the same PROVIDE/REQUIRE/BEFORE/KEYWORD semantics
 we use for rc script ordering. If none of those are provided in the ifconfig.*
 files, the order will be returned unchanged.
 
 Martin
 
 --ibTvN161/egqYuK8
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename=patch
 
 Index: network
 ===================================================================
 RCS file: /cvsroot/src/etc/rc.d/network,v
 retrieving revision 1.52
 diff -u -r1.52 network
 --- network    29 May 2008 15:38:35 -0000      1.52
 +++ network    28 Jul 2008 10:42:08 -0000
 @@ -191,7 +191,7 @@
                        tmp="$net_interfaces"
                fi
                echo -n 'Configuring network interfaces:'
 -              for int in $tmp; do
 +              for int in $( rcorder $tmp ); do
                        eval args=\$ifconfig_$int
                        if [ -n "$args" ] || [ -f /etc/ifconfig.$int ]; then
                                if ifconfig $int create 2>/dev/null && \
 
 --ibTvN161/egqYuK8--