I have a kubernetes cluster provisioned in a hypervisor. I have a tailscale pod running that advertises the kubernetes subnet and also accepts routes. The subnet is 192.168.0.0/16 I have tailscale setup to dns cluster.local to 192.168.1.10 (internal kubernetes dns server)
I have pfsense (firewall/router) on a totally separate machine and have installed tailscale package in pfsense and also advertises the private network of the machines and vms on 10.1.1.0/24 and accepts routes. I have tailscale setup to dns mydomain.local to 10.1.1.1 (ip of pfsense and dns resolver)
The physical machines pfsense, xcp, nfs AND vms are all on the subnet 10.1.1.0/24.
I have tailscale on my home pc out side of the physical network described above
When I connect from my pc to 192.168 subnet all works as expected. However when I try to connect from a machine on 10.1.1.0 subnet, the tailscale log out put on the 192.168 subnet shows this: 2022/10/08 17:21:56 CreateEndpoint error for 10.1.1.104:46546 -> 192.168.7.55:3000: connection was refused Then service at that ip and port defiantly work as I have confirmed this. What would cause tailscale to output this error message. What is it really saying…who is refusing the connection?