From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] drawterm authentication failure
Date: Mon, 22 Oct 2007 15:33:57 -0600 [thread overview]
Message-ID: <14ec7b180710221433u4351c697uf60080b3f66acb94@mail.gmail.com> (raw)
In-Reply-To: <20071022212644.GA888@shodan.homeunix.net>
looks like your drawterm can't connect to the authentication server's
port. are you specifying '-a' on the command line? do you have
anything filtering port 567? are you behind a nat and have to forward
it?
On 10/22/07, Martin Neubauer <m.ne@gmx.net> wrote:
> I've set up a new auth/cpu/fossil server via maht's make_cpuauth warlock.
> Things went smoothly for the most part, but if I try to connect to it
> drawterm does nothing for quite some time and finally prints:
>
> cpu: can't authenticate: plan9host: auth_proxy rpc: p9any client get tickets: p9sk1: gettickets: Operation timed out
>
> I don't quite have a clue what's going on (or, rather, not going on), but as
> I can boot terminals off the system and cpu in from other plan 9 hosts it
> seems that drawterm expects some network service cpu doesn't. Also, I dont
> think my drawterm is broken. I can connect to mordor just fine, for example.
>
> Baffled,
> Martin
>
>
next prev parent reply other threads:[~2007-10-22 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 21:26 Martin Neubauer
2007-10-22 21:33 ` andrey mirtchovski [this message]
2007-10-22 22:12 ` Martin Neubauer
2007-10-22 22:22 ` erik quanstrom
2007-10-23 8:35 ` Martin Neubauer
2007-10-23 11:16 ` erik quanstrom
2007-10-23 19:34 ` Lyndon Nerenberg
2007-10-23 19:38 ` andrey mirtchovski
2007-10-23 9:28 ` sqweek
2007-10-23 13:20 ` Martin Neubauer
2007-10-23 13:40 ` erik quanstrom
2007-10-23 15:16 ` Martin Neubauer
2007-10-23 15:23 ` erik quanstrom
2007-10-23 20:06 ` Tim Wiess
2007-10-23 20:24 ` Martin Neubauer
2007-10-23 20:33 ` Tim Wiess
2007-10-24 9:55 ` johnny
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=14ec7b180710221433u4351c697uf60080b3f66acb94@mail.gmail.com \
--to=mirtchovski@gmail.com \
--cc=9fans@cse.psu.edu \
/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).