Tailscale doesn't create the network adapter

[CheeryFlame]

I've setup the following

For some reason the tailscale0 network adapter isn't being created.

I've seen others having the same issues online in comment sections but no one actually had answer.

 

[help!]

in the same position

 

[darek-sts]

same on my end

 

[csj]

This is expected behavior. We don't expose the tailscale app interface (any app network interface in that respect) to the webUI.

 

[CheeryFlame]

I'm not an expert so take the following as a noob trying to explain stuff, but it works...

You can confirm if the `tailscale0` interface has been created or not by entering `ip link` in shell. Should return something like this.

Code:

649: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500 link/none

I needed to add the `100.100.100.100` magic dns IP from Tailscale in order to expose my Kubernetes applications.

Network > Edit Interface > DNS Servers

I had to remove the subnet route on Tailscale since both my servers were conflicting each other.

Tailscale Admin > Machines > Edit route settings

Then I needed to add both of my server's ip as nameservers and restrict those to my custom ingress domain.

Tailscale Admin > DNS > Add nameserver > Custom

It should look like this once setup. Basically magic dns will check if the request is for one of your domains and send the traffic to the right server IP, then your DNS server (Blocky from Truecharts in my case) will forward the request to Traefik and resolve the sub.domain.tld request. If the request is for a different domain than the ones configured on your servers it'll send them to Cloudflare or whatever public dns server you've setup.

I really like this method of installing Tailscale on my clients since I don't have to modify the DNS server anymore on my PC and phone and if I reboot the server I don't lose internet anymore.

The downsides are the following (currently trying to fix, please help)

• Can't access virtual machines (even external-service doesn't work)
• Can't access apps by tailscale:ip (requires ingress)

One thing I like as well is that I can configure ingress on app on server A with the domain configured on server B so I can use whichever domain I want for my apps no matter which server it's on.

 

[CheeryFlame]

Actually tried outside of my home network and if the routes are disabled you can't access the apps. So if you got 2 servers on the same vlan it's conflicting. Hopefully my second server is going at a remote site and will be on 192.168.x.x so that should fix it for me.