From: "Michael Ströder" <michael@stroeder.com>
To: galene@lists.galene.org
Subject: [Galene] Interferences with Zoom or other VC software
Date: Thu, 4 Mar 2021 17:11:13 +0100 [thread overview]
Message-ID: <8b13e461-63c9-e2af-f404-2d6448834bc1@stroeder.com> (raw)
HI!
Disclaimer: This is likely at least partially off-topic. But maybe it's
an interesting interop issue relevant for this community.
I generally recommend users to switch off all other video-conferencing
apps when connecting to my Galène instance. Because often mics and
cameras are blocked etc. But hey, users don't care much of what I write.
One user had serious connection problems today, we couldn't solve, and
thus I've searched through the logs.
What I found strange was the IP address 198.251.148.185 connecting to
the classic STUN port 3478. This port is not mentioned in Galène's
ice-servers.json. Well, could be the usual script kiddy.
But the really strange thing is that this seems to be a Zoom address:
$ whois 198.251.148.185
NetRange: 198.251.128.0 - 198.251.255.255
CIDR: 198.251.128.0/17
NetName: ZVC
NetHandle: NET-198-251-128-0-1
Parent: NET198 (NET-198-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Zoom Video Communications, Inc (ZVC)
We don't have a Zoom client installed. And our own browsers were
definitely not participating in any Zoom-related sessions.
Any idea what's going on?
Are they simply scanning the whole Internet for STUN servers?
Or are they tracking other video-conference apps on the client of the
remote user?
Ciao, Michael.
reply other threads:[~2021-03-04 16:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b13e461-63c9-e2af-f404-2d6448834bc1@stroeder.com \
--to=michael@stroeder.com \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox