View Issue Details

IDProjectCategoryView StatusLast Update
0004504unrealircdpublic2015-12-26 10:22
ReportervNode1 Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version4.0.0 
Summary0004504: JOIN's on a server
DescriptionOn a link, I type /Join #test
the services says: 01CULF80C JOIN test
I join #test on a different nickname and see SVS2AGENT is there HOWEVER
when I /whois 01CULF80C
You get the response below.
-
[02:50] SVS2AGENT is [email protected].*.com * SVS2SOFTWARE.
[02:50] SVS2AGENT is using modes +iowrsxHtqW
[02:50] SVS2AGENT is identified for this nick
[02:50] SVS2AGENT using twisted.vnode.ovh get real.
[02:50] SVS2AGENT is an IRC Operator
[02:50] SVS2AGENT is the network Owner
[02:50] SVS2AGENT is logged in as kevin
[02:50] 01CULF80C End of /WHOIS list.
-
Steps To ReproduceLink a server/client that can see JOIN/PART
make a client join #test a chat room, it should show <some string> JOIN test

then u join that same channel, you will see the client's real name, but you can also do things to their id, ie kick/ban etc.
3rd party modulesNone Currently

Activities

vNode1

2015-12-24 23:12

reporter   ~0018935

Last edited: 2015-12-24 23:38

Also can /kick #channel-name 01CULF80C and it will kick the real client, as well as any other user to user command such as /msg 01CULF80C, /ctcp 01CULF80C ping, etc.


** EDIT: could this problem happen because the server isn't telling the other servers "NICK 1 nick host server" or w/e it used to send in older versions, there used to be logs for that too, now I don't see it being sent to the linked server?

vNode1

2015-12-24 23:41

reporter   ~0018936

Example of what connects show when they are near and far connects:
-
[03:30] -irc.vnode.ovh- *** Client connecting: wynd ([email protected]) [192.99.145.191] {clients}

[03:34] -irc.vnode.ovh- *** Client exiting: wynd ([email protected]) [192.99.145.191] (Client Exited)

*** THIS IS IF THE CLIENT IS CONNECTING ON THE SAME SERVER ^ (ABOVE)
*** BELOW: REMOTE SERVER

[03:34] -twisted.vnode.ovh- *** Client connecting: wynd ([email protected]) [192.99.145.191] {0}
-
[03:34] -twisted.vnode.ovh- *** Client exiting: wynd ([email protected]) [192.99.145.191] (Client Exited)


^^ DIFFERENT SERVER

You'll notice, if they connect on the same server as "me" it shows {clients}
if they're connecting on a remote server {0}
something isn't being shared on connects of clients to all servers, just locally it seems.

syzop

2015-12-25 10:33

administrator   ~0018937

Last edited: 2015-12-25 10:38

Just asking to be sure..

The ID you learned (01CULF80C), you only got that because of you looking at services traffic/logs, correct? There was no way a user got to know this information otherwise?

vNode1

2015-12-25 18:37

reporter   ~0018939

Last edited: 2015-12-25 18:51

Correct; however

If services.vnode is linked to irc.vnode
and the client connects on IRC.vnode - it shows NICKNAME join #channel
if they connect to a server LINKED to irc.vnode, but not directly linked to services.vnode - it shows <ID> JOIN channel <without #>

syzop

2015-12-25 23:06

administrator   ~0018940

Last edited: 2015-12-25 23:11

It shows where? :D

Could you perhaps show it by some real example?
server1--server2--something
userX on server xyz
etc..

and you see traffic <<what>> at server <<which>>
as <<a user?>> or <<in logs / debug>>

so we can understand :)

vNode1

2015-12-25 23:23

reporter   ~0018941

The logs were over-written due to lots of traffic however: I believe I've figured it out

I have the linked "service" send NICKIP ESVID in PROTOCTL which I wasent sending in the older version of Unreal

Which then changes all joins to this: :irc.vnode.ovh SJOIN 1447736590 #Radio :gersga1

Instead of the older format: NICKNAME JOIN <Channel>

The problem I was having no longer reproduces.
I think it was my fault for not fully reading the new documentation on UID's

syzop

2015-12-26 10:22

administrator   ~0018942

Ok.

Issue History

Date Modified Username Field Change
2015-12-24 23:01 vNode1 New Issue
2015-12-24 23:12 vNode1 Note Added: 0018935
2015-12-24 23:38 vNode1 Note Edited: 0018935
2015-12-24 23:41 vNode1 Note Added: 0018936
2015-12-25 10:33 syzop Note Added: 0018937
2015-12-25 10:33 syzop Assigned To => syzop
2015-12-25 10:33 syzop Status new => feedback
2015-12-25 10:38 syzop Note Edited: 0018937
2015-12-25 18:37 vNode1 Note Added: 0018939
2015-12-25 18:51 vNode1 Note Edited: 0018939
2015-12-25 23:06 syzop Note Added: 0018940
2015-12-25 23:11 syzop Note Edited: 0018940
2015-12-25 23:23 vNode1 Note Added: 0018941
2015-12-26 10:22 syzop Note Added: 0018942
2015-12-26 10:22 syzop Status feedback => closed
2015-12-26 10:22 syzop Resolution open => no change required