Date: Thu, 26 Dec 2013 17:29:13 +0100 From: Oliver Pinter <oliver.pntr@gmail.com> To: Alex Long <alex.long@hostek.com> Cc: freebsd-arch@freebsd.org Subject: Re: Default gateway lost after netif restart Message-ID: <CAPjTQNH%2BgCXp7N=nkCRHPecgEdmfTA0zk38Eq5DRH3FLG9sCVg@mail.gmail.com> In-Reply-To: <52BC5177.70903@hostek.com> References: <52BC5177.70903@hostek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! Try to use screen or tmux. ;) screen service netif restart; service routing restart or when you must restart only one interface, then try this command: service netif restart _if_name_ e.g.: service netif restart em0 when you have intel network card. On 12/26/13, Alex Long <alex.long@hostek.com> wrote: > 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 > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPjTQNH%2BgCXp7N=nkCRHPecgEdmfTA0zk38Eq5DRH3FLG9sCVg>