Skip to content

Bug: 'Enable LAN discovery' option causes my router to shut down #652

@stevembuko

Description

@stevembuko

Contact Details (e.g. Tox ID or email)

tox:2087A4C0F8534FF48EFBF720334C6EA74EA665A66B082E94A426F8366B788540B5B1F86D86B8
email:stevembuko@gmail.com

qTox Version

v1.18.3

Commit Hash

b7802b4

Toxcore Version

0.2.20

Qt Version

6.8.2

Steps to reproduce

  1. Have QTox running with all settings default (importantly LAN discovery enabled)
  2. My router is a NETGEAR C7000v2 running firmware version V1.03.08. I think it's settings are mostly default, but I'm not the first or only person to use the router so I'm not sure.

Observed Behavior

When connected via Ethernet, my router would shut down within 10 seconds of being turned on, preventing everyone in the house from using it. This was very disruptive and took days to figure out, since my computer is usually always connected to Ethernet.

When connected via Wi-Fi, my router would no longer shut down, but would generate the log [DoS attack: IP packet w/MC or BC SRC addr] from (my computer's LAN IP), port 33445 twice in one second approximately every 10 seconds. QTox is the only thing on my computer using that port.

I scrolled through QTox's settings to see if anything would fix it, and after disabling the 'Enable LAN discovery' checkbox and making no other changes, the issue went away. No more concerning logs were generated by the router and I was able to switch back to Ethernet from WiFi without issue. I tested it by re-enabling the checkbox, and the issue came back.

Expected Behavior

Ideally, LAN discovery would work without disrupting my router. But I'm not the only person who uses that router and I'm not sure what other strange settings might be on it, so I wouldn't be surprised if the issue lied with the router and wasn't something that could be fixed on QTox's end.

If there isn't a fix on QTox's end, though, it'd be nice if LAN discovery was off instead of on by default so that, if it does cause problems like this that wholly prevented my whole household from using my router for multiple days, I would be able to recognize the cause/effect upon enabling it, instead of having no idea what was wrong.

Reproducibility

Always

Operating System

Linux

Operating System version/distro/name/etc.

Ubuntu (QTox from Flatpak)

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugBug fix for the user, not a fix to a build script

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions