swee/IRCat
swee/IRCat
1
0
Fork 0
Code Issues 5 Pull requests Releases 1 Packages 1 Wiki Activity Actions

Problem with client-side PING #9

New issue
Closed
opened 2025-08-16 18:32:29 -07:00 by swee · 1 comment
swee commented 2025-08-16 18:32:29 -07:00
Owner
Copy link

TCP logs:
ZNC sends

PING 1733847626047\r\n

IRCd sends

:swee.codes PONG swee.codes :1733847626047\r\n

ZNC sends

PING 1733847626047\r\n

IRCd sends

:swee.codes PONG swee.codes :1733847626047\r\n

ZNC sends

PING 1733847626047\r\n

IRCd sends

:swee.codes PONG swee.codes :1733847626047\r\n

A few seconds later, ZNC sends

PING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\n

IRCd sends

:swee.codes PONG swee.codes :1733847626047\r\n
:swee.codes PONG swee.codes :1733847626047\r\n
:swee.codes PONG swee.codes :1733847626047\r\n
:swee.codes PONG swee.codes :1733847626047\r\n
:swee.codes PONG swee.codes :1733847626047\r\n
:swee.codes PONG swee.codes :1733847626047\r\n

All lines in different send() functions
A few mins while spam pinging, ZNC quits.

<*status> Disconnected from IRC. Reconnecting...
<*status> Connected!

How to fix? Did I do something wrong with server PONG?

TCP logs: ZNC sends ``` PING 1733847626047\r\n ``` IRCd sends ``` :swee.codes PONG swee.codes :1733847626047\r\n ``` ZNC sends ``` PING 1733847626047\r\n ``` IRCd sends ``` :swee.codes PONG swee.codes :1733847626047\r\n ``` ZNC sends ``` PING 1733847626047\r\n ``` IRCd sends ``` :swee.codes PONG swee.codes :1733847626047\r\n ``` A few seconds later, ZNC sends ``` PING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\nPING 1733847626047\r\n ``` IRCd sends ``` :swee.codes PONG swee.codes :1733847626047\r\n :swee.codes PONG swee.codes :1733847626047\r\n :swee.codes PONG swee.codes :1733847626047\r\n :swee.codes PONG swee.codes :1733847626047\r\n :swee.codes PONG swee.codes :1733847626047\r\n :swee.codes PONG swee.codes :1733847626047\r\n ``` All lines in different send() functions A few mins while spam pinging, ZNC quits. ``` <*status> Disconnected from IRC. Reconnecting... <*status> Connected! ``` How to fix? Did I do something wrong with server PONG?
swee commented 2025-08-16 18:32:56 -07:00
Author
Owner
Copy link

Apparently, Client-side PING wasn’t the issue, the server marks the client as “ping pending” AFTER PINGING, so the client sends PONG before it was marked.

The spam pinging is normal ZNC behavior it seems.

I have fixed this problem, thank you all (people from IRC) for the support, and sorry for the misunderstanding. :,3

Commits that fixed the problem:

Apparently, Client-side PING wasn’t the issue, the server marks the client as “ping pending” AFTER PINGING, so the client sends PONG before it was marked. The spam pinging is normal ZNC behavior it seems. I have fixed this problem, thank you all (people from IRC) for the support, and sorry for the misunderstanding. :,3 Commits that fixed the problem: - f67203ceb2 - 25fda4534d
swee closed this issue 2025-08-16 18:32:56 -07:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.0.7
Labels
Clear labels   
Compat
Breaking
Breaking change that won't be backward compatible

  
Discourse migration

This post was migrated from Discuss Swee.

  
Feature
IRCv3
Discusses, fixes, or adds support for an IRCv3 feature.

  
Feature
RFC1459
Discusses, fixes, or adds support to an RFC 1459 standard.

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat
Breaking
Discourse migration
Feature
IRCv3
Feature
RFC1459
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: swee/IRCat#9
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?