9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 via QEMU
Date: Fri, 21 Aug 2009 18:28:12 -0400	[thread overview]
Message-ID: <fe41879c0908211528m4a7b581cra84f85e20f90177f@mail.gmail.com> (raw)
In-Reply-To: <fe41879c0908210857v771c72c8v3e5bb10d75b06b0e@mail.gmail.com>

This time with just
flag authdebug
and without going through secstore, since
it gave me the problem highlighted above,
plain auth from the QEMU host gives the
following at Ken FS:

il: allocating ...
user akumar = 2 authenticated
authorize: uid is 2
authorize: uid is 2
hangup! connection timed out-3 ...

so at least basic auth is being done --
but what's the bizarre problem when doing
secstore (notice it hangs around for a long
time before giving that error message in
the previous post)? And of course, why the
time out from the Ken FS server?

I've attached a conversation from start to
finish between Ken FS (192.168.1.3) and
the Plan 9 inside QEMU (192.168.1.20).
tcpdump command was:

tcpdump -w kenfs-full.pcap-X -s 0 -n -e \
-ttt -i ath0 src 192.168.1.3 or dst 192.168.1.3

to produce the pcap output, and

tcpdump -X -nnr kenfs-full.pcap > kenfs-full.convo

to produce the attached file with human-readble
data.

Please let me know if more information is desired.


Thanks,
ak



  reply	other threads:[~2009-08-21 22:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 13:50 Akshat Kumar
2009-08-21 14:32 ` matt
2009-08-21 15:11   ` Akshat Kumar
2009-08-21 15:19     ` Akshat Kumar
2009-08-21 15:25       ` erik quanstrom
2009-08-21 15:57         ` Akshat Kumar
2009-08-21 22:28           ` Akshat Kumar [this message]
2009-08-21 22:29             ` Akshat Kumar
2009-08-22  1:04               ` erik quanstrom
2009-08-22  1:34                 ` Akshat Kumar
2009-08-22  2:37                   ` erik quanstrom
2009-08-22  6:35                   ` Bakul Shah
2009-08-21 15:23     ` erik quanstrom

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=fe41879c0908211528m4a7b581cra84f85e20f90177f@mail.gmail.com \
    --to=akumar@mail.nanosouffle.net \
    --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).