From owner-freebsd-net Sat May 19 10:56:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id A0DAA37B422 for ; Sat, 19 May 2001 10:56:25 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id KAA86796; Sat, 19 May 2001 10:56:24 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.3/8.11.3) id f4JHtbe85136; Sat, 19 May 2001 10:55:37 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200105191755.f4JHtbe85136@arch20m.dellroad.org> Subject: Re: conflict ng_socket and ordinary tcp_socket? In-Reply-To: <31A473DBB655D21180850008C71E251A031AAF58@mail.kebne.se> "from Gunnar Olsson at May 17, 2001 01:52:57 pm" To: Gunnar Olsson Date: Sat, 19 May 2001 10:55:37 -0700 (PDT) Cc: "Freebsd Net (E-mail)" X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Gunnar Olsson writes: > Hi there, > does anyone know if this is a known problem or > if it should not work? > > ------------------ tcp-socket ---------------- > | Process1 |------------------------>| Process2 | > ----------------- ------------------ > | > | ng_socket > | > v > hookname: lower > path: rl0: > > I have two processes. > Process1 is a "tcp client", i.e. it wants to send a > packet to process2, which is the "tcp server". > The process2 goes to listen and waits for packets > from Process1. If the client now sends packets > it works just fine. Now to the problem. > > When Process2 receives packet from Process1, > he wants to send the packet further to the ethernet > driver, i.e Process2 opens up a ng_socket to > the hookname: lower of the driver. When sending > the connect message to the hook in the driver the > machine dies:-( > > If removing the tcp_socket, i.e having all in one process > everything works just fine. When splitting up in 2 processes > and connecting the ng_socket first and the tcp_socket after, > I can send one packet down all the way, but then the tcp_server, > i.e. Process2, go to wait state: recv and the machine dies. Can you get a panic backtrace? (see FreeBSD handbook for how). -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message