Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    MTU Packets broken over 8968

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    7 Posts 2 Posters 849 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      LordSandwurm
      last edited by

      i have a wired mtu problem.
      If i ping form my linux server (MTU 9000) to the Pfsense with "ping -s 8968" it worked. With
      8969-8972 it didnt work. The package didnt get to the Pfsense.

      In the other way I ping to the server with 8969 the server get the package send an ansewer, but the pfsense didnt get the answer package.

      Captured with tcpdump and pfsense packagecapture.

      Can anybody help ?

      1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott
        last edited by

        With ping, you have the payload and the headers. The headers take 32 bytes with IPv4, so the payload cannot be any more than 9000-32 or 8968.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 1
        • L
          LordSandwurm
          last edited by

          @JKnott Sorry thats wrong. The payload ist 28byte not 32 . Between two linux or Windows Systems you can transfer 8972 byte (8972 + 28)

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @LordSandwurm
            last edited by

            @lordsandwurm

            Sorry, I made the mistake of counting the MAC address. Regardless the point remains the same. You lose some of the MTU space to protocols. Here's a screen capture from Wireshark. I have selected the data field and look at what's highlighted. It starts right at 32.

            1fae6da0-32d3-406b-b1af-8a2e013350ad-image.png

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            1 Reply Last reply Reply Quote 0
            • L
              LordSandwurm
              last edited by

              This did not help.
              I try to explain it better.

              Client 1 MTU 9000
              Client 2 MTU 9000
              Pfsense MTU 9000

              Client 1 <-> Client 2 Connection work perfect (max Package size 8972)

              Client 1 <-> Pfsense <-> Client 2 Some Package Broken. All over 8968

              It seams like the VLAN header is the Problem.
              I can not increas the mtu over 9000. But i can not lower the mtu on Windows.

              JKnottJ 1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott @LordSandwurm
                last edited by

                @lordsandwurm

                Did you mention VLANs before? I didn't see it. Regardless, a VLAN tag will cost another 4 bytes from the MTU. The MTU refers to the bytes after the MAC addresses and before the CRC. That includes all the upper level protocols, including VLAN tags. Fire up Wireshark and take a look at the actual frames. Click on the various fields to see where they begin and end, as I did with that data field.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • L
                  LordSandwurm
                  last edited by

                  @JKnott thx i found the solution.

                  The solution is to lower the mtu on all partitipants of the vlan. Not on the Switches or the physical network adaper of the pfsense. I lower client1 client2 an vlan interface on pfsense on MTU 8800. With that i have no broken packats.

                  I transmit 8772 Data Bytes + 28Bytes header = MTU 8800. If i send one over it it gets fragmentet.

                  The Problem is that the switch added the 4byte VLAN header. So the packag was greater then 9000 (9004). The physical network adapter on the PFsense throw the package away and it gets lost in the VLAN.

                  by the way you can set this on windows also with the folowing command:

                  netsh interface ipv4 set subinterface "interface name" mtu=8800 store=persistent

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.