Date: Wed, 29 Jan 1997 00:17:37 -0800 (PST) From: Archie Cobbs <archie@whistle.com> To: ari.suutari@ps.carel.fi (Ari Suutari) Cc: archie@whistle.com, brian@awfulhak.demon.co.uk, hackers@freebsd.org, cmott@srv.net Subject: Re: ipdivert & masqd Message-ID: <199701290817.AAA22387@bubba.whistle.com> In-Reply-To: <01BC0DC7.5A8AF380@sodium.ps.carel.fi> from Ari Suutari at "Jan 29, 97 09:32:31 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> I had these problems with latest 2.2-SNAP release and > maybe, just maybe with 2.2-ALPHA. It was quite simple > to reproduce the problem - it occurred every time I opened > a TCP connection from the same machine that natd was > running on. Everything works well if packets come > from different interface and are routed to another. > > I did some investigations in the kernel land (not being > any expert on that), but it seemed like the ip_divert_ignore > flag was still set (from processing a outgoing packet) when > an incoming packet arrived. Can I get a quick sanity check on something... the divert code is programmed under the assumption that ip_input() and ip_output() can never sleep (ie., no other packet can be treated before the function returns). This is true, right? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701290817.AAA22387>