Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Aug 2008 22:59:09 -0700
From:      Julian Elischer <julian@elischer.org>
To:        Kip Macy <kmacy@freebsd.org>
Cc:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-net@freebsd.org, Mike Tancsa <mike@sentex.net>
Subject:   Re: strange TCP issue on RELENG_7
Message-ID:  <48B0F8AD.1090601@elischer.org>
In-Reply-To: <3c1674c90808232255s30a6fce7ma8e081e935a6adbc@mail.gmail.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
Kip Macy wrote:
> On Sat, Aug 23, 2008 at 10:52 PM, Julian Elischer <julian@elischer.org> 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?





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48B0F8AD.1090601>