From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22886 invoked from network); 3 Oct 2023 22:44:19 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 3 Oct 2023 22:44:19 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Tue Oct 3 18:42:11 -0400 2023 Received: from abbatoir (pool-108-6-24-2.nycmny.fios.verizon.net [108.6.24.2]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 281b6b08 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Tue, 3 Oct 2023 15:42:08 -0700 (PDT) Message-ID: <0BCEE42528CE6C80EFFD5B6D3B7CEC47@eigenstate.org> To: 9front@9front.org Date: Tue, 03 Oct 2023 18:42:07 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: secure distributed injection deep-learning database Subject: Re: [9front] DNS/ICMP via sshnet(4) or drawterm Reply-To: 9front@9front.org Precedence: bulk if the goal is dns, it may be better to simply make us fall back to dns-over-tcp. Quoth Romano : > Hi y'all, > > I'm interested in getting DNS/ICMP working over sshnet(4) or > drawterm and want to get feedback to make sure it's not a fool's > errand. A simple 'No.' would suffice. > > First, I saw that drawterm provides /mnt/term/net/udp/, and so > attempted to do the following within drawterm as a proof-of-concept, > to see if I could use drawterm instead of sshnet: > bind /mnt/term/net /net echo -n INTERNAL_DNS_SERVER > > /env/DNSSERVER ndb/dnsgetip INTERNAL_HOST_NAME > but get: > ndb/dnsgetip: INTERNAL_HOST_NAME: dns failure: server failure > I thought that kern/devip-posix.c would have properly passed on udp > packets. So my first question is: has anyone has done something like > this using drawterm, and if so, how? > > (If my understanding is correct, drawterm would be sending everything > over 9p, which adds another layer than just using sshnet(4), but might > not make a difference immediately if I'm just trying for DNS) > > Re: sshnet(4), it'd be more complicated because the different > solutions I've seen on linux hosts use socat and nc to start listening > on a specific port on the remote host, then set up a pipe between the > tcp-over-ssh port to whatever udp host and port on the remote host's > side. So by necessity, sshnet(4) would have to do something similar. > My initial thought is to use ssh(1) to execute port listening on > remote host that would then send to a specific udp port/host. So > maybe something like: > > 1. Add a flag to sshnet(4) called -u, which specifies a script to > call using ssh(1) on the same remote host to setup tcp-over-udp port > forwarding. > > 2. The script would be mere commands to run on the remote host, so > could be targeted based on the remote host. > > 3. The command on the remote host would be executed to implement the > UDP messages described in ip(3) (i.e., the script would handle the > ctl, data, err, etc. messaging). > > For the script, a stock one might be provided at some point for common > remote host OSes/setups. Does something like that look practically > feasible? >