Date: Wed, 24 Apr 2013 14:50:57 -0400 From: Randall Stewart <rrs@lakerest.net> To: Tom Evans <tevans.uk@googlemail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Default route changes unexpectedly Message-ID: <E3ADCED9-8C65-4B4A-84C7-D0277065262E@lakerest.net> In-Reply-To: <CAFHbX1LSC2_wYejg94hqciDmW9nX7Lajt=N_CqNBnniYoHh1HA@mail.gmail.com> References: <CAKOb=YYGu6mr-3nyydBi9K-FHPnEx-fKSZ2=r_uDVeY9pvrqtQ@mail.gmail.com> <5136FD71.6000408@freebsd.org> <CAKOb=YaX%2ByopoofwRbfN7ZXc_yG0uxoKkr3aXsVcXEdLqQ=AXQ@mail.gmail.com> <556E6D18-15FD-4D89-8064-45B139C9C6E7@lakerest.net> <CAFHbX1LSC2_wYejg94hqciDmW9nX7Lajt=N_CqNBnniYoHh1HA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
All Ok I fixed it ;-) Its in SVN r249848. I will see about getting it to 9 stable, 8 stable and maybe even 8.4 if RE will let me ;-) R On Apr 23, 2013, at 9:40 AM, Tom Evans wrote: > On Tue, Apr 23, 2013 at 1:08 PM, Randall Stewart <rrs@lakerest.net> wrote: >> Ok >> >> I too have been struck by this *multiple* times on my base home router. >> > > I hate "me too" style posts, since often they conflate unrelated > issues - however, "me too"! > > In my scenario, I have a simple home router with a wan if connected to > an ADSL modem, an internal if connected to a pretty ordinary switch > and the rest of the home network, using pf to NAT the connection > (pretty basic stuff). > > Infrequently, I can no longer connect to or ping the router from > internal connections, and have to grab a console, restart netif and > routing, and everything then works again. > > However, I also have an openvpn connection to work running on the > router. Work seem to believe that the reason there are 3 huge private > network ranges is so that they can use the 10/8 block for DC > infrastructure, the 172.16/12 block for offices and the 192.168/16 bit > block for VPNs. Until now, I had been assuming - without any proof - > that everything works great until openvpn gets told that 192.168.1/8 > should be routed down the VPN, at which point everything local is > inaccessible. > > Is there something useful I can look at when this next occurs that > would explain why or how it is wedged, so that I can either rule > myself in or out of this case? > > Cheers > > Tom > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > ------------------------------ Randall Stewart 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E3ADCED9-8C65-4B4A-84C7-D0277065262E>