Re: netstart diff for aggr(4) handling

2019-10-18 Thread Claudio Jeker
On Thu, Oct 17, 2019 at 11:24:24PM +0200, Alexander Bluhm wrote:
> On Thu, Oct 17, 2019 at 04:47:27PM -0400, Brad Smith wrote:
> > Shouldn't aggr(4) be handled in the same manner as trunk(4)?
> 
> I guess so, OK bluhm@

+1 OK claudio
 
> > Index: netstart
> > ===
> > RCS file: /home/cvs/src/etc/netstart,v
> > retrieving revision 1.200
> > diff -u -p -u -p -r1.200 netstart
> > --- netstart29 Aug 2018 11:30:48 -  1.200
> > +++ netstart17 Oct 2019 20:45:29 -
> > @@ -300,12 +300,12 @@ vifscreate
> >
> >  # 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 pppoe tun tap gif etherip gre egre 
> > mobileip pflow"
> > +ifmstart "" "aggr trunk svlan vlan carp pppoe tun tap gif etherip gre egre 
> > mobileip pflow"
> >
> >  # The trunk interfaces need to come up first in this list.
> >  # The (s)vlan interfaces need to come up after trunk.
> >  # Configure all the carp interfaces which we know about before default 
> > route.
> > -ifmstart "trunk svlan vlan carp pppoe"
> > +ifmstart "aggr trunk svlan vlan carp pppoe"
> >
> >  # Set default routes for IPv4 and IPv6.
> >  defaultroute
> 

-- 
:wq Claudio



Re: netstart diff for aggr(4) handling

2019-10-17 Thread Alexander Bluhm
On Thu, Oct 17, 2019 at 04:47:27PM -0400, Brad Smith wrote:
> Shouldn't aggr(4) be handled in the same manner as trunk(4)?

I guess so, OK bluhm@

> Index: netstart
> ===
> RCS file: /home/cvs/src/etc/netstart,v
> retrieving revision 1.200
> diff -u -p -u -p -r1.200 netstart
> --- netstart  29 Aug 2018 11:30:48 -  1.200
> +++ netstart  17 Oct 2019 20:45:29 -
> @@ -300,12 +300,12 @@ vifscreate
>
>  # 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 pppoe tun tap gif etherip gre egre 
> mobileip pflow"
> +ifmstart "" "aggr trunk svlan vlan carp pppoe tun tap gif etherip gre egre 
> mobileip pflow"
>
>  # The trunk interfaces need to come up first in this list.
>  # The (s)vlan interfaces need to come up after trunk.
>  # Configure all the carp interfaces which we know about before default route.
> -ifmstart "trunk svlan vlan carp pppoe"
> +ifmstart "aggr trunk svlan vlan carp pppoe"
>
>  # Set default routes for IPv4 and IPv6.
>  defaultroute



netstart diff for aggr(4) handling

2019-10-17 Thread Brad Smith
Shouldn't aggr(4) be handled in the same manner as trunk(4)?


Index: netstart
===
RCS file: /home/cvs/src/etc/netstart,v
retrieving revision 1.200
diff -u -p -u -p -r1.200 netstart
--- netstart29 Aug 2018 11:30:48 -  1.200
+++ netstart17 Oct 2019 20:45:29 -
@@ -300,12 +300,12 @@ vifscreate
 
 # 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 pppoe tun tap gif etherip gre egre mobileip 
pflow"
+ifmstart "" "aggr trunk svlan vlan carp pppoe tun tap gif etherip gre egre 
mobileip pflow"
 
 # The trunk interfaces need to come up first in this list.
 # The (s)vlan interfaces need to come up after trunk.
 # Configure all the carp interfaces which we know about before default route.
-ifmstart "trunk svlan vlan carp pppoe"
+ifmstart "aggr trunk svlan vlan carp pppoe"
 
 # Set default routes for IPv4 and IPv6.
 defaultroute