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
PING is not allowed until the connection is completed aka 001 is received from the server in case that it is used as a client
Except the irc3 core plugin send it directly after the user..nick.
This is correct, unless you use sasl authentication, then the sequence is CAP LS / USER / NICK / CAP REQ / ..... / CAP END / PING except with irc3 the sequence it send is CAP LS / USER / NICK / PING / CAP REQ /...../ CAP END
the server will ignore the invalid ping request, and then the irc3 timeouts and reconnect.
Reproduction
take the examples/humans.py
add sasl_username and sasl_password to the config
connect to a server which supports sasl
remove the 1 of the clients to make it easier to debug
command for running this script: strace -e trace=network -f ./.venv/bin/python test1.py
PING is not allowed until the connection is completed aka
001
is received from the server in case that it is used as a clientExcept the irc3 core plugin send it directly after the user..nick.
This is correct, unless you use sasl authentication, then the sequence is
CAP LS / USER / NICK / CAP REQ / ..... / CAP END / PING
except with irc3 the sequence it send isCAP LS / USER / NICK / PING / CAP REQ /...../ CAP END
the server will ignore the invalid ping request, and then the irc3 timeouts and reconnect.
Reproduction
command for running this script:
strace -e trace=network -f ./.venv/bin/python test1.py
this is from againts ircnet, but the same happens on more networks
workaround
remove timeout entry in the config, then the ping/pong sequence is not started on connection
The text was updated successfully, but these errors were encountered: