From: Samuel Thibault <samuel.thibault@gnu.org>
To: Ottavio Caruso <ottavio2006-usenet2012@yahoo.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Is traceroute supposed to work in user mode networking (slirp) ?
Date: Sun, 19 Jul 2020 13:16:02 +0200 [thread overview]
Message-ID: <20200719111602.2xeu4ise6zlbvf4c@function> (raw)
In-Reply-To: <CAEJNuHyYR1Vj4VaDVPLUG1dkSdzHjzbiCqq=Q+2j1tjy7kYBCw@mail.gmail.com>
Ottavio Caruso, le dim. 19 juil. 2020 12:07:21 +0100, a ecrit:
> On Sun, 19 Jul 2020 at 03:50, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> > Ottavio Caruso, le mar. 14 juil. 2020 12:15:48 +0100, a ecrit:
> > > I cannot get traceroute to work with standard udp from any of my
> > > guests.
> > >
> > > $ traceroute 8.8.8.8
> > > traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 40 byte packets
> > > 1 * * *
> >
> > That was because
> >
> > - libslirp was not forwarding the ttl value, thus always set to 64 hops
> > - libslirp was not reporting icmp errors.
> >
> > I had a try at both, and that indeed seems to be fixing the issue:
> > https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/48
> > https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/49
> >
> > > Any clues? Is this intended behaviour? Any workarounds that don't
> > > involve tap/tun/bridges?
> >
> > Not without updating libslirp with the abovementioned patches.
>
> Thanks Samuel. I've added a comment on the portal, but for the benefit
> of qemu-devel:
>
> Applying this patch on the latest qemu (5.0.90),
Did you also apply
https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/48 ?
Samuel
next prev parent reply other threads:[~2020-07-19 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEJNuHy+CqveTjiCxpjiLX-D=NczSveUSDSAZyz=D5F0XvL5QQ@mail.gmail.com>
2020-07-14 11:15 ` Is traceroute supposed to work in user mode networking (slirp) ? Ottavio Caruso
2020-07-19 2:50 ` Samuel Thibault
2020-07-19 11:07 ` Ottavio Caruso
2020-07-19 11:16 ` Samuel Thibault [this message]
2020-07-19 14:15 ` Ottavio Caruso
2020-07-19 14:58 ` Ottavio Caruso
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=20200719111602.2xeu4ise6zlbvf4c@function \
--to=samuel.thibault@gnu.org \
--cc=ottavio2006-usenet2012@yahoo.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 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).