All of lore.kernel.org
 help / color / mirror / Atom feed
* Fwd: WebRTC protocols broken when forwarding after a change to ip_dst_mtu_maybe_forward()
       [not found] <CAGvuCg_iLtzHr_rF0291oKAtYFCespoJ=dszFWjDftZd8EN6JA@mail.gmail.com>
@ 2021-06-20 22:58 ` Juan Manuel Santos
  0 siblings, 0 replies; only message in thread
From: Juan Manuel Santos @ 2021-06-20 22:58 UTC (permalink / raw)
  To: davem, yoshfuji, dsahern; +Cc: netdev

Hello,

Apologies if somebody receives this email twice. My first email was
filtered by the mailing list because gmail defaults to HTML. me--

I am writing to this mailing list because I believe based on the
maintainer list[1] that this is the correct place to report issues
like these, especially when unsure. I am a Gentoo user and I already
reported this downstream[2] but in my troubleshooting I was able to
confirm that linux-stable is affected, and possibly others.

The issue happens whenever a kernel version with a certain patch is
used in a gateway device doing IP forwarding for a LAN, such as a
Linux box running iptables / firewalld+iptables / firewalld+nftables.
It does not seem to matter which of the three methods is used, all are
affected. Applications inside the LAN using WebRTC (such as Google
Meet, Discord, etc) are affected. In the case of Meet, no video of any
participant can be seen, although audio works. In the case of Discord,
neither audio nor video works. It does not matter whether the
conference is started or joined from a device within the LAN, it won't
work properly.

I was able to git-bisect this using linux-stable and found the
offending upstream commit[3]. In linux-stable this was backported
right after 5.4.72 so >=5.4.73 are affected, up to 5.4.126. I can
confirm that reverting the commit (even if it is just commenting those
4 lines that the commit adds) fixes the issue at least on 5.4.109. No
other protocol/connection type seems to be affected, and this only
seems to affect webrtc in the context of forwarding (i.e. when
started/joined from a device in the LAN, not the gateway itself).

I am unsure how to proceed, whether this requires an upstream bugzilla
to be opened (which I can gladly do) or not. I searched the archives
first but I could find no mention relating webrtc and the change to
this function (I only found the relationship when git-bisecting).

Thanks in advance.

Regards,



[1] https://www.kernel.org/doc/html/latest/process/maintainers.html#maintainers
[2] https://bugs.gentoo.org/797211
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=02a1b175b0e92d9e0fa5df3957ade8d733ceb6a0

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-06-20 22:58 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAGvuCg_iLtzHr_rF0291oKAtYFCespoJ=dszFWjDftZd8EN6JA@mail.gmail.com>
2021-06-20 22:58 ` Fwd: WebRTC protocols broken when forwarding after a change to ip_dst_mtu_maybe_forward() Juan Manuel Santos

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.