From owner-freebsd-current@freebsd.org Thu Oct 6 13:53:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEEB3BE9BBF for ; Thu, 6 Oct 2016 13:53:03 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B5524D77; Thu, 6 Oct 2016 13:53:03 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bs96U-003saM-PW>; Thu, 06 Oct 2016 15:52:54 +0200 Received: from [141.89.176.196] (helo=hermann) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bs96U-000qhp-Id>; Thu, 06 Oct 2016 15:52:54 +0200 Date: Thu, 6 Oct 2016 15:52:53 +0200 From: "Hartmann, O." To: Oliver Peter Cc: FreeBSD CURRENT , allanjude@freebsd.org Subject: Re: CURRENT: "service netif restart" looses default route Message-ID: <20161006155253.3e97f90b@hermann> In-Reply-To: <20161006072753.GA11735@mail.opdns.de> References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> <20161006072753.GA11735@mail.opdns.de> Organization: FU Berlin MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 141.89.176.196 X-Mailman-Approved-At: Thu, 06 Oct 2016 14:18:02 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 13:53:04 -0000 On Thu, 6 Oct 2016 09:27:53 +0200 Oliver Peter wrote: > On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: > > > > Today, I checked on two servers of ours running both a recent > > CURRENT (i.e. FreeBSD 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 > > CEST 2016) via "service netif restart" the upcoming network and > > realised that the default route is lost then! > > > > I'm able to config the route via "service routing restart" - or > > manually as I did otherwise. But I recall that I did a simple > > "service netif restart" in 11-CURRENT recently and that worked. > > > > Has there been a change? What is now the official way to restart > > network? > > Since the past couple of years on every new FreeBSD I put this in > motd for my linux colleagues and coworkers: > > Network: > To apply changes you have made to the network: > # /etc/rc.d/netif restart && /etc/rc.d/routing restart > > Perhaps we could introduce a wrapper to be used with: > # service network restart > > oliver@local ~ % cat /etc/rc.d/network > #!/bin/sh > > # PROVIDE: network > # REQUIRE: netif routing > # KEYWORD: nojailvnet > > . /etc/rc.subr > . /etc/network.subr > > name="network" > start_cmd="network_start" > stop_cmd="network_stop" > > network_start() > { > /etc/rc.d/netif start > /etc/rc.d/routing start > } > > network_stop() > { > /etc/rc.d/netif stop > /etc/rc.d/routing stop > } > > load_rc_config $name > run_rc_command $* > > I'm sorry that my sloppyness brought up this discussion. I recall that I tried to hunt down a bug and did lots of "service netif restart". But on a local network with all essential servers on the same net, I never faced a problem with routing. If life gets too easy, people start digging for the reason of a problem too deep when the framework does too much stuff automated ... The knowledge of the fact that I also have to restart routing via a script is sufficient for me - also the fact to know that netif restart doesn't restart routing. Regards, Oliver