Daniel Kahn Gillmor wrote: > socat also appears to have this misbehavior, though it can be avoided by > supplying the reuseaddr option to the listening socket. Looking at the > socat source, it appears that this is related to the SO_REUSEADDR option.
That sounds right.. I remember it was SO_SOMETHING. :-) BTW: ./simpleproxy.c: if (setsockopt(SockFD, SOL_SOCKET, SO_REUSEADDR, (void*) > It's not clear to me if this should be implemented automatically for > every listening connection for redir, or if it warrants an additional > command-line option. I'm inclined to avoid additional command line > options (the UI is already too clumsy and ill-structured). Can you > think of a scenario where it would be a bad thing to have either of > these socket options set? Been a while sice I last dealt with this issue, but I can't think of any reason not to, and another proxy does, so.. -- see shy jo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
