Hello fellow netsed interested people ;) netsed does not have UDP support, I plan to implement it, but it's not as easy as it seams: UDP is by nature not connected, so it's not possible to know when the client or server has closed it's socket...
As the requirement are not clear (I guess user seen netsed fail to work with UDP have switched to other solutions) I'm planning to take the following assumption: * whenever a client send a datagram to a server it expects one and only one datagram back So netsed UDP implementation can be: * listen for incoming datagram * on each reception: fork * the child process then - sed the datagram - forward it - wait for a response (with a timeout as UDP does not guaranty that this datagram will be received) - sed the datagram - send it back to the incoming port - exit the child process I'll go for that but any suggestions or comments can be helpful, so feel free ;) Note: Using a child process to wait for only one response look overkill but it's closer to what is done for TCP, so I don't plan on doing anything more fancy now. Julien VdG -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
