On Tue, Sep 19, 2017 at 04:54:04PM +1000, David Gwynne wrote: > this helsp if you want to have a tap interface joined to a bridge > on boot. > > ok?
Uhm, why? bridge is already delayed and tap will be initialized therefore before bridge? Neither tun nor tap should be in that list in my opinion since they do not depend on other interfaces to be present to initalise them. > Index: netstart > =================================================================== > RCS file: /cvs/src/etc/netstart,v > retrieving revision 1.186 > diff -u -p -r1.186 netstart > --- netstart 25 Jul 2017 21:17:11 -0000 1.186 > +++ netstart 19 Sep 2017 06:53:10 -0000 > @@ -255,7 +255,7 @@ fi > > # Configure all the non-loopback interfaces which we know about, but > # do not start interfaces which must be delayed. Refer to hostname.if(5) > -ifmstart "" "trunk svlan vlan carp gif gre pfsync pppoe tun bridge switch > pflow" > +ifmstart "" "trunk svlan vlan carp gif gre pfsync pppoe tun tap bridge > switch pflow" > > # The trunk interfaces need to come up first in this list. > # The (s)vlan interfaces need to come up after trunk. > @@ -275,7 +275,7 @@ fi > # require routes to be set. TUN might depend on PPPoE, and GIF or GRE may > # depend on either of them. PFLOW might bind to ip addresses configured > # on either of them. > -ifmstart "pppoe tun gif gre bridge switch pflow" > +ifmstart "pppoe tun tap gif gre bridge switch pflow" > > # Reject 127/8 other than 127.0.0.1. > route -qn add -net 127 127.0.0.1 -reject >/dev/null > -- :wq Claudio
