From: Ship Mints <shipmints@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 74907@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#74907: 31.0.50; nsm-check-local-subnet-ipv4 test fails on macOS with VPN enabled
Date: Tue, 17 Dec 2024 08:11:36 -0500 [thread overview]
Message-ID: <CAN+1Hbq9800zNkBk8CKfNbK-c0w54mCj_gkqu=drytRsfKBuPQ@mail.gmail.com> (raw)
In-Reply-To: <87cyhq4gch.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Good catch. Bug could be either or both Apple or vendor +/- the VPN
implementation and if it also uses Network Extension Framework filters or
whatever. The BSD-derived source code in question in netinet hasn't really
changed appreciably in ages. Could also be an implied "6to4" bridge that
the VPN sets up that screws things up. With the VPN running, go go System
Preferences...Network...and you should be able to visually identify if
there's a virtual "port" or relay.
On Tue, Dec 17, 2024 at 7:57 AM Robert Pluim <rpluim@gmail.com> wrote:
> >>>>> On Tue, 17 Dec 2024 12:45:26 +0000, Stefan Kangas <
> stefankangas@gmail.com> said:
>
> Stefan> Thanks, that fixes the issue. Tested with and without VPN on
> macOS.
>
> Please let me know the name of the VPN client so that I can write a
> suitably scathing commit message (although itʼs possible this is
> macOSʼ fault).
>
> Robert
> --
>
[-- Attachment #2: Type: text/html, Size: 1403 bytes --]
next prev parent reply other threads:[~2024-12-17 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 2:03 bug#74907: 31.0.50; nsm-check-local-subnet-ipv4 test fails on macOS with VPN enabled Stefan Kangas
2024-12-16 10:56 ` Robert Pluim
2024-12-16 11:23 ` Ship Mints
2024-12-16 11:46 ` Robert Pluim
2024-12-16 21:55 ` Stefan Kangas
2024-12-17 7:36 ` Robert Pluim
2024-12-17 11:26 ` Stefan Kangas
2024-12-17 12:40 ` Robert Pluim
2024-12-17 12:45 ` Stefan Kangas
2024-12-17 12:57 ` Robert Pluim
2024-12-17 13:11 ` Ship Mints [this message]
2024-12-17 13:14 ` Ship Mints
2024-12-17 13:30 ` Robert Pluim
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN+1Hbq9800zNkBk8CKfNbK-c0w54mCj_gkqu=drytRsfKBuPQ@mail.gmail.com' \
--to=shipmints@gmail.com \
--cc=74907@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).