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 [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
