From owner-freebsd-net@FreeBSD.ORG Wed Mar 6 07:32:42 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 9EB14F2C for ; Wed, 6 Mar 2013 07:32:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by mx1.freebsd.org (Postfix) with ESMTP id 133B67A1 for ; Wed, 6 Mar 2013 07:32:41 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id fg15so6853704wgb.13 for ; Tue, 05 Mar 2013 23:32:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Tynyg9fXL6DfIoA1/e9slZogS8k9CTqbtZDi5floLgk=; b=CTF+x27Ya5LjbXh32BYYzSe+bDbdk55VVecTJKiXzkox3XKd46wlgds1rMbbjnDpgA RjpVsbOxjxOH0SAQyLdLMp86HxQX4nbnfHXACkbGbWxnRFC6FJQI196yM3mIB/oi6Gni t1abd7GwwuHMskkzWEy6sL76S9r/kOr7sirRJ+1RjYraxq12guiE/i4feeIjVt5EquHC N0iUvfWnSmvjGZe2LFb4SkHkBpIGnRsGxwzo4BlUDfZkqAkr8PF61mrBndUD/i42d6uH xBRvgwRGnFpTL3/BJeEJa7oAxnzMVi44dATkPlPhkQ0iS7CXdckBXfalb/G+ZxyH7nV0 A6+Q== MIME-Version: 1.0 X-Received: by 10.180.108.3 with SMTP id hg3mr23594376wib.33.1362555160454; Tue, 05 Mar 2013 23:32:40 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Tue, 5 Mar 2013 23:32:40 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Mar 2013 23:32:40 -0800 X-Google-Sender-Auth: O_oVYtcpGYq0nhueZ0odFTAQD1w Message-ID: Subject: Re: Default route changes unexpectedly From: Adrian Chadd To: Nick Rogers Content-Type: text/plain; charset=ISO-8859-1 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, 06 Mar 2013 07:32:42 -0000 It's a known problem; it just seems that it doesn't overlap/intersect the day to day activities of any network focused freebsd developers. If you guys want it fixed then you may have to find a developer to hire on contract to fix it, or find some kind of ruleset/traffic generation setup that reliably triggers the bug. Adrian On 5 March 2013 09:39, Nick Rogers wrote: > Hello, > > I am attempting to create awareness of a serious issue affecting users > of FreeBSD 9.x and PF. There appears to be a bug that allows the > kernel's routing table to be corrupted by traffic routing through the > system. Under heavy traffic load, the default route can seemingly > randomly change to an IP address that is not directly connected to the > network (i.e., is not configured anywhere). Dhclient is not in the > mix, nor is routed, bgpd, etc. Running `route monitor` shows no > evidence of the change in the default route. The one commonality > between all the systems experiencing this problem seems to be the use > of PF. > > Obviously this is a serious problem as it causes all Internet-bound > traffic to stop routing until the default route is corrected. Some > users, including myself, are working around this problem by installing > a script that runs multiple times a second to check if the default > route is incorrect and fixing it if necessary, which mitigates the > amount of downtime caused by the bug. > > Please refer to these past posts for more examples and evidence of > other users experiencing this problem: > > http://forums.freebsd.org/showthread.php?p=211610#post211610 > > http://freebsd.1045724.n5.nabble.com/Default-route-quot-random-quot-gateway-modification-bug-td5750820.html > > http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html > > http://lists.freebsd.org/pipermail/freebsd-ipfw/2010-September/004361.html > > There is also a PR that was incorrectly labeled as an IPFW issue. > Myself and others believe this issue is not restricted to the use of > IPFW and that the PR should be relabeled. I am inclined to think it is > strictly a PF issue since I am not using IPFW, however there is > evidence of the default route changing on people using IPFW for past > versions of FreeBSD (7.x/8.x), so perhaps this is related. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/174749 > > Another PR for the same problem but specific to IPFW and 8.2-RELEASE > > http://www.freebsd.org/cgi/query-pr.cgi?pr=157796 > > I am hoping someone reading this can give the problem the attention it > deserves. Thank you. > > -Nick > _______________________________________________ > 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"