Opened 6 years ago
Closed 5 years ago
#1098 closed defect (wontfix)
IRC client tunnel send quit at shutdown
| Reported by: | zzz | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.12 |
| Component: | apps/i2ptunnel | Version: | 0.9.8.1 |
| Keywords: | easy maybe | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
If the IRC client proxy automatically sends a /quit at shutdown, then you can come back with the same nick. I2P IRC servers generally have a very long idle time, so you are often still "connected" as far as the server knows, after you restart your router.
It seems like the streaming connections should already be closed or reset at shutdown, shouldn't that be sufficient? Is it not happening or is it just not getting to the server? Are there any improvements to make on the IRC server tunnel side?
Applies to SOCKS IRC also.
Subtickets
Change History (2)
comment:1 Changed 6 years ago by
comment:2 Changed 5 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I looked at this and it looks pretty difficult. Where we find out about shutdown is too far away from where the I2PSocket output stream is. If it's really hard or disruptive we shouldn't do it.