From: Samuel Thibault <samuel.thibault@gnu.org>
To: Felix Wu <flwu@google.com>
Cc: Lukas Straub <lukasstraub2@web.de>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Subject: Re: Tips for local testing guestfwd
Date: Thu, 20 Jul 2023 16:54:15 +0200 [thread overview]
Message-ID: <20230720145415.w7s3ystkrf5gc66y@begin> (raw)
In-Reply-To: <CAJt6XFpDwuim-FF7a5MMibQvJa1YJ=X165n43XEtQaF4356r9w@mail.gmail.com>
Hello,
Felix Wu, le mar. 18 juil. 2023 18:12:16 -0700, a ecrit:
> 02 == SYN so it looks good. But both tcpdump and wireshark (looking into packet
> dump provided by QEMU invocation)
Which packet dump?
> I added multiple prints inside slirp and confirmed the ipv6 version of [1] was
> reached.
> in tcp_output function [2], I got following print:
> qemu-system-aarch64: info: Slirp: AF_INET6 out dst ip =
> fdb5:481:10ce:0:8c41:aaff:fea9:f674, port = 52190
> qemu-system-aarch64: info: Slirp: AF_INET6 out src ip = fec0::105, port = 54322
> It looks like there should be something being sent back to the guest,
That's what it is.
> unless my understanding of tcp_output is wrong.
It looks so.
> To understand the datapath of guestfwd better, I have the following questions:
> 1. What's the meaning of tcp_input and tcp_output? My guess is the following
> graph, but I would like to confirm.
No, tcp_input is for packets that come from the guest, and tcp_output is
for packets that are send to the guest. So it's like that:
> tcp_input write_cb host send()
> QEMU --------> slirp -----------> QEMU --------------------> host
> <-------- <--------- <-----------------
> tcp_output slirp_socket_recv host recv()
> 2. I don't see port 6655 in the above process. How does slirp know 6655 is the
> port that needs to be visited on the host side?
Slirp itself *doesn't* know that port. The guestfwd piece just calls the
SlirpWriteCb when it has data coming from the guest. See the
documentation:
/* Set up port forwarding between a port in the guest network and a
* callback that will receive the data coming from the port */
SLIRP_EXPORT
int slirp_add_guestfwd(Slirp *slirp, SlirpWriteCb write_cb, void *opaque,
struct in_addr *guest_addr, int guest_port);
and
/* This is called by the application for a guestfwd, to provide the data to be
* sent on the forwarded port */
SLIRP_EXPORT
void slirp_socket_recv(Slirp *slirp, struct in_addr guest_addr, int guest_port,
const uint8_t *buf, int size);
Samuel
next prev parent reply other threads:[~2023-07-20 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 5:58 Tips for local testing guestfwd Felix Wu
2023-06-26 9:49 ` Lukas Straub
2023-06-26 10:08 ` Samuel Thibault
2023-07-19 1:12 ` Felix Wu
2023-07-20 14:54 ` Samuel Thibault [this message]
2023-08-17 18:58 ` Felix Wu
2023-08-23 17:27 ` Felix Wu
2023-09-06 20:53 ` Felix Wu
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=20230720145415.w7s3ystkrf5gc66y@begin \
--to=samuel.thibault@gnu.org \
--cc=flwu@google.com \
--cc=jasowang@redhat.com \
--cc=lukasstraub2@web.de \
--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 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).