Denton Gentry
Denton Gentry
I think the next step is to begin returning both A and AAAA records to MagicDNS queries.
I agree that in 1.30 we'll have better information about whether to include AAAA records in the DNS response. I'd propose to remove this from the blocking list for turning...
> I think this may be some kind of MTU / EDNS issue combined with resolved server feature detection. It's probably our bug, but this combo is tickling it. There...
Could you add a `tailscale bugreport` shortly after sending a DNS query which fails?
The last entry in the allowed IPs list in item 2 is "10.64.0.0/10"; should that be "100.64.0.0/10" ?
I promise that we will update the bug when work begins in earnest.
This is a tracking bug for a feature request. No work has been done on it. You can best signal support by clicking on the reaction buttons in the top...
https://github.com/tailscale/tailscale/issues/925#issuecomment-1164218447 > I've made a script to set up a Mullvad VPN from Wireguard config files, with support for Tailscale (by updating the routing table after the tunnel goes up):...
Shortly before the bugreport: ``` 2022-07-28 21:41:30.468709227 +0000 UTC: allowing exit node access to internal IPs: [127.0.0.0/8] ``` This means that: 1. It did notice and act on the `--exit-node-allow-lan-access`...
> Or provide a way to make tailscale not mess with anything IPv4 related on a particular node (node should not even have a tailscale IPv4 address). There is a...