From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 11 04:50:35 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9FE5106566B for ; Wed, 11 Jul 2012 04:50:35 +0000 (UTC) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD3C8FC12 for ; Wed, 11 Jul 2012 04:50:35 +0000 (UTC) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.11/8.12.11) with ESMTP id q6B4VBSC014473 for ; Wed, 11 Jul 2012 00:31:11 -0400 (EDT) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.11/8.12.11/Submit) id q6B4VBbU014472 for freebsd-hackers@freebsd.org; Wed, 11 Jul 2012 00:31:11 -0400 (EDT) (envelope-from wayne) Date: Wed, 11 Jul 2012 00:31:11 -0400 From: "Michael R. Wayne" To: freebsd-hackers@freebsd.org Message-ID: <20120711043110.GR42080@manor.msen.com> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 11 Jul 2012 11:01:33 +0000 Subject: kernel ignores default route? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2012 04:50:36 -0000 One of my machines is doing something I can not understand and may have uncovered some form of bug. The kernel appears to be ignoring the default route. Had several people look this over, we can't determine where the route is being hidden. This is 7.4-RELEASE-p2. I suspect that rebooting the box will clear the problem but I would REALLY like to figure out why the routing table is not being followed. I have two routers, on the same ethernet at: 148.59.4.1 (default) 148.59.4.3 & 139.171.192.26 148.59.4.2 (FreeBSD box) This is correct (see routing table below): > traceroute -n 148.59.48.1 traceroute to 148.59.48.1 (148.59.48.1), 64 hops max, 40 byte packets 1 139.171.192.26 7.366 ms 4.748 ms 6.879 ms 2 148.59.48.1 3.357 ms 5.130 ms 3.006 ms And "route" agrees: > route -n get 148.59.48.1 route to: 148.59.48.1 destination: 148.59.48.0 mask: 255.255.255.192 gateway: 148.59.4.3 interface: fxp0 flags: recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 This is not, it should go out 148.59.4.1: > traceroute -n 148.59.80.1 traceroute to 148.59.80.1 (148.59.80.1), 64 hops max, 40 byte packets 1 139.171.192.26 6.874 ms 6.496 ms 4.288 ms 2 139.171.198.139 5.907 ms 8.251 ms 4.156 ms 3 198.22.65.217 5.246 ms 4.961 ms 4.719 ms 4 198.22.65.222 14.096 ms 4.760 ms 6.545 ms 5 148.59.80.1 5.753 ms 5.813 ms 5.952 ms "route" says it should: > route -n get 148.59.80.1 route to: 148.59.80.1 destination: default mask: default gateway: 148.59.4.1 interface: fxp0 flags: recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 netstat -rn (minus a few 148.59.4.x machines that can be ignored) Internet: Destination Gateway Flags Refs Use Netif Expire default 148.59.4.1 UGS 0 667619000 fxp0 10.151.89.0/24 link#1 UC 0 0 em0 10.151.89.49 00:c0:9f:21:b2:31 UHLW 1 14 lo0 127.0.0.1 127.0.0.1 UH 2 23811 lo0 148.59.4.0/27 link#2 UC 0 0 fxp0 148.59.4.1 00:a0:c8:2c:5f:38 UHLW 2 602 fxp0 47 148.59.4.3 00:a0:c8:2c:5f:38 UHLW 5 0 fxp0 23 148.59.4.64 ff:ff:ff:ff:ff:ff UHLWb 1 14991 em0 => 148.59.4.64/26 link#1 UC 0 0 em0 148.59.4.66 00:02:b3:e9:0e:c0 UHLW 1 8098 em0 903 148.59.4.130 148.59.4.129 UH 0 2073 tun0 148.59.48.0/26 148.59.4.3 UG1 0 1158 fxp0 148.59.50.0/24 148.59.4.3 UG1 0 194507 fxp0 148.59.80.39 148.59.4.3 UGH1 0 0 fxp0 198.11.50.21 148.59.4.3 UGH1 0 0 fxp0 224.0.0.5 127.0.0.1 UGH1 0 0 lo0 224.0.0.6 127.0.0.1 UGH1 0 0 lo0