Date: Thu, 17 May 2001 13:52:57 +0200 From: Gunnar Olsson <gunnar.olsson@xelerated.com> To: "Freebsd Net (E-mail)" <freebsd-net@freebsd.org> Subject: conflict ng_socket and ordinary tcp_socket? Message-ID: <31A473DBB655D21180850008C71E251A031AAF58@mail.kebne.se>
next in thread | raw e-mail | index | archive | help
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. Regards Gunnar ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gunnar Olsson Phone: +46 8 5062 5762 Xelerated Packet Devices AB Fax: +46 8 5455 3211 Regeringsgatan 67 Mobile: +46 73 3279765 SE-10386 Stockholm Web: http://www.xelerated.com Email: mailto:gunnar.olsson@xelerated.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31A473DBB655D21180850008C71E251A031AAF58>