9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com>
To: ori@eigenstate.org
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Venti on OpenBSD - some information and a question
Date: Mon, 4 May 2020 22:58:17 +0200	[thread overview]
Message-ID: <CAHqDL_-fDJ6W9F=ouH3e8f-jm1Wt44gooeiM5ZeS2tdxGof6ew@mail.gmail.com> (raw)
In-Reply-To: <4484D19719C88F2CB22F9EDC74A9DFC4@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

Thanks, I found the problem by inspection of src/lib9/_p9dialparse.c.
IPv6 is indeed the default when using an address of tcp!*!17034
 /* translate host */
if(strcmp(host, "*") == 0){
ss->ss_family = AF_INET6;
((struct sockaddr_in6*)ss)->sin6_addr = in6addr_any;
}else if((he = gethostbyname(host)) != nil && he->h_addr_list[0] != nil){

So, setting the address string to tcp!dell-openbsd!17034 fixed the problem.
My Linux machines actually have an IPv6 address, the OpenBSD box does not,
so that explains the difference.

Ole-Hj.

On Mon, May 4, 2020 at 10:09 PM <ori@eigenstate.org> wrote:

> > I can connect to the venti from localhost, but not from any other
> machine.
> > However, if I run nc -l on ports 17034 and 80, I can connect from any
> > machine. It is definitely not the packet filter, since the problem
> persists
> > even if I disable the packet filter. Any suggestions about what might be
> > blocking the connection?
>
> My first guess is that it's listening on the wrong interface.
> Run it under 'ktrace', then run 'kdump' and look for the bind()
> calls and friends.
>
>

[-- Attachment #2: Type: text/html, Size: 1561 bytes --]

      reply	other threads:[~2020-05-04 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 20:05 Ole-Hjalmar Kristensen
2020-05-04 20:09 ` [9fans] " ori
2020-05-04 20:58   ` Ole-Hjalmar Kristensen [this message]

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='CAHqDL_-fDJ6W9F=ouH3e8f-jm1Wt44gooeiM5ZeS2tdxGof6ew@mail.gmail.com' \
    --to=ole.hjalmar.kristensen@gmail.com \
    --cc=9fans@9fans.net \
    --cc=ori@eigenstate.org \
    /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).