From owner-freebsd-net@FreeBSD.ORG Tue Apr 23 13:40:10 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 804AC5D3 for ; Tue, 23 Apr 2013 13:40:10 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2101353 for ; Tue, 23 Apr 2013 13:40:09 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fd20so549401lab.39 for ; Tue, 23 Apr 2013 06:40:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qV/5Blg8I23J4SruNDNJhAyAcFYyTlyNdq0AknNt684=; b=cfs3MGhFx6TcVEhDfDK/Qkx68Lf1agbvcwyujhe0MosH4rdd1oy7C/pmCaT1ppnzpm ijmODB1MTIgS4e9q3IpXXajTibHkUOn+RIumnp710p8QVnLnGYNFPeydw51HQLmEGL1N CBXubg+2Q4HsiJtP2ahgd62MgZRR9KXCzTnTTgoB53RGF21zMq1/JySCTZT2pJU93jYd /0H7ICGsJCOBbm5+83/MzkQAJM86FV5qq4j/nILhy+QB2CvsUu1zOyoiGR1+cxUVgs9d mFWoQMtxkA2Syy+dl8jB/1MSA2ofMkxhWlQkyFNFdMhzFulHnDvxZdqRvTPLuB0ODWtx O0FA== MIME-Version: 1.0 X-Received: by 10.152.26.101 with SMTP id k5mr15740797lag.31.1366724408867; Tue, 23 Apr 2013 06:40:08 -0700 (PDT) Received: by 10.112.162.36 with HTTP; Tue, 23 Apr 2013 06:40:08 -0700 (PDT) In-Reply-To: <556E6D18-15FD-4D89-8064-45B139C9C6E7@lakerest.net> References: <5136FD71.6000408@freebsd.org> <556E6D18-15FD-4D89-8064-45B139C9C6E7@lakerest.net> Date: Tue, 23 Apr 2013 14:40:08 +0100 Message-ID: Subject: Re: Default route changes unexpectedly From: Tom Evans To: Randall Stewart Content-Type: text/plain; charset=UTF-8 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: Tue, 23 Apr 2013 13:40:10 -0000 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