• 0 Posts
  • 35 Comments
Joined 10 months ago
cake
Cake day: September 8th, 2023

help-circle




  • stown@lemmy.worldtoSelfhosted@lemmy.worldMeasuring latency
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    40 Mbps is the amount of data that can be moved in one second; the difference between 20% saturation and 90% saturation should have negligible impact on latency. The bottleneck would occur if you OVERsaturate the line (ie. trying to pull more than 40mbps down) because then the packets would need to take turns coming in and possibly even be re-sent from the source if the latency is so bad that those packets are wiped from cache on routers or switches. (FUN FACT: this is basically how a DDOS attack works, too many packets are being thrown at your network and your router can’t say “no” fast enough to the bad data so latency approaches infinity and the good data ends up getting buried as well)


  • stown@lemmy.worldtoSelfhosted@lemmy.worldMeasuring latency
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    Mbps is a measurement for bandwidth not latency. However, it’s a little confusing what OP wants based on the image alone. The question marks in tandem with the bandwidth values makes me assume OP wants to know their outbound bandwidth but they are clearly asking for latency in the post text.













  • I already do use firewall rules, this is just an extra step I take to segment things which also serves to make it a bit easier for me to remember certain addresses. It is entirely unnecessary, but I like it this way.

    Let’s say I have a static IPv4: 72.235.228.162

    And IPv6 block: 2660:1100:45f0:c17:: /60

    What I do is set up a Virtual IP in OPNSense and give it the address 2660:1100:45f0:c171:72:235:228:162

    Then I set up the firewall rules for that IP.

    Then I NAT 1:1 that IP to the NGINX VM’s IP and now the Internet doesn’t need to know about it.