Recent content by Aaron407

That sounds like a different, device-specific issue since my problem affects all devices on the connection.

It sounds like the packet loss that I was seeing with the pingpath was typical for that node as it doesn't respond to trace routes/pings and normally drops packets in such fashion. The thinkbroadband monitor hasn't been showing anything really out of the ordinary so far either. My ISP is going...

Ok, I tried pingpath to what google shows as my phone's public IP, but it's hard to know how the private subnets are configured below that. Anyway, it never shows it actually reaching that public IP (even though it doesn't run through all 30 hops), and ends up with 100% packet loss after tries...

Wow, thanks for the wealth of feedback! Here are some follow up notes: -I have a second NIC on the computer I use as a home server, but it didn't make any difference in perceivable speeds. I'm not sure if I noted previously, but the speed issue is experienced by other devices on the network as...

Long delay, and the problem remains. My ISP has gotten back to me with a bit of info as stated below, though: "We've ran a bunch of packet captures and analysis, and approximately 40-45% of the TCP packets coming from your system are being retransmitted, this means that the higher the latency...

My ISP finally got around to testing the FTP speeds at their location within their network when downloading from my server, and the speeds were great. What this tells me is that it's not an issue with my configuration, but rather it's upstream of where they tested - either at their connection to...

That's fair. I've had to explain the difference between bits and bytes to more people than I can count, so it's good to rule out stuff like that. Thanks for sticking with me this far, I appreciate it.

I'm very familiar with the difference between bits and bytes. My b's vs. B's were intentional. Just curious, what's the line of thinking for changing the file server software? I'm not sure how that could have an impact, especially when http transfer speeds are also affected.

No double NAT. The service originally had one, but I couldn't do hairpinning properly, so I'm currently set up with a static IP and no upstream NAT. I can port forward to my heart's content, and the IP address seen by the router is a proper public IP (102.255.xxx.xxx). So, the plot thickens...

From what I've been told, there's no traditional access point on my end, and the wireless link acts effectively as a simple protocol converter for ethernet -> 2.4 GHz RF link over air -> ethernet. There's just an ethernet cable coming from the radio on our roof that runs to a PoE injector and...

I have a Windows 10 laptop that I may install an FTP server on and hardwire it on the network (maybe direct connection to the P2P radio), just to take the other computer out of the equation for testing. I need approximately three fewer children to have enough time for some of this...

Yeah. Unfortunately, it'll be some time before I can really dive into the troubleshooting as we leave for an extended camping trip soon...

I don't believe so. Both of the devices (my phone, work computer) can download with full speeds from other sources. It's just from my home server that things are choked at some point, unfortunately.

I use Filezilla server. The speed is slow for the directional remote transfers outside of FTP as well, though. If I try to download a security camera clip through http from a remote location, I get the same slow speeds, so it doesn't seem to be related to the FTP server config.

I can give it a shot. I'll try 1000 Mbps full duplex rather than auto negotiate since it is connected to a gigabit router. Edit: didn't make a measurable difference, unfortunately.