Hello! I (tried, at least) converted an old laptop to a Debian home server, and I was trying to set up duckdns.org and to enable port forwarding on my router. internet connection was working, I installed packages, docker, immich, etc, and then suddenly (I don’t know exactly when) it refuses to connect to the internet. It does connect to local addresses (I can ssh into it) but ping google.com and any other internet-involving command fail. I had set up a rule on the router to forward port 80 to the device’s port 80, but I then removed the rule and it still does not connect to the internet. I rebooted the router but nothing changed. Any idea what could be? the router is a Vodafone router.

I changed the hostname to debianserver but on the router it is still written debian. Also, it’s the only device with unknown ipv6

thanks in advance!

  • mozz@mbin.grits.dev
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    This is kind of a nutty network config. It looks like docker is setting up extra default routes, which I could easily see fouling everything up. As a first experiment (warning, this may ruin your networking until the next reboot):

    ip route flush 0/0
    ip route add default via 192.168.1.1 dev enp1s0
    

    … and see if that makes things work (start with ping 192.168.1.1 and ping 8.8.8.8). If that solves the problem, then I think something about your docker config is adding stuff to your networking that’s causing the problem; maybe remove/disable docker completely and then re-add docker things one at a time to see where the problem comes in.

    • tubbadu@lemmy.kde.socialOP
      link
      fedilink
      arrow-up
      0
      ·
      10 months ago

      okay, I thought to have solved the problem but I was wrong, here I go again. When I docker compose up -d the immich server (the only one I have installed) all those routes are created, and apparently some of them conflicts with something else and now my host has no internet connection. however it seems that ip route flush 0/0 solves the problem until the reboot, which is strange. the other command returns RTNETLINK answers: File exists

      • mozz@mbin.grits.dev
        link
        fedilink
        arrow-up
        0
        ·
        10 months ago

        Hm. Yeah, that’s weird. The default routes you’re seeing should basically never exist, so it sounds like there’s some kind of manual network config happening inside the Docker container that’s creating a broken network.

        What does docker network inspect [network] say for each of your Docker networks (substituting each Docker network for “[network]”)? What’s the network section of docker-compose.yml look like?