From owner-freebsd-net@FreeBSD.ORG Mon Jul 27 23:24:48 2009 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 8B85F106566B for ; Mon, 27 Jul 2009 23:24:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outP.internet-mail-service.net (outp.internet-mail-service.net [216.240.47.239]) by mx1.freebsd.org (Postfix) with ESMTP id 713A08FC14 for ; Mon, 27 Jul 2009 23:24:48 +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 1DEEEDC2F; Mon, 27 Jul 2009 16:24:48 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id B4EB42D6010; Mon, 27 Jul 2009 16:24:47 -0700 (PDT) Message-ID: <4A6E3743.7050708@elischer.org> Date: Mon, 27 Jul 2009 16:24:51 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: Oleg Sharoyko References: <1248704237.96833.127.camel@brain.cc.rsu.ru> <4A6DE356.6040006@elischer.org> <4A6DEE30.6000108@sfedu.ru> <4A6DFFA1.1010709@elischer.org> <4A6E0121.2020004@sfedu.ru> <4A6E05EC.8050401@elischer.org> <4A6E0A8B.5000103@sfedu.ru> <4A6E2666.2040906@elischer.org> In-Reply-To: <4A6E2666.2040906@elischer.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Wrong outgoing interface with multiple routing tables 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: Mon, 27 Jul 2009 23:24:48 -0000 Julian Elischer wrote: > Oleg Sharoyko wrote: >> >> Julian Elischer wrote: >> >>> great.. in your simple server, can you do the sockopt on the socket >>> AFTER you did the listen()? >>> (just as a test). >> >> Doesn't help. I have also tried to add setsockopt() after accept() >> (for a new socket) and in this case the only packet that is being sent >> out via wrong interface is the SYN+ACK from server. >> >> I'll try to look into the kernel code tomorrow and will report any >> findings. >> >> -- >> Oleg > > > in addition to the patches already sent you might like to add the > following line to netinet/tcp_input.c > > } > inc.inc_fport = th->th_sport; > inc.inc_lport = th->th_dport; > inc.inc_fibnum = so->so_fibnum; <------------- > /* > * Check for an existing connection attempt in syncache if > * the flag is only ACK. A successful lookup creates a new > * socket appended to the listen queue in SYN_RECEIVED > state. > */ in fact you might try just this on its own > _______________________________________________ > 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"