From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 14 Jan 2014 07:10:18 -0700 From: Grant Mather To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20140114141018.GA71647@Grants-MacBook.local> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Subject: Re: [9fans] Venti on OpenBSD: vtversion: bad format ... Topicbox-Message-UUID: b2e0e41a-ead8-11e9-9d60-3106f5b1d025 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 > > (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