Date: Wed, 5 Oct 2016 19:50:24 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: "service netif restart" looses default route Message-ID: <alpine.BSF.2.20.1610051942260.39603@mail.fig.ol.no> In-Reply-To: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Oct 2016 18:47+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? I see something similar on stable/11, r306639. During boot this system can't add its IPv6 default route. I need to add it manually afterwards. Note, this is on XenServer 7.0.0, so maybe the hypervisor play a certain role. Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add host 127.0.0.1: gateway lo0 fib 0: route already in table Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net default: gateway 128.x.y.z Oct 4 13:23:24 <console.info> [WITHHELD] kernel: Additional inet routing options: gateway=YES. Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add host ::1: gateway lo0 fib 0: route already in table Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net fe80::: gateway ::1 Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net ff02::: gateway ::1 Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net ::ffff:0.0.0.0: gateway ::1 Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net ::0.0.0.0: gateway ::1 Oct 4 13:23:24 <console.info> [WITHHELD] kernel: route: writing to routing socket: Network is unreachable Oct 4 13:23:24 <console.info> [WITHHELD] kernel: add net default: gateway 2001:x:y:z::1 fib 0: Network is unreachable Also, why do the startup scripts attempt to add additional routes for 127.0.0.1 and ::1? I see that behaviour on both head and stable/11. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@freebsd.org Wed Oct 5 17:54:03 2016 Return-Path: <owner-freebsd-current@freebsd.org> 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 D983FAF63B4 for <freebsd-current@mailman.ysv.freebsd.org>; Wed, 5 Oct 2016 17:54:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 BE1722AE for <freebsd-current@freebsd.org>; Wed, 5 Oct 2016 17:54:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 834A811C8E for <freebsd-current@freebsd.org>; Wed, 5 Oct 2016 17:54:01 +0000 (UTC) Subject: Re: CURRENT: "service netif restart" looses default route To: freebsd-current@freebsd.org References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> From: Allan Jude <allanjude@freebsd.org> Message-ID: <30598abd-3a76-10cd-e7f9-aa9bb0bad87b@freebsd.org> Date: Wed, 5 Oct 2016 13:54:00 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Oct 2016 17:54:03 -0000 On 2016-10-05 12:47, 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? > > Kind regards, > Oliver > As far as I am aware, this has always been this way, at least with FreeBSD 6.0 and later. When you delete the interfaces, the route goes away, then you recreate the interfaces but not the routes. -- Allan Jude
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1610051942260.39603>