From owner-freebsd-arch@FreeBSD.ORG  Thu Dec 26 16:14:48 2013
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E60DA71
 for <freebsd-arch@freebsd.org>; Thu, 26 Dec 2013 16:14:48 +0000 (UTC)
Received: from htmail1.hostek.com (htmail1.hostek.com [216.15.165.50])
 (using TLSv1 with cipher AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id AAC001CF7
 for <freebsd-arch@freebsd.org>; Thu, 26 Dec 2013 16:14:48 +0000 (UTC)
Received: from [192.168.1.242] (tulsokzl.etel.64-207-234-198.easytel.com
 [64.207.234.198]) by htmail1.hostek.com with SMTP (version=Tls
 cipher=Aes128 bits=128); Thu, 26 Dec 2013 09:54:11 -0600
Message-ID: <52BC5177.70903@hostek.com>
Date: Thu, 26 Dec 2013 09:55:35 -0600
From: Alex Long <alex.long@hostek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: freebsd-arch@freebsd.org
Subject: Default gateway lost after netif restart
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Dec 2013 16:14:49 -0000

I am new to FreeBSD so I apologize if this is the wrong place to post 
this.  But there is a flaw in the logic regarding restart of the netif 
service.  I understand that after restarting the netif service, you have 
to manually restart the routing service.  The problem is that if you are 
configuring a machine remotely and you have to restart the netif service 
for whatever reason, your defaut gateway is lost, thus preventing you 
from restarting the routing service and you lose connectivity to the 
machine.

Now I get around this by creating a shell script that does both and just 
executing that script.  This works but it is sloppy in my opinion.  It 
does not makes sense to restart a network service and lose ANY network 
functionality (i.e. your routes) once it comes back up.

Regards,
Alex Long