Evkob (they/them)

Languages: Français, English

Pronouns: They/them

Communities:

  • 1 Post
  • 26 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2023

help-circle
  • I was having issues getting my Android device to use my local DNS server over VPN, what worked for me was setting it up through RethinkDNS. There’s a setting to prevent DNS leaks by capturing all traffic on port 53 and directing it to the DNS server you set. It doesn’t feel like an elegant solution but hey, it works.

    Note, you’ll have to make sure your private DNS setting is off, in the internet section of the system settings.





  • The reason for the VPN is to have access to my Unbound DNS on my phone from anywhere, not only my local network. If I just wanted to configure the DNS on my local network, I’d set up static IP for my network in Android’s settings and input the DNS server manually. This works fine when I set it up, but like I said I want to use Unbound on my phone anywhere via Wireguard.

    I’m not sure what’s the second thing you want me to clarify! Sorry for the confusion, I appreciate you trying to help out :)





  • When connected through wireguard can you access anything on the local network?

    Everything works as expected with Wireguard otherwise, I can ssh into my server or my desktop, and access the other things hosted on my server (although these are all through Docker, which is why I suspect container isolation to be an issue).

    Does this issue also happen when you’re on another network and vpning back?

    Yup, same issues whether I’m on the local network, the WiFi at work, or on LTE.


  • And people wonder why the average person isn’t embracing the fediverse

    I find being able to choose my instance based on their moderation and federation policies much less obtuse than the black-box algorithms and shadow-banning of the mainstream corporate platforms.

    IMO, the average person not embracing the fediverse has much less to do with any flaws in the fediverse (these do exist, don’t get me wrong) and much more to do with inertia, the network effect, and just lack of knowledge or fucks to give about privacy and open platforms.




  • Hey sorry for the late reply, I just wanted to say I really appreciate your perspective here! It’s definitely made me simmer down a bit instead of jumping in head first. I’ll try it out for myself and a few friends first before trying to recruit everyone I know :P

    Part of why I want to do this is that I do want to learn more about all the stuff you mentioned (except Kubernetes, gosh everytime I look up documentation for it I drown in a swarm of terminology).

    As who very much doesn’t work in IT, computer stuff is a fun hobby for me. I can see how assuming the responsibilities for hosting an instance could make it less fun and more work, though.


  • None of my selfhosted stuff is available to the public internet, I run everything through Wireguard. However I do know how to get SSL certificates from Let’s Encrypt because of previous messing around.

    Backups is definitely something that I’m lazy about with my selfhosting that I’d need to address for a public service. I currently just manually copy over the few essential files I have to my server, my desktop and my phone. If I commit to hosting stuff for others, proper backups are definitely at the top of the priority list.

    Governance is something I’ve already thought a lot about, since these services would be aimed at a specific minority community.

    Thanks for your comment! I’m currently messing about with Hugo to build a landing page to explain decentralized, federated servers and link to services I might host in the future. I really want to do this, I don’t want to just accept that the common communication platforms are controlled by American fascists.






  • It depends on if you want to access it from anywhere (or give others access), or if you’re only accessing your server from specific devices.

    Since I only ever access my server from my phone or my desktop, I use Wireguard via wg-easy. You set it up as a docker container on your server and it gives you a neat web UI (defaults to port 51821) from which to add Wireguard clients. Once connected through Wireguard, you can access your services as if you’re on the server’s local network.

    Note, you’ll of course have to open up a port for Wireguard on your router for this to work, the default being 51820.