• 0 Posts
  • 379 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle







  • Overly technical one.

    I was trying to download a 700MB game ISO over ADSL in 2007 in Australia. The modem sync speed was 10Mb of the supposed 24Mb that ADSL could get.
    It would take a while but Dad was also home doing whatever he did online slowing the download. As I was doing my CCNA at the time I thought it would be a fun idea to stop all TCP traffic to my dad’s PC so I could download the ISO faster and get to gaming.

    About 10 min after configuring the modem dad asked if the internet is working for me and naturally it was but he could resolve DNS but not browse websites as they use TCP (this is pre Quic).

    After my download finished I waited a bit longer and changed the modem settings back. I did this a couple times over the years before moving out.

    A several years later when dad changed ISP he asked for my help to change the PPPoE details on the modem and he saw a disabled firewall rule called ‘Suck it dad’ and asked me what that was. So I told him, each time he had internet issues when he could resolve DNS but not access web pages it was me enabling that rule so I could download a game faster.

    He wasn’t angry just annoyed that he never looked at the modem when trying to work out his connectivity issues.










  • I would have a standalone Forgejo server to act as your infrastructure server. Make it separate from your production k8s/k3s environment.
    If something knocks out your infrastructure Forgejo instance then your prod instance will continue to work. If something knocks out your prod, then your infrastructure instance is still there to pull on.

    One of the reasons I suggest k8s/k3s if something happens k8s/k3s will try to automatically bring the broken node back online.