Date: Mon, 11 Oct 2010 01:30:17 -0400 From: jhell <jhell@DataIX.net> To: Garrett Cooper <gcooper@FreeBSD.org> Cc: Doug Barton <dougb@FreeBSD.org>, FreeBSD Current <freebsd-current@FreeBSD.org>, Sergey Kandaurov <pluknet@gmail.com>, freebsd-rc@FreeBSD.org Subject: Re: [RFC] ifconfig description support in rc.d Message-ID: <4CB2A0E9.50108@DataIX.net> In-Reply-To: <AANLkTimyHSkD=HVZKy4mXt9uMtCvTBZ687=2w-msx28h@mail.gmail.com> References: <AANLkTinfOSQGnk0%2BPK6iM0=v5CZn2vcmJZbA8TvgGbfr@mail.gmail.com> <4C76CA06.5010001@FreeBSD.org> <AANLkTintgji3vzrb8XuUQHWp%2B7YDvHtd7ynP0MmV0oZr@mail.gmail.com> <4CB135F5.20804@DataIX.net> <AANLkTik77T2xjB2Gcmbh4z0EPu-%2BaQ1qwyKoQhGkHZPf@mail.gmail.com> <AANLkTimyHSkD=HVZKy4mXt9uMtCvTBZ687=2w-msx28h@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/10/2010 13:23, Garrett Cooper wrote: > <offtopic> > I'm not sure it would get resolved after this commit, but one > minor annoyance is that restarting the netif rc.d script purges all > gateways set, so I have to do and restart the routing rc.d script (if > my connectivity doesn't get whacked). I think there was something else > with natd and ipfw that I've run into in the past where I've restarted > those scripts and things weren't all puppydogs and rainbows on my > CURRENT systems. > </offtopic> > Thanks, > -Garrett Is that the dynamic routes only or also the static routes ? Either or if it would be any of the above it would be nice if these were kept if it was only a restart of the interface, but offhand nothing comes to mind that could prevent this from happening since the routes are acting according to when the interface becomes inactive then the route becomes meaningless. Maybe if the action of 'restart' to etc/rc.d/netif could also call etc/rc.d/routing with 'restart' if the configuration of the interface happens to match one of the recorded routes in rc.conf(5). Just a thought. Regards, -- jhell,v
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CB2A0E9.50108>