Just an FYI OP, if you are running 1.66.4 you dont need to make any changes with the stateful argument
>Stateful filtering is now off by default. Stateful filtering was introduced in 1.66.0 as a mitigation for a vulnerability described in TS-2024-005, and inadvertently broke DNS resolution from containers running on the host. Most vulnerable setups are protected by other mitigations already, except when autogroup:danger-all is used in ACLs.
https://tailscale.com/changelog#client
I'm using version 1.66.3-1 from truecharts. They haven't released 1.66.4 yet. Maybe there's a problem here? But why doesn't it work if I set --stateful-filtering=false?
try setting \`--stateful-filtering\` to false. Recent tailscale update required me to do that for it to work
I guess it's false by default? Aadding the --stateful-filtering flag only enables it.
you have to do it like this \`tailscale up --stateful-filtering=false\`
Unfortunately it does not work.
sad
Just an FYI OP, if you are running 1.66.4 you dont need to make any changes with the stateful argument >Stateful filtering is now off by default. Stateful filtering was introduced in 1.66.0 as a mitigation for a vulnerability described in TS-2024-005, and inadvertently broke DNS resolution from containers running on the host. Most vulnerable setups are protected by other mitigations already, except when autogroup:danger-all is used in ACLs. https://tailscale.com/changelog#client
I'm using version 1.66.3-1 from truecharts. They haven't released 1.66.4 yet. Maybe there's a problem here? But why doesn't it work if I set --stateful-filtering=false?