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: Mon, 16 Dec 2024 12:46:13 +0100 [thread overview]
Message-ID: <87jzbz6ebe.fsf@gmail.com> (raw)
In-Reply-To: <CAN+1HboZQ0+3SEg8uv+7Po9w10mniuX5tQxd+Mmu8rJA+Y4+CA@mail.gmail.com> (Ship Mints's message of "Mon, 16 Dec 2024 06:23:12 -0500")
>>>>> On Mon, 16 Dec 2024 06:23:12 -0500, Ship Mints <shipmints@gmail.com> said:
Ship> With the VPN running and without, check the value
Ship> of (network-lookup-address-info "localhost") and see if the VPN-regime
Ship> value looks sensible. It is possible that your VPN set up is absconding
Ship> with host resolution. I'd bet that (nsm-should-check "127.0.0.1") works
Ship> fine under both scenarios. You could at the command line also ping
Ship> localhost and see what that reveals or try macOS network "reachability"
Ship> diagnostic utility scutil -W -r localhost.
Looking at the code, itʼs possible that `network-lookup-address-info'
needs a small adjustment. Letʼs see what Stefan says.
Robert
--
next prev parent reply other threads:[~2024-12-16 11:46 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 [this message]
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
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=87jzbz6ebe.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.