this post was submitted on 18 Jul 2024
12 points (100.0% liked)
homelab
6589 readers
8 users here now
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
start with basics:
iperf
on every device you can between an external device and your internal host(s) and use it to find any bottleneckstcpdump
to analyze packets flowing over the network. you can often find surprising results this wayiperf
) with the most simple config (no nginx etc) and add the complexity of your config bit by bit until the issue returnsThanks. I also forgot to mention that I have a Home Assistant instance running on a different machine that isn't reliant on NPM, and it works fine, and has the same issue when I try to migrate it to NPM, so I'm sure the issue is there. I'll try your suggestions.
Regarding tcpdump, you can use it directly from the command line to print out packets, or you can have it record traffic to a file. That file can later be opened in Wireshark for analysis, with filters, color, ~~blackjack and hookers~~, and protocol decoding.
Things like TCP retries or MTU issues/fragmentation will be very apparent when presented in Wireshark.