From owner-freebsd-net@FreeBSD.ORG Sun Aug 24 05:59:11 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2254C106567E for ; Sun, 24 Aug 2008 05:59:11 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outW.internet-mail-service.net (outw.internet-mail-service.net [216.240.47.246]) by mx1.freebsd.org (Postfix) with ESMTP id 041138FC19 for ; Sun, 24 Aug 2008 05:59:10 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id A6AEE2478; Sat, 23 Aug 2008 22:59:11 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 3B60D2D60BF; Sat, 23 Aug 2008 22:59:10 -0700 (PDT) Message-ID: <48B0F8AD.1090601@elischer.org> Date: Sat, 23 Aug 2008 22:59:09 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Kip Macy References: <200808221719.m7MHJY25090566@lava.sentex.ca> <20080822191146.T66593@maildrop.int.zabbadoz.net> <200808221922.m7MJMcUN091064@lava.sentex.ca> <3c1674c90808231916l2c92a8e4sae0f191af31b5870@mail.gmail.com> <200808240312.m7O3CZS0098145@lava.sentex.ca> <48B0F722.3050005@elischer.org> <3c1674c90808232255s30a6fce7ma8e081e935a6adbc@mail.gmail.com> In-Reply-To: <3c1674c90808232255s30a6fce7ma8e081e935a6adbc@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , freebsd-net@freebsd.org, Mike Tancsa Subject: Re: strange TCP issue on RELENG_7 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2008 05:59:11 -0000 Kip Macy wrote: > On Sat, Aug 23, 2008 at 10:52 PM, Julian Elischer wrote: >> Mike Tancsa wrote: >>> At 10:16 PM 8/23/2008, Kip Macy wrote: >>>> Can you help me out a bit with your workload? >>>> >>>> tcp_offload_connect(...) needs to determine which interface an address >>>> corresponds to see if that interface supports TCP offload. The code >>>> does the exact same thing as ip_output does except it doesn't have the >>>> inpcb locked (which isn't used as part of the route lookup). >>> This is the only RELENG_7 box that I have where it routes tcp packets >>> asymmetrically, so that sounds like it might be the portion that is badly >>> interacting. The server has just one default gateway, which is out em0, but >>> clients all over the net will connect to IP addresses aliased on lo0 and to >>> the one IP on em1. But all connections exit out em0 other than connected >>> routes of course. >>> >>> ---Mike >>> >>>> Julian has worked in this code most recently, maybe he has some idea >>>> what is going on. >>>> >> huh? wha? I haven't been following this thread.. what's up? >> > Julian - see previous e-mails, the arp cache gets messed up as a > result of calling rtalloc in tcp_offload.c - which is done to > determine which interface will be used for connection. Any thoughts on > why it may end up with dozens of bogus entries? > > -Kip has anyone tried the same scenario on -current?