From owner-freebsd-net@FreeBSD.ORG Wed Apr 24 18:51:05 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 427E2A4 for ; Wed, 24 Apr 2013 18:51:05 +0000 (UTC) (envelope-from rrs@lakerest.net) Received: from lakerest.net (lakerest.net [70.155.160.98]) by mx1.freebsd.org (Postfix) with ESMTP id C4EEF166C for ; Wed, 24 Apr 2013 18:51:04 +0000 (UTC) Received: from [10.1.1.213] ([10.1.1.213]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id r3OIovXA015987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 14:50:58 -0400 (EDT) (envelope-from rrs@lakerest.net) Subject: Re: Default route changes unexpectedly Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Randall Stewart In-Reply-To: Date: Wed, 24 Apr 2013 14:50:57 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <5136FD71.6000408@freebsd.org> <556E6D18-15FD-4D89-8064-45B139C9C6E7@lakerest.net> To: Tom Evans X-Mailer: Apple Mail (2.1283) Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:51:05 -0000 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 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)