Bug #192
open
using "hide ping pong event" in mIRC doesn't work with bip
Added by Pierre-Louis Bonicoli almost 14 years ago.
Updated almost 11 years ago.
Description
Reported by DoDzy, thank to him !
i still get [10:35] * PONG from oftc <
it used to work when i was using psybnc
nvm, after all it is my client misbehaving
"If mIRC sends a PING with a parameter, it expects a PONG response with that parameter. This
is meant to be standard PING/PONG behaviour. If your bouncer is intercepting the message and
is not replying correctly, then mIRC will not work."
Related issues
1 (1 open — 0 closed)
- Target version changed from 0.8.8 to 0.8.9
That's what bip replies as far as I can see:
<telnet>
PING toto
:servername PONG toto
</telnet>
I wonder what mirc expects here. maybe the :servername makes it unhappy. Any idea on how to know?
- Assignee deleted (
Pierre-Louis Bonicoli)
- Status changed from New to Feedback
- Priority changed from Normal to Low
- Target version deleted (
0.8.9)
- Help Needed set to No
More info is needed. Currently it doesn't seem bip is behaving badly.
Arnaud Cornet wrote:
That's what bip replies as far as I can see:
<telnet>
PING toto
:servername PONG toto
</telnet>
I wonder what mirc expects here. maybe the :servername makes it unhappy. Any idea on how to know?
<< PING LAG130951
>> :servername PONG servername :LAG130951
here's the answer the irc client (mIRC and konversation) expects.
it's answer from raw debug mode of konversation on the normal irc server.
but bip answer is
<< PING LAG130714
>> :servername PONG LAG130714
and client dos not recognizes the answer. konversation in this instance reconnect after 3 min.
- Has duplicate Bug #355: Invalid PONG response added
Also available in: Atom
PDF