Hi,
I noticed why the chardev socket backend disconnects, and I would like to
make this a RFC to see how I should fix it.
Current scenario after boot-up:
1. tcp_chr_read_poll keeps polling the slirp_socket_can_recv, and
slirp_socket_can_recv returns 0 since slirp_find_ctl_socket couldn't
Update on debugging this thing (already updated
https://gitlab.com/qemu-project/qemu/-/issues/1835):
I saw that `tcp_chr_free_connection` was called after the first response
being successfully sent:
```
slirp_guestfwd_write guestfwd_write: size 80tcp_chr_write
tcp_chr_write: s->state:2tcp_chr_writ
Hi Samuel,
Thanks for the clarification! I missed the email so didn't reply in time,
but was able to figure it out.
Hi everyone,
IPv6 guestfwd works in my local test but it has a weird bug: if you send
two requests, the first one gets the correct response, but the second one
gets stuck.
I am usin
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.
Hi all,
I am continuing debugging the ipv6 guestfwd feature, and I would like to
understand the behavior of slirp better.
Progress I've made:
Let QEMU take parameter like following:
guestfwd=tcp:[fec0::105]:54322-tcp:[::1]:6655
For slirp side, I basically searched for the appearance of gfwd_list
Hello,
Felix Wu wrote:
> 2. I want to understand what ip I should use. Currently I have following
> formats for the QEMU invocation in ipv6:
> ```
> guestfwd=tcp:[::1]:1234-tcp:[my:host:ip:from:ifconfig]:22
> ```
> I know the general form is `guestfwd=tcp:server:port-dev`, where
> server:port is
CC'ing SLIRP and net maintainer.
On Sun, 25 Jun 2023 22:58:36 -0700
Felix Wu wrote:
> Hi all,
>
> TL,DR: I am working on QEMU ipv6 guestfwd feature and finished coding, and
> would like to learn the best practice to test it.
> Context: in slirp side this task is tracking by [1].
> Currently, I
Hi all,
TL,DR: I am working on QEMU ipv6 guestfwd feature and finished coding, and
would like to learn the best practice to test it.
Context: in slirp side this task is tracking by [1].
Currently, I have done following:
i. made char parse + guestfwd functions happy with ipv6 address.
ii. enabled d
