View Issue Details

IDProjectCategoryView StatusLast Update
0003262unrealircdpublic2010-07-14 17:51
ReporterSmithsonian Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
OSWindowsOS VersionXP 
Product Version3.2-beta5 
Summary0003262: Bug
DescriptionWhen you are shunned your disconnect button on your irc client will not work (usually uses /disconnect)
TagsNo tags attached.
3rd party modules

Activities

aquanight

2007-03-16 23:11

reporter   ~0013316

Last edited: 2007-03-16 23:13

Say what?

/disconnect is a "brutal quit" - client says it's going to quit and just disconnects. You must be thinking of /quit (which in some clients just sends the quit and waits for disconnect). Think of it like a phone conversation: you could say "Bye" and wait for the other end to hang up (standard /quit), say "Bye" and then hang up (the "brutal quit"), or just hang up. Since "hanging up" is at the TCP/IP level, unreal can't prevent the client from doing so at all, especially since there are many software ways as well as hardware to end the connection without the ircd having a say: SIGKILL/force quit the client (software), shutdown the computer (mix software/hardware), unplug computer (hardware) from either network or power, remove network adapter (if hotpluggable such as USB / pcimcia / cardbus / etc, and obviously hardware), turn off the router/modem, (dialup only:) pick up the phone and push random tones into the connection, making the modem go ZOMGWTF *hangup* (hardware, with a dab of software as the modem firmware is what goes ZOMGWTF).

ircd-level shun simply cannot prevent disconnecting. at all. /quit might not work, but I doubt it. If the "disconnect" button doesn't work, then it is your client that's broken.

Stealth

2007-03-17 09:24

reporter   ~0013317

Last edited: 2007-03-17 09:28

What client are you using? (version of it too)

There was one mIRC version which did a "soft disconnect", where it waited for the server to close the connection. That feature was taken back out in the next version.

EDIT: And I hope you're not really running 3.2-beta5

Issue History

Date Modified Username Field Change
2007-03-16 20:29 Smithsonian New Issue
2007-03-16 23:11 aquanight Note Added: 0013316
2007-03-16 23:13 aquanight Note Edited: 0013316
2007-03-17 09:24 Stealth Note Added: 0013317
2007-03-17 09:28 Stealth Note Edited: 0013317
2007-04-15 08:10 stskeeps Status new => feedback
2010-07-14 17:51 syzop QA => Not touched yet by developer
2010-07-14 17:51 syzop U4: Need for upstream patch => No need for upstream InspIRCd patch
2010-07-14 17:51 syzop Status feedback => closed
2010-07-14 17:51 syzop Resolution open => no change required