All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] interesting tftp experiments
Date: Mon, 27 Jun 2005 16:25:29 +0200	[thread overview]
Message-ID: <46d6db6605062707256a4e600f@mail.gmail.com> (raw)

Hi,

since I was able on a windows host to connect (but no transfer)
on a ftp server over slirp, I thought I could do the same:
over slirp, connect to a true tftp server, not the layer provided
in slirp/tftp.c

In order to do so, I had to do minor patches to v0.7.0
- remove reference to tftp in vl.c
- remove reference to tftp in slirp/udp.c
- remove tftp.o linkage

By doing so, I have a ~true~ tftp-over-slirp qemu. I tried it
and yes I can READ & WRITE to a small tftp server I
found for windows host (http://tftpd32.jounin.net).

I still have some problems though. When the read or
write command is sent, it apparently somehow jams
the slirp channel. The read or write happens, but
not immediately (around 2 sec delay). 

The bad news is that so far, I've manage per session
of qemu either one write, or one read. If someone
has the knowledge of what could be wrong in this
part of slirp, please correct the flaws of what I just
found out.

At least, we should be able to transfer back and
forth files lesser than 32M.

-- 
Christian

             reply	other threads:[~2005-06-27 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 14:25 Christian MICHON [this message]
2005-06-29 23:45 ` [Qemu-devel] interesting tftp experiments Henrik Nordstrom
  -- strict thread matches above, loose matches on Subject: below --
2005-06-28 10:46 CoMiKe
2005-06-28 11:40 ` Christian MICHON
2005-06-29 23:43 ` Henrik Nordstrom

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=46d6db6605062707256a4e600f@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.