HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 2201
Connection: close
<!DOCTYPE html><html><head><meta http-equiv="Cache-control" content="no-transform">...
...followed by the rest of the page.
In the failure mode, I get this only:
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 2201
Connection: close
In both cases, the header info above is in the first TCP packet. When it's working the remainder of the page is broken up over 2 more packets. In the failure mode, data ends after the header packet. If I am reading the wireshark data correctly it seems like multiple packets are expected but no more are sent.
I should note that I have captured packets from behind the firewall and I am watching all data coming to/from the ESPWebserver. So why would it stop sending? Is it missing an ACK? Or is this related to MTU size and packet fragmentation? I feel like it's in the networking layers. All my devices are set to MTU=1500.
I know this sounds improbable but I sat down 4 times to solve it and still can't come up with a solution. I just moved my home Internet from Comcast to FIOS so I was waiting until that change was complete in case there was any effect. Still have the same problem. This is the layout:
ESP<---->unifi WAP<------>wired to sonicwall<----------->FIOS
I have some packet traces in .pcap form. Anything I am missing?