Default gateway lost after netif restart
Oliver Pinter
oliver.pntr at gmail.com
Thu Dec 26 16:29:14 UTC 2013
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 at 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
>
More information about the freebsd-arch
mailing list