On multiple networks jumpnetwork makes new network join all channels from the old one #192

New Issue

2026-10-05T04:03:29+02:00

adam commented

2026-10-05 04:03:29 +02:00

This issue is present on version 1.0.

I have two networks:
freenode
quakenet

When I connect to znc i am loaded with freenode channels and backlog.
I decide to take look on whats going on quakenet.
I query *status and write jumpnetwork quakenet
I observe quakenet joining all of the freenode channels among with the correct ones.

Simple workaround I do now I connect twice to znc in my irc client, while one connection is for freenode and other for quakenet.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/101811-on-multiple-networks-jumpnetwork-makes-new-network-join-all-channels-from-the-old-one?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

This issue is present on version 1.0. I have two networks: freenode quakenet When I connect to znc i am loaded with freenode channels and backlog. I decide to take look on whats going on quakenet. I query *status and write jumpnetwork quakenet I observe quakenet joining all of the freenode channels among with the correct ones. Simple workaround I do now I connect twice to znc in my irc client, while one connection is for freenode and other for quakenet. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/101811-on-multiple-networks-jumpnetwork-makes-new-network-join-all-channels-from-the-old-one?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin>

adam closed this issue

2026-10-05 04:03:29 +02:00

adam commented

2026-10-05 04:03:30 +02:00

Simple workaround I do now I connect twice to znc in my irc client, while one connection is for freenode and other for quakenet.

This is what you are supposed to do and it's not only workaround.

I believe this issue has nothing to zo with ZNC as it's your client storing channels that it's on and attempting to rejoin them after reconnect.

> Simple workaround I do now I connect twice to znc in my irc client, while one connection is for freenode and other for quakenet. This is what you are supposed to do and it's not only workaround. I believe this issue has nothing to zo with ZNC as it's your client storing channels that it's on and attempting to rejoin them after reconnect.

adam commented

2026-10-05 04:03:31 +02:00

ZNC tells the client to PART the channels when the JumpNetwork command is used. Your client is the issue.

Commit from 2011 before 1.0 release: https://github.com/znc/znc/commit/d3ffdbb2a62c111c80705b42ca8254d27f248010

ZNC tells the client to ```PART``` the channels when the ```JumpNetwork``` command is used. Your client is the issue. Commit from 2011 before 1.0 release: https://github.com/znc/znc/commit/d3ffdbb2a62c111c80705b42ca8254d27f248010

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#192