Re: lang/nodejs lang/npm problems

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On 21 December 2022 20:01:08 (+00:00), Greg Troxel wrote:

> 
> It's great you have a workaround, but I wonder what the root cause is.

I also wonder, it used to work in the same environment without a problem, 
perhaps three months ago when I last tried to do something with yarn on 
this NetBSD box. 

> It seems like a combination of:

> 

>   there are some addresses your machine cannot reach

My ISP still does not have any IP6 connectivity, to the best of my 
knowledge. I haven't even heard if they have any plans for this. Hence, I 
have never bothered to actually learn about it... A couple of years ago at 
a customers' site I fought valiantly against a BTConnect router that 
insisted the addresses it was giving to the Windows servers and clients 
must be used, whereas the actual ones were in the AD server database; there 
was no published way to disable it, I figured out something at the end and 
that was all my IPv6 experience. 
 

> 

>   something about yarn tries one address, but does not try others?


Here are two outputs of the same command - ' env DEBUG=\* npm -d -d ping', 
the first was issued when ip6addrctl returned 'no source-address-selection 
policy is installed': 
---

npm info using npm@9.2.0
npm info using node@v19.2.0
npm notice PING https://registry.npmjs.org/
2022-12-21T20:19:53.280Z agentkeepalive 
sock[0#registry.npmjs.org:443::::::::true:::::::::::::] create, timeout 
300001ms
2022-12-21T20:19:53.303Z agentkeepalive 
sock[0#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) error: Error: connect EHOSTUNREACH 2606:4700::6810:1323:443 - 
Local (:::65507)
    at internalConnect (node:net:1036:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:466:18)
    at emitLookup (node:net:1192:9)
    at GetAddrInfoReqWrap.callback 
(/usr/pkg/lib/node_modules/npm/node_modules/make-fetch-happen/lib/dns.js:46:14)
    
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:8) {
  errno: -65,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '2606:4700::6810:1323',
  port: 443
}, listenerCount: 2
2022-12-21T20:19:53.307Z agentkeepalive 
sock[0#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) close, isError: true
2022-12-21T20:20:03.318Z agentkeepalive 
sock[1#registry.npmjs.org:443::::::::true:::::::::::::] create, timeout 
300001ms
2022-12-21T20:20:03.319Z agentkeepalive 
sock[1#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) error: Error: connect EHOSTUNREACH 2606:4700::6810:1323:443 - 
Local (:::65506)
    at internalConnect (node:net:1036:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:466:18)
    at emitLookup (node:net:1192:9)
    at process.processTicksAndRejections 
(node:internal/process/task_queues:83:21) {
  errno: -65,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '2606:4700::6810:1323',
  port: 443
}, listenerCount: 2
2022-12-21T20:20:03.320Z agentkeepalive 
sock[1#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) close, isError: true
2022-12-21T20:21:03.325Z agentkeepalive 
sock[2#registry.npmjs.org:443::::::::true:::::::::::::] create, timeout 
300001ms
2022-12-21T20:21:03.326Z agentkeepalive 
sock[2#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) error: Error: connect EHOSTUNREACH 2606:4700::6810:1323:443 - 
Local (:::65505)
    at internalConnect (node:net:1036:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:466:18)
    at emitLookup (node:net:1192:9)
    at process.processTicksAndRejections 
(node:internal/process/task_queues:83:21) {
  errno: -65,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '2606:4700::6810:1323',
  port: 443
}, listenerCount: 2
2022-12-21T20:21:03.332Z agentkeepalive 
sock[2#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 0) close, isError: true
npm http fetch GET 200 https://registry.npmjs.org/-/ping?write=true 70087ms 
(cache stale)
npm notice PONG 70089ms
npm info ok 

----

 the second - when one was installed by 'ip6addrctl install ...'    (or if 
I have NODE_OPTIONS=--dns-result-order=ipv4first  in the environment) :


npm info using npm@9.2.0
npm info using node@v19.2.0
npm notice PING https://registry.npmjs.org/
2022-12-21T20:22:09.324Z agentkeepalive 
sock[0#registry.npmjs.org:443::::::::true:::::::::::::] create, timeout 
300001ms
2022-12-21T20:22:09.627Z agentkeepalive 
sock[0#registry.npmjs.org:443::::::::true:::::::::::::](requests: 1, 
finished: 1) free
npm http fetch GET 200 https://registry.npmjs.org/-/ping?write=true 339ms 
(cache updated)
npm notice PONG 341ms
npm info ok 




> 

> 

> Or is it that you have public and private v6, and something is picking

> the private v6?

The hosts in the network have their ip6 link-local addresses, they don't 
appear able to ping each other, they have no public ip6 addresses.
 

> 

> It seems that things should work without explicit configuration.

> 

This is what it used to be, as I mentioned above. 

--
----
Chavdar Ivanov