Unable to upload files larger than approx 1.2MB

bdelia

@bdelia I just enabled logging of events via M929 P"eventlog.txt" S1, but the resultant log on shows the following after trying to upload a file that failed and caused the network error.

2025-03-08 09:41:49 [info] Event logging started at level warn
2025-03-08 09:41:49 [info] Running: Duet Ethernet 1.02 or later: 3.5.4 (2024-11-24 10:43:42)

bdelia

@bdelia I am at my wits end and am thinking I may need to replace the board...but everything seems to work with the exception of uploading files bigger than about 1.4MB. The uploads consistently fail, it is not intermittent.

Phaedrux

Did this start happening after updating a firmware or any other change?
Have you tried uploading from a different computer?

bdelia

@Phaedrux I just tried uploading from another computer and it worked. I have cleared the cache on the original computer's browser (Chrome), but that did not seem to help. I'll try again and another browser.

dc42

@bdelia if this issue continues then it may be helpful if you install Wireshark on your PC and get a trace of a failed attempt to upload a larger file.

bdelia

@dc42 , thanks I will give that a try tonight or tomorrow.

bdelia

@dc42 , I have been learning wireshark and have done some testing. I am not sure yet how to detect errors associated with network connections, but I know how to isolate the capture between my laptop IP and Duet IP. I now see that any file under about 1.5MB never gets to the POST command. Any file under that threshold uploads fine and I see the POST command.

Any recommendations on what to look for in the capture that might indicate a network issue? I am familiar with HTTP response codes due to my day job, but I am not a network engineer.

dc42

@bdelia there should always be a POST command, that's how file uploads are done.

Usually when there are network issues we see network packets with error status. Wireshark usually highlights these in a dark colour.

You probably already know this, but to isolate the traffic to the Duet use filter ip.addr==192.169.1.150 (substitute the actual IP address of the Duet).

bdelia

@dc42 I have been able to isolate the isolate the traffic to the Duet. I can see lines of info colored Red and Black amongst the green.

I am just not able to interpret the lines for meaningful errors.

dc42

@bdelia if you save the trace as a .pcap file and attach it to a post then we can look at it.

bdelia

@dc42 Thanks. Here is my .pcap file. Wireshark reveals just how much back and forth takes place between my laptop browser and the Duet. I tried to limit the packets capture to just the act of uploading but that was hard. I believe the upload is initiated at the TimeStamp: 738 21.597390

UploadFail.pcapng