After Core 153, Discord Cam no longer working

Discord video output fails on Windows 10, Ubuntu 20.04, and Android.

I can receive other people’s video output in discord calls.

IPFire works if I use Core 152 and earlier, but after 153, it continues to not work.

I only have port forwarding to my servers. I switched to OPNsense and had no issues.

I disabled Guardian, the IPS, the QOS, basically anything not running by default. I even did fresh reinstalls. Nothing resolved. My hardware is also from a vendor through the IPFire site.

https://fireinfo.ipfire.org/profile/ee857a9c0e323acca98c8d2252102bb00a11f4f7

My hardware profile.

Hi John, I have the exact same problem as you. I upgraded IPFire to core 156 and the problems are still present.
Here is my hardware profile: fireinfo.ipfire.org - Profile 5acd41bddc17da143b4a5e6f967fc7fdcae815c7
We could compare our material.

Has anyone seen progress with 157 or 158 on this issue?

157 may be worth a try.

The info below is from the Development Mailing List posted earlier today:

(c) For quite some time, I suffered from VoIP calls not being established properly, as described in VoIP connection tracking oddities - Development - lists.ipfire.org a while ago. I unfortunately never caught the root cause for this, but blamed an error somewhere in the Linux kernel. Bug #12563 sounds pretty related.

After upgrading all IPFire machines to Core Update 157, the problem disappeared (and I was happy). Surprisingly, it reappeared at least once after having upgraded one system to Core Update 158.

Since we did not ship a kernel in C158, this rules out Linux being the sole root cause for this. I am starting to blame pppd as well, as it is the only piece of software changed in C158 that smells relevant to me. On the other hand, this would have meant we suffer from this since March 2020 at least, where we successfully updated pppd the last time (blog.ipfire.org - IPFire 2.25 - Core Update 142 released).

Anyway: I will investigate, finally try to get meaningful traces of it, and report back. I do not want to lose my functioning VoIP calls. :slight_smile:

1 Like

Hi,

yes, Core Update 157 definitely improves our behaviour in terms of fragmenting UDP packets. Please install it and report back - we are still lacking feedback on a potentially related issue, so it would be good to finally get some reports on this.

Thanks, and best regards,
Peter Müller

I tried an upgrade to 157 and subsequent upgrade to 158 to no avail. I was checking the fix with use of Teams screen share, with Cisco webex screen share and FB Messenger. I did a reload of 152 and retested with above applications and that does work. Note that Teams and webex were also over corporate VPN in both cases.

I too tried upgrading beyond 152 and have had no luck. The posted hardware profiles look to be protectcli hardware. it would be interesting to know if either some kernel driver config combination is causing this issue. I am willing to spend some time digging and providing data, but I don’t know what would be most helpful.

Hi all,

meanwhile, Core Update 159 is available for testing:

Since it comes with a new major release of the Linux kernel, the underlying network code has changed significantly. May I ask everyone affected by this issue to give Core Update 159 a try (see here for further information on how to do this) and report back?

Thanks, and best regards,
Peter Müller

No luck. Point-to-point FB video call failed. Teams remote share failed… :frowning: not happy. Not sure if this helps but:
ipfire #1 SMP Mon Aug 2 22:53:53 GMT 2021 x86_64 Intel(R) Celeron(R) CPU J1900 @ 1.99GHz GenuineIntel GNU/Linux

not sure of which slot but the intels are red and green
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
orange - 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)

Yes! It does help!

I had the same board. But I had no problems with FaceTime, MS Teams or Zoom.

Linux ipfire.localdomain 4.14.232-ipfire #1 SMP Mon Jun 21 20:55:12 GMT 2021 x86_64 Intel(R) Celeron(R) CPU J1900 @ 1.99GHz GenuineIntel GNU/Linux


EDIT: added LAN

4 x RJ-45 Ports - Intel I211-AT- 10/100/1000 Controller

I tried to see if I could install the released ver of 159, but it IPFire did not show I could install it. I assumed then it was the same. Facebook messenger, Google Meet, Zoom and Teams all have issues. Signal worked! I’m going to downgrade shortly b/c my peeps want some video!

Hi all,

just for the records: This bug is finally being fixed in upcoming Core Update 165, and it would be great if some of you could test this update and confirm it really is. :slight_smile:

Thanks in advance, and best regards,
Peter Müller

2 Likes

I am running 169 and I am have the issue realted above. Discord will not connect. I am early in my searching so maybe I’ll find the solution further.

Are you using IPS?
Intrusion Prevention System.

That was it. I recently added the BLUE interface into my network and had that enable on BLUE. Previously everything was on the GREEN interface which had it disabled.

1 Like