@dataprolet@lemmy.dbzer0.com

dataprolet

@dataprolet@lemmy.dbzer0.com

Formerly know as u/Arjab.
Anarchist | Antifascist | Anticapitalist.
Arch Linux | FOSS | Piracy | Security & Privacy

Looking for a Mastodon instance?
Check out @serverbot.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

dataprolet,

You’re technically right, but nobody anticipated and therefore agreed on their posts being used for training LLMs.

dataprolet,

Oh boy have I bad news for you. You ever heard of copyright?

I Just Don’t See Trans Women As Women

I just can’t wrap my head around it. They want to be called and seen woman, but they have to get bottom surgery. Take hormone pills, all these excessive stuff to be a woman. They don’t have menstrual cycles nor can they carry a child. Why can’t they just be happy being a male and just wear feminine clothes? Like a femboy...

dataprolet,

Have you even tried educating yourself prior to posting this bullshit?

dataprolet,

Full on conspiracy?

there are hidden interests and hands that pull the strings of the dynamics that are harmful

dataprolet,

How can something like Tailscale be blocked?

dataprolet,

Interesting, because Tailacale doesn’t use any special ports. How would that be detected? And could you maybe use Headscale on a dynamic port to circumvent that?

dataprolet,

Systemd-haters would rather install MacOS than admit that systemd is not that bad.

dataprolet,

I’m using Headscale, but yes.

dataprolet,

How do I make sure of this? What am I supposed to see using the command?

dataprolet,

Thanks, that’s what I’m trying to do. :)

And my VPS doesn’t have any IPs in the same range as my home server.

dataprolet,

Doesn’t seem to work.

dataprolet,

No, I’m not using ACLs.

dataprolet,

Yes, both clients can tailscale ping each other and after doing so the status shows active; relay “ams”.

Using tailcale ping 192.168.178.178 also works for some reason.

Not sure what to do with the output of netmap.

dataprolet,

So to confirm your behavior, you can tailscale ping each other fine and tailscale ping to the internal network. You cannot however ping from the OS to the remote internal network?

Exactly.

Have you checked your routing tables to make sure the tailscale client added the route properly?

How do I do this? I use Headscale and headscale routes list shows the following:


<span style="color:#323232;">ID | Machine | Prefix           | Advertised | Enabled | Primary
</span><span style="color:#323232;">1  | server  | 0.0.0.0/0        | false      | false   | -
</span><span style="color:#323232;">2  | server  | ::/0             | false      | false   | -
</span><span style="color:#323232;">3  | server  | 192.168.178.0/24 | true       | true    | true
</span>

Also have you checked your firewall rules? If you’re using ipfw or something, try just turning off iptables briefly and see if that lets you ping through.

I’m not using a firewall, but the VPS is hosted on Hetzner, which has a firewall. But I already allowed UDP port 41641 and 41641. The wg0 rule is from the Wireguard setup I want to replace using Tailscale.


<span style="color:#323232;"># iptables --list-rules
</span><span style="color:#323232;">-P INPUT ACCEPT
</span><span style="color:#323232;">-P FORWARD ACCEPT
</span><span style="color:#323232;">-P OUTPUT ACCEPT
</span><span style="color:#323232;">-N DOCKER
</span><span style="color:#323232;">-N DOCKER-ISOLATION-STAGE-1
</span><span style="color:#323232;">-N DOCKER-ISOLATION-STAGE-2
</span><span style="color:#323232;">-N DOCKER-USER
</span><span style="color:#323232;">-A INPUT -s 100.64.0.0/10 -j ACCEPT
</span><span style="color:#323232;">-A FORWARD -j DOCKER-USER
</span><span style="color:#323232;">-A FORWARD -j DOCKER-ISOLATION-STAGE-1
</span><span style="color:#323232;">-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
</span><span style="color:#323232;">-A FORWARD -o docker0 -j DOCKER
</span><span style="color:#323232;">-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
</span><span style="color:#323232;">-A FORWARD -i docker0 -o docker0 -j ACCEPT
</span><span style="color:#323232;">-A FORWARD -i wg0 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.3/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 443 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.3/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 81 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.3/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 80 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.5/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 9090 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.5/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 8080 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.6/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 443 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER -d 172.17.0.2/32 ! -i docker0 -o docker0 -p tcp -m tcp --dport 9001 -j ACCEPT
</span><span style="color:#323232;">-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
</span><span style="color:#323232;">-A DOCKER-ISOLATION-STAGE-1 -j RETURN
</span><span style="color:#323232;">-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
</span><span style="color:#323232;">-A DOCKER-ISOLATION-STAGE-2 -j RETURN
</span><span style="color:#323232;">-A DOCKER-USER -j RETURN
</span>
dataprolet,

There is no tailscale0, but also not on my home server which also runs Tailscale and which I can access remotely using my Android. Could my existing Wireguard setup interfere with Tailscale?

dataprolet,

I’m not sure the Docker container is even using a tailscale interface, because there is none on my VPS or my home server.

And how do I see whether I have a device at /dev/net/tun?

dataprolet,

Are you sure Tailscale in Docker is creating a wg0 interface? Because I got a working connection between my smartphone and my home server and the home server is not showing any interface related to Tailscale?


<span style="color:#323232;">default via 192.168.178.1 dev ens18 
</span><span style="color:#323232;">172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 
</span><span style="color:#323232;">192.168.178.0/24 dev ens18 proto kernel scope link src 192.168.178.178 
</span>
dataprolet,

Yes I’m running it on Docker and therefore have the docker0 interface.

dataprolet,

Headscale is pretty straight forward to set up and easy to use. And there are multiple WebGUIs available to choose from, if you need. If you have any questions, let me know.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • Youngstown
  • mdbf
  • everett
  • slotface
  • khanakhh
  • ethstaker
  • rosin
  • kavyap
  • tacticalgear
  • modclub
  • JUstTest
  • DreamBathrooms
  • ngwrru68w68
  • Durango
  • tester
  • GTA5RPClips
  • cisconetworking
  • cubers
  • normalnudes
  • osvaldo12
  • provamag3
  • Leos
  • anitta
  • lostlight
  • All magazines