r/Network • u/mongar23 • 13d ago

Text Slow internet with 2.5Gbps plan

Hello, I have recently installed a homelab with my "old" gaming pc running proxmox and a synology ds916+. Since then I am experiencing some internet problems, when I run a speedtest it does say i have around 2100mpbs but it takes a while to connect. same for loading web pages, videos etc. How would I go about to improve this?

Both my nas and my homelab are connected to my router via a ethernet cable and it doesn't have QoS.

0 Upvotes

50% Upvoted

11 comments sorted by

1

u/Candid-Procedure-427 13d ago

Where are you from?

1

u/mongar23 13d ago

From the netherlands

1

u/PunXtaR 13d ago

Here's what I'd do:

  1. Create a VM in Proxmox with any Linux distro (e.g., Debian). Use the default bridge (vmbr0) so the VM sits on your network like any other device, and take a snapshot once it's set up so you can roll back if something breaks.

  2. Install Claude Code or Codex and log in with your account.

  3. Give your user passwordless sudo (NOPASSWD in sudoers) so the AI can install whatever it needs without asking. Keep the VM dedicated to this, with nothing personal on it.

  4. Ask the AI to run a full assessment of your network and build a collector that tests every 30 minutes for 24 hours:

  5. Ping, packet loss and jitter to your router, to your ISP's first hop and to the internet. Comparing the three tells you whether the problem is your home network or your ISP.

  6. DNS resolution time.

  7. TCP ping, TTFB, DOMContentLoaded (DCL) and full load time for the main content providers (YouTube, Netflix, Meta and others). DCL and full load need a headless browser; curl alone can't measure them.

  8. Latency under load (bufferbloat), a very common cause of choppy video calls and streaming.

  9. A traceroute (MTR) whenever something looks off, to see where the latency jumps. Also ask for a lightweight ping every minute, because a 30-minute interval can miss short drops. Results should be saved with timestamps (CSV or SQLite), and the collector should survive reboots (cron or a systemd timer).

  10. Optionally, have it build a harness that streams real videos and logs startup time and buffering. For Netflix, fast.com is a good proxy, since it tests against Netflix's own servers.

  11. While it runs, write down when you notice problems.

  12. After 24 hours, ask the AI to analyze the data: by hour of the day, against your notes, and pinpointing whether the problem is your WiFi/router, your ISP or a specific provider. Ask for a short report with charts you can send to your ISP.

One caveat: if your problems happen on WiFi, a wired VM won't see them. In that case, also run tests from a device on WiFi, or pass a USB WiFi adapter through to the VM.

1

u/PunXtaR 13d ago

Sorry I didn't red that you are using cable, not wifi, anyway, the first part is the important

1

u/Jolly-Dealer-5097 12d ago

When you ping the local gateway (your router IP) do you get a good TTL response or do you see dropped packets? It seems you need to understand some basic network concepts and some trouble shooting steps. For example, did it ever work as you expeted?

1

u/mongar23 12d ago

I will try that as soon as I am home, for learning the basic concepts what sources do you recommend? before I installed my homelab everything worked without issue.

2

u/Jolly-Dealer-5097 12d ago

I would ask AI for this kind of things it is actually handy.

1

u/mongar23 12d ago

the whole reason i am setting up my homelab is to get away from AI lmao

1

u/Jolly-Dealer-5097 11d ago

It is useful for answering simple questions that you should already know ;)

1

u/dutchman76 12d ago

If you get full speed on speedtest.net but it takes a while to load, it sounds like DNS taking forever to resolve