Date: Wed, 3 Dec 2008 17:40:01 -0500 From: "Benjie Chen" <benjie@addgene.org> To: "Peter Jeremy" <peterjeremy@optushome.com.au> Cc: freebsd-net@freebsd.org Subject: Re: Weird TCP connect issue in FreeBSD 6 Message-ID: <c53be070812031440k7660e022of8a77d1427fb1f47@mail.gmail.com> In-Reply-To: <20081203193609.GB58682@server.vk2pj.dyndns.org> References: <c53be070812021210u736bef58v79c2f80785308a5@mail.gmail.com> <20081203193609.GB58682@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter, Thanks for the response. When I had two IPs from two different subnets configured for the two NICs, I had the same error. So while I did have a configuration issue, the problem with replicated SYNs did occur even when the two NICs had IP addresses on different networks. Benjie On Wed, Dec 3, 2008 at 2:36 PM, Peter Jeremy <peterjeremy@optushome.com.au> wrote: > On 2008-Dec-02 15:10:11 -0500, Benjie Chen <benjie@addgene.org> wrote: >>I have a weird issue to report, and I am not sure if it's a bug or >>some other configuration problem. > > I would suggest it is a configuration problem. > >>Server is a dual NICed FreeBSD 6.2 system. For example, one NIC is em0 >>= 192.168.0.1, and the other one is em1 = 192.168.0.2. > > This is not a supported configuration - you cannot have addresses within > the same subnet on more than one interface. > >>I just switched to using IP aliasing on the same NIC, and so far I >>have not been able to re-produce the same problem. > > This is the correct configuration. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed behaviour. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c53be070812031440k7660e022of8a77d1427fb1f47>