From: Robert Pluim <rpluim@gmail.com>
To: Ship Mints <shipmints@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 14:30:16 +0100 [thread overview]
Message-ID: <87wmfy309j.fsf@gmail.com> (raw)
In-Reply-To: <CAN+1Hbq9800zNkBk8CKfNbK-c0w54mCj_gkqu=drytRsfKBuPQ@mail.gmail.com> (Ship Mints's message of "Tue, 17 Dec 2024 08:11:36 -0500")
>>>>> On Tue, 17 Dec 2024 08:11:36 -0500, Ship Mints <shipmints@gmail.com> said:
Ship> Good catch. Bug could be either or both Apple or vendor +/- the VPN
Ship> implementation and if it also uses Network Extension Framework filters or
Ship> whatever. The BSD-derived source code in question in netinet hasn't really
Ship> changed appreciably in ages. Could also be an implied "6to4" bridge that
Ship> the VPN sets up that screws things up. With the VPN running, go go System
Ship> Preferences...Network...and you should be able to visually identify if
Ship> there's a virtual "port" or relay.
I suspect vendor more than Apple, since I donʼt see such behaviour
with either of the two VPN clients I have on my macOS machine.
Robert
--
next prev parent reply other threads:[~2024-12-17 13:30 UTC|newest]
Thread overview: 16+ 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
2024-12-17 13:14 ` Ship Mints
2024-12-17 13:30 ` Robert Pluim [this message]
2024-12-18 0:16 ` Stefan Kangas
2024-12-18 16:03 ` Robert Pluim
2024-12-19 15:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmfy309j.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=74907@debbugs.gnu.org \
--cc=shipmints@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.