Well done to johnson for successfully modifying the FW with respect to baby jumbo frames capability and to meritez for having the courage to test despite the possibility of a "bad flash" and the associated recovery issues.
Have not loaded the modified FW on my spare 1312-B10D as it's based on the V.5.13(AAXA.8) revision with modified GUI which I don't like and I don't currently intend to put the router on line, however, the ping test method as supplied by meritez prompted further research ref. usage in a Windows environment, found this information:
https://interworks.com/blog/tlester/2010/12/29/test-jumbo-frames-how-tell-if-9000-mtu-working/This command line worked on my 1312-B10A which is not baby jumbo frames FW modified:
C:\WINDOWS\system32>ping -f -l 1472 198.41.215.162(the second command line option is lower case "-L", upper case "-L" won't work)
For reference, ping on 1312-B10A with
1464 bytes requested:
C:\WINDOWS\system32>ping -f -l 1464 198.41.215.162
Pinging 198.41.215.162 with 1464 bytes of data:
Reply from 198.41.215.162: bytes=1464 time=30ms TTL=58
Reply from 198.41.215.162: bytes=1464 time=30ms TTL=58
Reply from 198.41.215.162: bytes=1464 time=29ms TTL=58
Reply from 198.41.215.162: bytes=1464 time=29ms TTL=58
Ping statistics for 198.41.215.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms
For comparison, ping on 1312-B10A with
1465 bytes requested:
C:\WINDOWS\system32>ping -f -l 1465 198.41.215.162
Pinging 198.41.215.162 with 1465 bytes of data:
Request timed out.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 198.41.215.162:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Probably very much stating the obvious here to the better informed forum members, however, I was not aware of the packet frame size ping testing method so hopefully this will act as a guide to lesser informed parties (such as myself) who may wish to implement / test the FW modification on their 1312-B10D's and are running in a Windows environment.