From: Jeff Sickel <jas@corpus-callosum.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] sshnet and the go dns resolver
Date: Tue, 23 Feb 2021 17:23:08 -0600 [thread overview]
Message-ID: <2B6B7294-863E-40DE-96A6-BDE503887FD6@corpus-callosum.com> (raw)
In-Reply-To: <F61B1682-DF92-4EFE-BFF9-49D8A3D54D87@quintile.net>
I’ve noticed similar problems with go programs and resolving a lookup.
There are go programs that explicitly look for “/etc/resolv.conf” to
grab the nameserver to use, though it would be nice if the developer
were using the default net package for lookups.
> On Feb 23, 2021, at 3:34 PM, Steve Simon <steve@quintile.net> wrote:
>
> hi,
>
> the senerio - i have a plan9 terminal, a mac laptop. the laptop connects to a vpn.
>
> i write in go, and thus far i use sshfs to mount the mac’s filesystem and edit my code. i build and run the code on the mac.
>
> i thought i could use git9 via sshnet to work natively on plan9
>
> most of this is fine but when go tries to access mod files for packages on the vpn i get a “no sutiable address found” error for proxy.golang.org.
>
> i can resce the address i need (over the vpn) using ndb/dnsquery however.
>
> if i try and build without my sshnet vpn connection then i get a different error which refers to a repository on the vpn.
>
> so. i think the native resolver in the go libraries (and thus in the go executable) do not play nicely with sshnet.
>
> my guess (only a guess) is go is trying to do its own name resolution using udp port 53 and sshnet does not support udp.
>
> anyone any ideas?
> can i convince go to use plan9’s own name resolution?
> can ssh (and thus sshnet) forward udp or is that not possible?
>
> thanks for any ideas
>
> -Steve
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T774469ff9f943e45-Mab4a9e43134cbeda9523e532
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-02-23 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 21:34 Steve Simon
2021-02-23 22:23 ` Fazlul Shahriar
2021-02-23 23:23 ` Jeff Sickel [this message]
2021-02-24 1:05 ` Steve Simon
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=2B6B7294-863E-40DE-96A6-BDE503887FD6@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).