From owner-freebsd-stable@FreeBSD.ORG Fri Mar 19 10:59:45 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22759106567F for ; Fri, 19 Mar 2010 10:59:45 +0000 (UTC) (envelope-from kasahara@nc.kyushu-u.ac.jp) Received: from elvenbow.cc.kyushu-u.ac.jp (elvenbow.nc.kyushu-u.ac.jp [133.5.7.92]) by mx1.freebsd.org (Postfix) with ESMTP id BDF038FC2A for ; Fri, 19 Mar 2010 10:59:44 +0000 (UTC) Received: from localhost (kasahara@localhost [IPv6:::1]) by elvenbow.cc.kyushu-u.ac.jp (8.14.4/8.14.4) with ESMTP id o2JARjcA020983 for ; Fri, 19 Mar 2010 19:27:45 +0900 (JST) (envelope-from kasahara@nc.kyushu-u.ac.jp) Date: Fri, 19 Mar 2010 19:27:44 +0900 (JST) Message-Id: <20100319.192744.1739162714673139515.kasahara@nc.kyushu-u.ac.jp> To: stable@freebsd.org From: Yoshiaki Kasahara X-Fingerprint: CDA2 B6B6 6796 0DD3 9D80 2602 E909 4623 A15E A074 X-URL: http://www.nc.kyushu-u.ac.jp/~kasahara/ X-Mailer: Mew version 7.0.50 on Emacs 23.1.92 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: TSO and pf(4) reply-to/route-to combination problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2010 10:59:45 -0000 Hello, Could anyone who knows the TCP/IP stack well please review kern/144311? In summary, on a multi-homed server I have a trouble when using pf(4) 'reply-to' to return reply packets of incoming TCP connections to the incoming interface. When TSO is enabled on the interface which is used for the default route, redirecting packets to other interfaces using 'reply-to'(or 'route-to') causes massive 'ICMP unreachable - need to frag' storm on lo0 (up to 10Mbytes/sec on my server). The problem doesn't happen when TSO is disabled on the default NIC. I reproduced the problem on msk(4) and em(4), so I guess it is not device specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=144311 Regards, -- Yoshiaki Kasahara Research Institute for Information Technology, Kyushu University kasahara@nc.kyushu-u.ac.jp