They're a bug, but the bug is just that it prints the warning, not so
much that it hurts anything. Well, okay, if the channel number
wrapped all the way around in 0.1 seconds or something, which I think
is impossible at least on modern computers, then it would cause a real
I've been too lazy to fix it so far. In case someone is feeling
motivated, what happens is:
- a connection isn't officially closed until both ends close it.
- when one end decides that it's closed, it sends the other end a
- if the other end has *already* decided it's closed, then it prints
...hmm, actually the closed connection getting a DATA message is
pretty bad; it means somebody closed it before they felt safe.
All in all, the connection closing state machine isn't quite right. It
needs to be thoroughly traced through and thought about. The final
fix will probably only be two or three lines, but it has to be the
*right* two or three lines :)
You received this message because you are subscribed to a topic in the Google Groups "sshuttle" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sshuttle/hTMW2OCpAmk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sshuttle+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sshuttle/c70cb7bd-6b79-449e-82fc-770fb4870687n%40googlegroups.com.