adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-10-31 01:32:02 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

clientnotify: do not notify when the same IP log in as your user but under another network #417

New Issue
Open
opened 2026-10-05 04:19:42 +02:00 by adam · 3 comments
adam commented 2026-10-05 04:19:42 +02:00
Owner
Copy link
Copy source

I have a single user that connect to 3 networks.
when I start my local client, that connects to znc, it connects to the znc 3 fake networks. I then receive a message from znc on 2 of 3 connections saying "Another client authenticated as your user. Use the 'ListClients' command to see all 2 clients.".

I think that is unreasonable to notify me when I log in in the very same moment, from the same IP.

Sorry for not being clear, today my english is not the best.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I have a single user that connect to 3 networks. when I start my local client, that connects to znc, it connects to the znc 3 fake networks. I then receive a message from znc on 2 of 3 connections saying "Another client authenticated as your user. Use the 'ListClients' command to see all 2 clients.". I think that is unreasonable to notify me when _I_ log in in the very same moment, from the same IP. Sorry for not being clear, today my english is not the best. ## <bountysource-plugin> Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6383250-clientnotify-do-not-notify-when-the-same-ip-log-in-as-your-user-but-under-another-network?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> <!-- github-sync-id:49606586 -->
adam commented 2026-10-05 04:19:42 +02:00
Author
Owner
Copy link
Copy source

Not sure if there's really a solution to this. What if the connection comes from the same IP only you weren't expecting it? The module also does what it's supposed to. However, at the same time it can be annoying to have it show up on every network you are connected to. Imagine if you were on 20+ networks, as some folks are.

There is a work-around, though it's a bit of work to set up.

  1. Make another ZNC user, and make it Admin.
  2. Load the Notify_connect global module.
  3. Unload client_notify.
  4. Connect the ZNC user from step 1 to some secret channel you own (make one if you don't have one). Ideally on an IRC server you run, but it doesn't have to be.
  5. Set up some sort of IRC bot, and connect it to the user from step 1. Make sure it's set up so only you can do anything with the bot. It's best if the bot is dedicated to this purpose, as it will have Admin access on the ZNC.
  6. Using a script, module, or some sort of feature, relay all the PMs and Notices into the secret channel from step 4.

Using this method, you will still get the notices but they will only show up in one place, the secret channel.

Ben (MrC @ Freenode)

Not sure if there's really a solution to this. What if the connection comes from the same IP only you weren't expecting it? The module also does what it's supposed to. However, at the same time it can be annoying to have it show up on every network you are connected to. Imagine if you were on 20+ networks, as some folks are. There is a work-around, though it's a bit of work to set up. 1. Make another ZNC user, and make it Admin. 2. Load the Notify_connect global module. 3. Unload client_notify. 4. Connect the ZNC user from step 1 to some secret channel you own (make one if you don't have one). Ideally on an IRC server you run, but it doesn't have to be. 5. Set up some sort of IRC bot, and connect it to the user from step 1. Make sure it's set up so only you can do anything with the bot. It's best if the bot is dedicated to this purpose, as it will have Admin access on the ZNC. 6. Using a script, module, or some sort of feature, relay all the PMs and Notices into the secret channel from step 4. Using this method, you will still get the notices but they will only show up in one place, the secret channel. Ben (MrC @ Freenode) <!-- github-comment-id:63866191 -->
adam commented 2026-10-05 04:19:43 +02:00
Author
Owner
Copy link
Copy source

It can have some period of time starting with first client connecting when no need to report users from the same IP, yeah.
However, I foresee funny interaction of this with clients which implement RFC 6555

It can have some period of time starting with first client connecting when no need to report users from the same IP, yeah. However, I foresee funny interaction of this with clients which implement RFC 6555 <!-- github-comment-id:63877462 -->
adam commented 2026-10-05 04:19:44 +02:00
Author
Owner
Copy link
Copy source

Do many clients implement Happy Eyeballs?

Do many clients implement Happy Eyeballs? <!-- github-comment-id:63939359 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#417