From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ftpfs shows empty /n/ftp after login
Date: Thu, 25 Jun 2015 11:28:12 -0700 [thread overview]
Message-ID: <20150625182812.9A0E9B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 25 Jun 2015 19:25:36 +0200." <20150625172536.GA1214@ananda.local>
On Thu, 25 Jun 2015 19:25:36 +0200 "Nils M Holm" <nmh@t3x.org> wrote:
>
> Came back to Plan 9 recently, and I'm running into some trouble.
> I'm running Plan 9 on QEMU and wanted to use ftpfs to exchange
> data with my FreeBSD system.
>
> When logging in via ftpfs, though, I get an empty /n/ftp directory.
My guess: you are using qemu's networking and can only make
outgoing connections but not accept incoming connections and
The default ftp protocol is to have the server connect back to
you. To go past firewalls and NAT gateways these days you use
ftp passive mode (i.e. force the client to make a connection to
a separate server port). My guess is ftpfs requires active
mode connection (but should be easy to change).
Otherwise use qemu in bridged networking mode so that a guest
os can accept any connection. I can't recall the details at
the moment but you have to use FreeBSD bridge device and add
tap ports to it.
In any case, here are some debugging ideas: Try tcpdump on
freebsd or the qemu host? Are you ftping to the qemu host
machine or another? Does 9fs sources works? There is also
ratrace (sort of like strace) - pick up my modifications from
sources/contrib/bakul/cmd as it separates trace output from
normal output.
ratrace -o tracefile ftpfs ...
next prev parent reply other threads:[~2015-06-25 18:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 17:25 Nils M Holm
2015-06-25 18:09 ` Ryan Gonzalez
2015-06-25 19:57 ` Nils M Holm
2015-06-25 22:01 ` Ryan Gonzalez
2015-06-25 18:28 ` Bakul Shah [this message]
2015-06-25 19:51 ` Nils M Holm
2015-06-25 20:16 ` Bakul Shah
2015-06-25 20:29 ` Nils M Holm
2015-06-26 8:22 ` Nils M Holm
2015-06-26 8:24 ` Mark van Atten
2015-06-26 9:32 ` Nils M Holm
2015-06-26 10:00 ` David du Colombier
2015-06-27 9:11 ` Nils M Holm
2015-06-27 9:54 ` David du Colombier
2015-06-27 20:24 ` Nils M Holm
2015-06-29 18:04 ` Nils M Holm
2015-06-26 8:29 ` Nils M Holm
2015-06-26 8:52 ` Bakul Shah
2015-06-26 9:44 ` Nils M Holm
2015-06-26 13:57 ` fgergo
2015-06-25 19:00 ` Steve Simon
2015-06-26 9:41 ` Nils M Holm
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=20150625182812.9A0E9B827@mail.bitblocks.com \
--to=bakul@bitblocks.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).