Comment

Thanks, I did check that my machine had IP forwarding enabled, and it does. I also ran those lines to create the config file as well, but that didn’t change anything. And I do have the lines in my compose file to advertise routes.

source

Sort:hotnew top

codemichael@lemmy.world ⁨1⁩ ⁨day⁩ ago
If it’s enable then this command should produce a 1 in the output

cat /proc/sys/net/ipv4/ip_forward
source
- pirateMonkey@lemmy.world ⁨1⁩ ⁨day⁩ ago
  Yes, it does (been checking with sysctl net.ipv4.ip_forward, but guess it’s the same thing). It seems like the issue may be that IPv6 may not be enabled within the container. It’s enabled on the host, but the docker logs say ipv6 forwarding is not enabled.
  
  source
  - codemichael@lemmy.world ⁨1⁩ ⁨day⁩ ago
    Did you end up enabling ipv6 as well? Did that help?
    
    source
    pirateMonkey@lemmy.world ⁨1⁩ ⁨day⁩ ago
    Yes, I believe I made the stupid mistake of not restarting after enabling. Once I did that the warning went away and I was able to enable subnets, but I’m still not able to see my local services (where I try to access via the IP of the host given by Tailscale or the magicDNS address). So, progress!
    
    source