On 3/12/23 00:43, Roger Heflin wrote:
My experience with the MTU being wrong is that often nothing works to inform the sending end that the MTU is wrong. The MTU being wrong (and below 1500) is not an expected/handled condition for the TCP stack. meaning it will break for anything that uses a MTU above the size, especially if the wrong MTU is a few byte(or more) than any advertised MTU in the path. So what does your network diagram look like?
A rather simple setup. server \ \ \ eth1 192.168.2.7 --- 192.168.2.5 - modem --- 4G eth0 192.168.3.7 --- switch -- home network modem is TP-Link VX420-G2h supplied by the ISP. My main clue is that everything worked for a year with this modem, then unexpectedly, overnight, the problem appeared and still persist. [trimmed] -- Eyal at Home (fedora@xxxxxxxxxxxxxx) -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
