View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001915 | unreal | ircd | public | 2004-07-02 05:20 | 2004-07-10 11:29 |
| Reporter | ObiWan | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | open | ||
| Product Version | 3.2 | ||||
| Summary | 0001915: Nick collision on connect | ||||
| Description | I don't know if this is a bug but. I just connected to another server on the network and instead of giving me "this nickname is already in use" a big "Nick Collision" and killed me. | ||||
| 3rd party modules | |||||
|
|
It's possible in for example the following situation: if you connect to A, then semi-disconnect and connect to B.. and there's enough lag between A<->B (depending on how fast you switched... a few seconds is usually enough). This is because B didn't get your connect to A yet when you are registering @ B, so it allows you in.. then when you are connected it suddenly (finally ;p) receives the msg from A which causes a nick collision.. then a few seconds later it sees (finally) the quit from A and then it's ok again :P. edited on: 2004-07-02 09:12 |
|
|
But I didn't disconnect on the other server so this would be impossible from the start. |
|
|
Well, it doesn't have to be you ;). Anyway, check the kill msg (ircd.log, or perhaps you've seen it yourself).. eg: [Fri Jul 2 15:20:21 2004] - KILL ([email protected]) by testlink.test.net(testlink!testlink.test.net (Nick Collision)) Or a tad more useful... just do /whowas nick and check user@hosts and the date/time of every entry. Anyway, again.. 95% chance it was harmless :P |
|
|
I was on romulus.st-city.net with the nick Obi_Wan. In mIRC my primary nick is Obi_Wan so I connected to vulkan.st-city.net to test something. When I connected it gave me nick collision and disconnected me from vulkan. Then I reconnected and the server told me that Obi_Wan was already in use. I've got NetAdmin on the network so I saw that it was a nick collision. |
|
|
In that case it was most likely lag between the servers: 1) You connect to romulus.* as Obi_Wan. 2) You then /server -m vulkan.*. Because of lag, vulkan hasn't received your connection on romulus.* yet, so it allows your normal nick of Obi_Wan. 3) Vulkan finally receives the introduction of Obi_Wan on romulus.* and because the Time Stamp is lower on romulus, it KILLs you on vulkan.* with a Nick Collision message. |
|
|
But I've been on romulus for about more than 70 hours or something and I don't think that vulkan is that laggy. |
|
|
No, it doesn't have to be 70 hours of lag. The important part is the timestamp. If your clocks are out of synch, that can cause just this kind of problem. That's exactly why we tell people when the clocks are more than ~3 seconds out of sync, it can be a serious issue. Check /tsctl alltime. My guess is you'll find some differences. |
|
|
This is normal. If someone with the same nickname on another server has an earlier timestamp than yourself, it will kill the newest client. |
|
|
assuming bogus. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-07-02 05:20 | ObiWan | New Issue | |
| 2004-07-02 09:09 | syzop | Note Added: 0006837 | |
| 2004-07-02 09:12 | syzop | Note Edited: 0006837 | |
| 2004-07-02 09:13 | ObiWan | Note Added: 0006839 | |
| 2004-07-02 09:32 | syzop | Note Added: 0006841 | |
| 2004-07-02 09:38 | ObiWan | Note Added: 0006842 | |
| 2004-07-02 11:42 | aquanight | Note Added: 0006843 | |
| 2004-07-02 11:48 | ObiWan | Note Added: 0006846 | |
| 2004-07-02 12:09 |
|
Note Added: 0006850 | |
| 2004-07-09 23:00 | ryangard | Note Added: 0006963 | |
| 2004-07-10 11:29 | syzop | Status | new => closed |
| 2004-07-10 11:29 | syzop | Note Added: 0006967 |
