9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Grant Mather <hcaulfield57@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Venti on OpenBSD: vtversion: bad format ...
Date: Tue, 14 Jan 2014 07:10:18 -0700	[thread overview]
Message-ID: <20140114141018.GA71647@Grants-MacBook.local> (raw)
In-Reply-To: <CAPkKT5FY-dDiufwRw9Rf6_amyebC92c_AM3h1WTjWhdAxTcEzA@mail.gmail.com>

On Tue, Jan 14, 2014 at 03:46:11AM -0800, Michael Hansen wrote:
> Are you using OpenBSD's stock pf ruleset? I don't think it blocks or
> otherwise interferes with any 9Pish ports by default, but it's
> something to check.
> mmh
>
> > Date: Mon, 13 Jan 2014 16:59:13 -0700
> > From: Grant Mather <hcaulfield57@gmail.com>
> > (snip)
> > Using plan9port-20120508 that is provided with OpenBSD seems to have
> > venti working properly on the system, but it does not work across the
> > network, when trying to connect with vac/unvac to the server with a
> > different OS, I invariably get "vtversion: bad format in version
> > string".
> >
> > Using the most up to date plan9port-20140107, I get the same vtversion
> > string when connecting from other OSes, and venti doesn't seem to even
> > work on the server, I in turn get "vac: could not connect to server:
> > Connection refused".
> > (/snip)

Yes, I'm using the stock pf ruleset. As far as I can tell it's not a
port issue or anything like that. It appears to be listening on the
standard venti port 17034 according to netstat, and venti gets started
properly out of inetd. venti/venti -d doesn't reveal anything
interesting either.

grm



      reply	other threads:[~2014-01-14 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 11:46 Michael Hansen
2014-01-14 14:10 ` Grant Mather [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=20140114141018.GA71647@Grants-MacBook.local \
    --to=hcaulfield57@gmail.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).