ZNC.el icon indicating copy to clipboard operation
ZNC.el copied to clipboard

Connecting to multiple networks causes erratic behavior

Open rschuetzler opened this issue 11 years ago • 10 comments

I have a ZNC bouncer set up with one account connecting to multiple networks. Using znc-erc to connect to a single network works great, but upon connecting to the second network, either with znc-erc, or immediately with znc-all, everything goes crazy. Every IRC buffer with changed content gets automatically pulled up in the right-side frame. I can kill the frame, but it comes back at some point no matter what I do. I also cannot figure out a way to see my channels on the second network.

Also, once I connect to the second network, all of my messages begin showing up duplicated and all spaced out.

rschuetzler avatar Nov 01 '14 00:11 rschuetzler

That does not happen here.

jeroentbt avatar Aug 04 '15 21:08 jeroentbt

That does not happen here.

You're probably running an older version of ZNC.

@rschuetzler this seems like a dupe of #9?

strugee avatar Aug 05 '15 16:08 strugee

@strugee I am running a bit behind indeed (ZNC 1.4)

jeroentbt avatar Aug 05 '15 22:08 jeroentbt

@jeroentbt I'm running 1.4, too. That's not sufficiently far behind to not trigger this bug... weird that you're not seeing it. Do you have multiple networks in one user?

strugee avatar Aug 06 '15 01:08 strugee

@strugee yes, two (debian and freenode)

I have this set up in my config:

(setq znc-servers (quote (("my.znc.host" 16667 t (
    (freenode "jeroen/freenode" "hunter2")
    (debian "jeroen/debian" "hunter2"))))))

jeroentbt avatar Aug 06 '15 19:08 jeroentbt

@jeroentbt Well, that's why you're not seeing it. You're duplicating the network in the username. The point of #14 is tor ZNC.el to use the network slug, and have the username be the same. E.g.:

(setq znc-servers
      '(("znc.example.org" 1337 t
     ((freenode "alex" "hunter2")
      (moznet "alex" "hunter2")
      (oftc "alex" "hunter2")
      (gimpnet "alex" "hunter2")))))

strugee avatar Aug 06 '15 22:08 strugee

I used to have it like that but then I got two network buffers, both connecting to OFTC (referenced as debian in my config).

Furthermore, in those network buffer I get:

09:41:28 -*status- You have several networks configured, but no network was specified for the
                   connection.
09:41:28 -*status- Selecting network [debian]. To see list of all configured networks, use /znc
                   ListNetworks
09:41:28 -*status- If you want to choose another network, use /znc JumpNetwork <network>,
                   or connect to ZNC with username jeroen/<network> (instead of just jeroen)

Hence the user/network

jeroentbt avatar Aug 07 '15 07:08 jeroentbt

I used to have it like that but then I got two network buffers, both connecting to OFTC (referenced as debian in my config).

Yes. That's exactly what this bug is describing.

strugee avatar Aug 07 '15 17:08 strugee

Put the network slug in the username. So rather than:

 (moznet "alex" "hunter2")

you need to include the slug in the username like so:

(moznet "alex/moznet" "hunter2")

This is one of ZNC's built-in methods for dealing with multiple networks for the same user.

rschuetzler avatar Nov 14 '15 11:11 rschuetzler

@hammerheadlemon you could also do what I do and patch ZNC.el with #14.

strugee avatar Nov 14 '15 17:11 strugee