You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ircd does not appear to properly wipe out the +L channel redirect mode during netburst. It appears to the client that it sets -L during the burst, but a /check #channel reveals that +L is still set, and is still active for any client trying to join.
With my services disconnected, I can cycle one of its registered channels and set +L to redirect to another test channel. When I reconnect the services, the net burst deops me (as it should), ops the bot and appears to set -L. However, any client that tries joining the channel still gets redirected, and a /check #channel reveals that +L is still set.
This also happens between client servers. Also, when I'm in the channel on a newer timestamp, I still see -L being set when the services connects, even when +L was never set in the first place.
Discovered this by accident...
The ircd does not appear to properly wipe out the +L channel redirect mode during netburst. It appears to the client that it sets -L during the burst, but a /check #channel reveals that +L is still set, and is still active for any client trying to join.
With my services disconnected, I can cycle one of its registered channels and set +L to redirect to another test channel. When I reconnect the services, the net burst deops me (as it should), ops the bot and appears to set -L. However, any client that tries joining the channel still gets redirected, and a /check #channel reveals that +L is still set.
This also happens between client servers. Also, when I'm in the channel on a newer timestamp, I still see -L being set when the services connects, even when +L was never set in the first place.
cycle channel
[18:10.42] ***
[18:10.42] *** Information for channel #sometestchannel
[18:10.42] ***
[18:10.42] *** Creation time:: Sun Jan 3 18:18:38 2016
[18:10.43] *** Topic::
[18:10.43] *** Channel mode(s):: +tn
[18:10.43] *** Users (@ = op, % = halfop, + = voice, < = delayed)
[18:10.43] *** @StoneC0ld ([email protected]) (Blarg)
[18:10.43] ***
[18:10.43] *** Total users:: 1 (1 ops, 0 halfops, 0 voiced, 0 clones, 0 authed, 0 delayed)
[18:10.43] ***
[18:10.43] *** Bans on channel::
[18:10.43] ***
[18:10.43] ***
[18:10.43] *** Excepts on channel::
[18:10.43] ***
[18:10.43] ***
[18:10.58] *** StoneC0ld sets mode: +L #test1
[18:11.09] *** X ([email protected]) has joined #sometestchannel
[18:11.09] *** .Nefarious sets mode: -Lo+tno StoneC0ld X
[18:11.19] **
[18:11.19] *** Information for channel #sometestchannel
[18:11.19] ***
[18:11.19] *** Creation time:: Tue Apr 30 12:40:36 2013
[18:11.19] *** Topic::
[18:11.19] *** Channel mode(s):: +tnL #test1
[18:11.19] *** Users (@ = op, % = halfop, + = voice, < = delayed)
[18:11.19] *** @x ([email protected]) (For help: /msg X ShowCommands)
[18:11.19] *** StoneC0ld ([email protected]) (Blarg)
[18:11.19] ***
[18:11.19] *** Total users:: 2 (1 ops, 0 halfops, 0 voiced, 0 clones, 0 authed, 0 delayed)
[18:11.19] ***
[18:11.19] *** Bans on channel::
[18:11.19] ***
[18:11.19] ***
[18:11.19] *** Excepts on channel::
[18:11.19] ***
[18:11.19] ***
The text was updated successfully, but these errors were encountered: