home.social

#headscale — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #headscale, aggregated by home.social.

  1. Setup #headscale for fun today (it is an open source reimplementation of the #Tailscale Servers) was quite easy, just that at some point the docs stated to use FQDN but it was not just the domain name required but also https:// and the port it seems. Still got it working, was just mildly annoying.
    Running natively on #Debian was so easy to set up otherwise. Will set up some sort of UI later on maybe even with #SSO via my #Keycloak.

    #homelab #selfhosting

  2. Setup #headscale for fun today (it is an open source reimplementation of the #Tailscale Servers) was quite easy, just that at some point the docs stated to use FQDN but it was not just the domain name required but also https:// and the port it seems. Still got it working, was just mildly annoying.
    Running natively on #Debian was so easy to set up otherwise. Will set up some sort of UI later on maybe even with #SSO via my #Keycloak.

    #homelab #selfhosting

  3. @mkwadee I could never manage to get any external access stuff working with reverse proxies and certificates and authentication (this was pre LLM-days), so I just installed Tailscale. Wow was that easy!

    My homelab services are for me and my family anyway, so I just put Tailscale on their devices and added them to the same Tailnet. Done. I can even host my own control server with Headscale and not touch any Tailscale servers.

    #Linux #HomeLab #SelfHost #Tailscale #Headscale

  4. @mkwadee I could never manage to get any external access stuff working with reverse proxies and certificates and authentication (this was pre LLM-days), so I just installed Tailscale. Wow was that easy!

    My homelab services are for me and my family anyway, so I just put Tailscale on their devices and added them to the same Tailnet. Done. I can even host my own control server with Headscale and not touch any Tailscale servers.

  5. @mkwadee I could never manage to get any external access stuff working with reverse proxies and certificates and authentication (this was pre LLM-days), so I just installed Tailscale. Wow was that easy!

    My homelab services are for me and my family anyway, so I just put Tailscale on their devices and added them to the same Tailnet. Done. I can even host my own control server with Headscale and not touch any Tailscale servers.

    #Linux #HomeLab #SelfHost #Tailscale #Headscale

  6. @mkwadee I could never manage to get any external access stuff working with reverse proxies and certificates and authentication (this was pre LLM-days), so I just installed Tailscale. Wow was that easy!

    My homelab services are for me and my family anyway, so I just put Tailscale on their devices and added them to the same Tailnet. Done. I can even host my own control server with Headscale and not touch any Tailscale servers.

    #Linux #HomeLab #SelfHost #Tailscale #Headscale

  7. @mkwadee I could never manage to get any external access stuff working with reverse proxies and certificates and authentication (this was pre LLM-days), so I just installed Tailscale. Wow was that easy!

    My homelab services are for me and my family anyway, so I just put Tailscale on their devices and added them to the same Tailnet. Done. I can even host my own control server with Headscale and not touch any Tailscale servers.

    #Linux #HomeLab #SelfHost #Tailscale #Headscale

  8. Quite pleased with this.
    1 year uptime of 99.9% for website hosted on our internal LAN served to internet using #Headscale

    #selfhosting

  9. Good morning!

    I have been happily using headscale (self hosted implementation tailscale's management service) for some time. An update was over-due but I was struggling to get things working in a satisfactory way. And I didn't like that my set-up wasn't portable (a lot of manual set-up is required).

    This led me to plan out what my ideal headscale project would look like:
    * Everything runs in docker
    * Containers for headscale, headscale-ui, and caddy
    * Re-implement user names in the MagicDNS (eg "mobile" is a user, resulting in "iain-t480s.mobile.example.com") that was removed in 0.23.0+ versions of headscale
    * Backup and restore procedures
    * Single file configuration

    Over a few cocktails while on holiday, I instructed OpenCode, with the Big Pickle model, to develop this project.

    The result is github.com/bigcalm/headscale-c

    A simple project I can clone to any public facing server and hit the ground running with minimal config set-up.

    A few notes:
    * I have 20 years experience of linux server management, programming, devops, project management, and quality assurance.
    * While OpenCode created all of the file contents, I provided the requirements, code review, testing, feedback, and more testing.
    * This has been an iterative process to create a fully working project that I am happy with. Not a single prompt and ship whatever gets created.
    * I am not a tech bro.
    * Agentic development is a useful tool. But only a tool that I have been able to use due to my prior knowledge.

    The project isn't perfect, but it suits my needs. Maybe it can help somebody else too :)

    #headscale #tailscale #selfhosting #opencode #bigpickle

  10. Good morning!

    I have been happily using headscale (self hosted implementation tailscale's management service) for some time. An update was over-due but I was struggling to get things working in a satisfactory way. And I didn't like that my set-up wasn't portable (a lot of manual set-up is required).

    This led me to plan out what my ideal headscale project would look like:
    * Everything runs in docker
    * Containers for headscale, headscale-ui, and caddy
    * Re-implement user names in the MagicDNS (eg "mobile" is a user, resulting in "iain-t480s.mobile.example.com") that was removed in 0.23.0+ versions of headscale
    * Backup and restore procedures
    * Single file configuration

    Over a few cocktails while on holiday, I instructed OpenCode, with the Big Pickle model, to develop this project.

    The result is github.com/bigcalm/headscale-c

    A simple project I can clone to any public facing server and hit the ground running with minimal config set-up.

    A few notes:
    * I have 20 years experience of linux server management, programming, devops, project management, and quality assurance.
    * While OpenCode created all of the file contents, I provided the requirements, code review, testing, feedback, and more testing.
    * This has been an iterative process to create a fully working project that I am happy with. Not a single prompt and ship whatever gets created.
    * I am not a tech bro.
    * Agentic development is a useful tool. But only a tool that I have been able to use due to my prior knowledge.

    The project isn't perfect, but it suits my needs. Maybe it can help somebody else too :)

    #headscale #tailscale #selfhosting #opencode #bigpickle

  11. Good morning!

    I have been happily using headscale (self hosted implementation tailscale's management service) for some time. An update was over-due but I was struggling to get things working in a satisfactory way. And I didn't like that my set-up wasn't portable (a lot of manual set-up is required).

    This led me to plan out what my ideal headscale project would look like:
    * Everything runs in docker
    * Containers for headscale, headscale-ui, and caddy
    * Re-implement user names in the MagicDNS (eg "mobile" is a user, resulting in "iain-t480s.mobile.example.com") that was removed in 0.23.0+ versions of headscale
    * Backup and restore procedures
    * Single file configuration

    Over a few cocktails while on holiday, I instructed OpenCode, with the Big Pickle model, to develop this project.

    The result is github.com/bigcalm/headscale-c

    A simple project I can clone to any public facing server and hit the ground running with minimal config set-up.

    A few notes:
    * I have 20 years experience of linux server management, programming, devops, project management, and quality assurance.
    * While OpenCode created all of the file contents, I provided the requirements, code review, testing, feedback, and more testing.
    * This has been an iterative process to create a fully working project that I am happy with. Not a single prompt and ship whatever gets created.
    * I am not a tech bro.
    * Agentic development is a useful tool. But only a tool that I have been able to use due to my prior knowledge.

    The project isn't perfect, but it suits my needs. Maybe it can help somebody else too :)

    #headscale #tailscale #selfhosting #opencode #bigpickle

  12. Good morning!

    I have been happily using headscale (self hosted implementation tailscale's management service) for some time. An update was over-due but I was struggling to get things working in a satisfactory way. And I didn't like that my set-up wasn't portable (a lot of manual set-up is required).

    This led me to plan out what my ideal headscale project would look like:
    * Everything runs in docker
    * Containers for headscale, headscale-ui, and caddy
    * Re-implement user names in the MagicDNS (eg "mobile" is a user, resulting in "iain-t480s.mobile.example.com") that was removed in 0.23.0+ versions of headscale
    * Backup and restore procedures
    * Single file configuration

    Over a few cocktails while on holiday, I instructed OpenCode, with the Big Pickle model, to develop this project.

    The result is github.com/bigcalm/headscale-c

    A simple project I can clone to any public facing server and hit the ground running with minimal config set-up.

    A few notes:
    * I have 20 years experience of linux server management, programming, devops, project management, and quality assurance.
    * While OpenCode created all of the file contents, I provided the requirements, code review, testing, feedback, and more testing.
    * This has been an iterative process to create a fully working project that I am happy with. Not a single prompt and ship whatever gets created.
    * I am not a tech bro.
    * Agentic development is a useful tool. But only a tool that I have been able to use due to my prior knowledge.

    The project isn't perfect, but it suits my needs. Maybe it can help somebody else too :)

    #headscale #tailscale #selfhosting #opencode #bigpickle

  13. Good morning!

    I have been happily using headscale (self hosted implementation tailscale's management service) for some time. An update was over-due but I was struggling to get things working in a satisfactory way. And I didn't like that my set-up wasn't portable (a lot of manual set-up is required).

    This led me to plan out what my ideal headscale project would look like:
    * Everything runs in docker
    * Containers for headscale, headscale-ui, and caddy
    * Re-implement user names in the MagicDNS (eg "mobile" is a user, resulting in "iain-t480s.mobile.example.com") that was removed in 0.23.0+ versions of headscale
    * Backup and restore procedures
    * Single file configuration

    Over a few cocktails while on holiday, I instructed OpenCode, with the Big Pickle model, to develop this project.

    The result is github.com/bigcalm/headscale-c

    A simple project I can clone to any public facing server and hit the ground running with minimal config set-up.

    A few notes:
    * I have 20 years experience of linux server management, programming, devops, project management, and quality assurance.
    * While OpenCode created all of the file contents, I provided the requirements, code review, testing, feedback, and more testing.
    * This has been an iterative process to create a fully working project that I am happy with. Not a single prompt and ship whatever gets created.
    * I am not a tech bro.
    * Agentic development is a useful tool. But only a tool that I have been able to use due to my prior knowledge.

    The project isn't perfect, but it suits my needs. Maybe it can help somebody else too :)

    #headscale #tailscale #selfhosting #opencode #bigpickle

  14. #netbird ist ja komplett out of control!

    Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
    Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
    Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

    Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

    #diy #homelab #overlaynetwork #wireguard

    danke @staticvoid für den #nerdsnipe

  15. #netbird ist ja komplett out of control!

    Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
    Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
    Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

    Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

    #diy #homelab #overlaynetwork #wireguard

    danke @staticvoid für den #nerdsnipe

  16. #netbird ist ja komplett out of control!

    Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
    Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
    Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

    Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

    #diy #homelab #overlaynetwork #wireguard

    danke @staticvoid für den #nerdsnipe

  17. #netbird ist ja komplett out of control!

    Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
    Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
    Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

    Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

    #diy #homelab #overlaynetwork #wireguard

    danke @staticvoid für den #nerdsnipe

  18. #netbird ist ja komplett out of control!

    Ich wollte per #headscale meine VPS mit meiner homeprod verdrahten.
    Netbird ist alles was tailscale per SaaS sein kann, aber #selfhosted.
    Das setup ist irre. FW auf auf den relevanten Ports, DNS aufsetzen, script anwerfen, Fertig.

    Wer wie ich keine Lust auf externe Infrastruktur ausserhalb der eigenen Kontrolle hat und site2site braucht, ich glaube besser gehts nich.

    #diy #homelab #overlaynetwork #wireguard

    danke @staticvoid für den #nerdsnipe

  19. Wenn man einmal anfängt ...
    Nach Feierabend "bloss" mal eben #crowdsec auf der outpost vps aufsetzen. Ok, geht. Oh, da sieht man ja die ganzen ssh-bruteforces ... Prometheus draussen im Web aufmachen keine so gute Idee, aber will adminp0rn, gibt so schöne Dashboards.

    Zwischendrin @oli nmap Terror machen geschickt, um die alerts zu testen 🤖

    Bis halb 12 #headscale aufgesetzt mit ein paar Stolperern und jetzt ist besser mal Schluss für heute.

    Up next: #tailscale IM docker

  20. Wenn man einmal anfängt ...
    Nach Feierabend "bloss" mal eben #crowdsec auf der outpost vps aufsetzen. Ok, geht. Oh, da sieht man ja die ganzen ssh-bruteforces ... Prometheus draussen im Web aufmachen keine so gute Idee, aber will adminp0rn, gibt so schöne Dashboards.

    Zwischendrin @oli nmap Terror machen geschickt, um die alerts zu testen 🤖

    Bis halb 12 #headscale aufgesetzt mit ein paar Stolperern und jetzt ist besser mal Schluss für heute.

    Up next: #tailscale IM docker

  21. Wenn man einmal anfängt ...
    Nach Feierabend "bloss" mal eben #crowdsec auf der outpost vps aufsetzen. Ok, geht. Oh, da sieht man ja die ganzen ssh-bruteforces ... Prometheus draussen im Web aufmachen keine so gute Idee, aber will adminp0rn, gibt so schöne Dashboards.

    Zwischendrin @oli nmap Terror machen geschickt, um die alerts zu testen 🤖

    Bis halb 12 #headscale aufgesetzt mit ein paar Stolperern und jetzt ist besser mal Schluss für heute.

    Up next: #tailscale IM docker

  22. Wenn man einmal anfängt ...
    Nach Feierabend "bloss" mal eben #crowdsec auf der outpost vps aufsetzen. Ok, geht. Oh, da sieht man ja die ganzen ssh-bruteforces ... Prometheus draussen im Web aufmachen keine so gute Idee, aber will adminp0rn, gibt so schöne Dashboards.

    Zwischendrin @oli nmap Terror machen geschickt, um die alerts zu testen 🤖

    Bis halb 12 #headscale aufgesetzt mit ein paar Stolperern und jetzt ist besser mal Schluss für heute.

    Up next: #tailscale IM docker

  23. Wenn man einmal anfängt ...
    Nach Feierabend "bloss" mal eben #crowdsec auf der outpost vps aufsetzen. Ok, geht. Oh, da sieht man ja die ganzen ssh-bruteforces ... Prometheus draussen im Web aufmachen keine so gute Idee, aber will adminp0rn, gibt so schöne Dashboards.

    Zwischendrin @oli nmap Terror machen geschickt, um die alerts zu testen 🤖

    Bis halb 12 #headscale aufgesetzt mit ein paar Stolperern und jetzt ist besser mal Schluss für heute.

    Up next: #tailscale IM docker

  24. Be me.
    Make a typo `pcke` instead of `pkce` in your NixOS config for headscale.
    Config does not get spellchecked, just converted to yml.
    Kandidm does not reciece pkce challenge.
    Fight for hours over 4 weeks to finally decide to open the generated yml.

    GG.

    #NixOS #HeadScale #KanIDM

  25. Be me.
    Make a typo `pcke` instead of `pkce` in your NixOS config for headscale.
    Config does not get spellchecked, just converted to yml.
    Kandidm does not reciece pkce challenge.
    Fight for hours over 4 weeks to finally decide to open the generated yml.

    GG.

    #NixOS #HeadScale #KanIDM

  26. Be me.
    Make a typo `pcke` instead of `pkce` in your NixOS config for headscale.
    Config does not get spellchecked, just converted to yml.
    Kandidm does not reciece pkce challenge.
    Fight for hours over 4 weeks to finally decide to open the generated yml.

    GG.

    #NixOS #HeadScale #KanIDM

  27. Be me.
    Make a typo `pcke` instead of `pkce` in your NixOS config for headscale.
    Config does not get spellchecked, just converted to yml.
    Kandidm does not reciece pkce challenge.
    Fight for hours over 4 weeks to finally decide to open the generated yml.

    GG.

    #NixOS #HeadScale #KanIDM

  28. Be me.
    Make a typo `pcke` instead of `pkce` in your NixOS config for headscale.
    Config does not get spellchecked, just converted to yml.
    Kandidm does not reciece pkce challenge.
    Fight for hours over 4 weeks to finally decide to open the generated yml.

    GG.

    #NixOS #HeadScale #KanIDM

  29. Do someone know why exactly do #bitwarden is forcing https on self-hosted servers? I have #vaultwarden behind #headscale already, and all the bitwarden clients are refusing to work (unless I stop them from updating). Seems like a dick move. #askfedi

  30. Do someone know why exactly do #bitwarden is forcing https on self-hosted servers? I have #vaultwarden behind #headscale already, and all the bitwarden clients are refusing to work (unless I stop them from updating). Seems like a dick move. #askfedi

  31. Do someone know why exactly do #bitwarden is forcing https on self-hosted servers? I have #vaultwarden behind #headscale already, and all the bitwarden clients are refusing to work (unless I stop them from updating). Seems like a dick move. #askfedi

  32. Do someone know why exactly do #bitwarden is forcing https on self-hosted servers? I have #vaultwarden behind #headscale already, and all the bitwarden clients are refusing to work (unless I stop them from updating). Seems like a dick move. #askfedi

  33. Do someone know why exactly do #bitwarden is forcing https on self-hosted servers? I have #vaultwarden behind #headscale already, and all the bitwarden clients are refusing to work (unless I stop them from updating). Seems like a dick move. #askfedi

  34. #Tailscale was really decent, but I think #Headscale needs more time to mature

  35. #Tailscale was really decent, but I think #Headscale needs more time to mature

  36. #Tailscale was really decent, but I think #Headscale needs more time to mature

  37. I tried out #tailscale today, and am making a rocky start to hosting my own #headscale server. I normally dislike #Discord, but made an exception to enter their chat forum - where I eventually got helped with my config troubles. I have a working config now, so I'm grateful for the help I got.
    #InfoSec #OpenSource

  38. I tried out #tailscale today, and am making a rocky start to hosting my own #headscale server. I normally dislike #Discord, but made an exception to enter their chat forum - where I eventually got helped with my config troubles. I have a working config now, so I'm grateful for the help I got.
    #InfoSec #OpenSource

  39. I tried out #tailscale today, and am making a rocky start to hosting my own #headscale server. I normally dislike #Discord, but made an exception to enter their chat forum - where I eventually got helped with my config troubles. I have a working config now, so I'm grateful for the help I got.
    #InfoSec #OpenSource

  40. I tried out #tailscale today, and am making a rocky start to hosting my own #headscale server. I normally dislike #Discord, but made an exception to enter their chat forum - where I eventually got helped with my config troubles. I have a working config now, so I'm grateful for the help I got.
    #InfoSec #OpenSource

  41. I tried out #tailscale today, and am making a rocky start to hosting my own #headscale server. I normally dislike #Discord, but made an exception to enter their chat forum - where I eventually got helped with my config troubles. I have a working config now, so I'm grateful for the help I got.
    #InfoSec #OpenSource

  42. Today I applied to do a 30-minute presentation for Bsides 2026. I offered to do a presentation and demo of Wireguard, where Wireguard is used in a TailScale/Headscale sort of way, but somewhat simpler. My solution is much more "pure-play" Wireguard - I wrote no software beyond using the conveniences provided by PiVPN. My "secret sauce" lies in being able to understand, and hand-edit wireguard conf files beyond a simplistic use. My solution has no "mesh" - it just uses a subnet where each node on the subnet is a working Wireguard client. My solution has no AI. I consider this to be a feature, not a bug. My solution uses conventional DNS, there is no "Magic DNS". My solution has no 2FA. It just uses Wireguard's default encryption methods, as are part of the mainline Linux kernel. The advantage to this is that all clients and server components are Open Source, whereas the Tailscale clients (Windows and macOS/iOS) are closed source.
    #Wireguard #Tailscale #Headscale #infosec #VPN #OpenSource #linux @bsidesyxe

  43. Today I applied to do a 30-minute presentation for Bsides 2026. I offered to do a presentation and demo of Wireguard, where Wireguard is used in a TailScale/Headscale sort of way, but somewhat simpler. My solution is much more "pure-play" Wireguard - I wrote no software beyond using the conveniences provided by PiVPN. My "secret sauce" lies in being able to understand, and hand-edit wireguard conf files beyond a simplistic use. My solution has no "mesh" - it just uses a subnet where each node on the subnet is a working Wireguard client. My solution has no AI. I consider this to be a feature, not a bug. My solution uses conventional DNS, there is no "Magic DNS". My solution has no 2FA. It just uses Wireguard's default encryption methods, as are part of the mainline Linux kernel. The advantage to this is that all clients and server components are Open Source, whereas the Tailscale clients (Windows and macOS/iOS) are closed source.
    #Wireguard #Tailscale #Headscale #infosec #VPN #OpenSource #linux @bsidesyxe

  44. Today I applied to do a 30-minute presentation for Bsides 2026. I offered to do a presentation and demo of Wireguard, where Wireguard is used in a TailScale/Headscale sort of way, but somewhat simpler. My solution is much more "pure-play" Wireguard - I wrote no software beyond using the conveniences provided by PiVPN. My "secret sauce" lies in being able to understand, and hand-edit wireguard conf files beyond a simplistic use. My solution has no "mesh" - it just uses a subnet where each node on the subnet is a working Wireguard client. My solution has no AI. I consider this to be a feature, not a bug. My solution uses conventional DNS, there is no "Magic DNS". My solution has no 2FA. It just uses Wireguard's default encryption methods, as are part of the mainline Linux kernel. The advantage to this is that all clients and server components are Open Source, whereas the Tailscale clients (Windows and macOS/iOS) are closed source.
    #Wireguard #Tailscale #Headscale #infosec #VPN #OpenSource #linux @bsidesyxe

  45. Today I applied to do a 30-minute presentation for Bsides 2026. I offered to do a presentation and demo of Wireguard, where Wireguard is used in a TailScale/Headscale sort of way, but somewhat simpler. My solution is much more "pure-play" Wireguard - I wrote no software beyond using the conveniences provided by PiVPN. My "secret sauce" lies in being able to understand, and hand-edit wireguard conf files beyond a simplistic use. My solution has no "mesh" - it just uses a subnet where each node on the subnet is a working Wireguard client. My solution has no AI. I consider this to be a feature, not a bug. My solution uses conventional DNS, there is no "Magic DNS". My solution has no 2FA. It just uses Wireguard's default encryption methods, as are part of the mainline Linux kernel. The advantage to this is that all clients and server components are Open Source, whereas the Tailscale clients (Windows and macOS/iOS) are closed source.
    #Wireguard #Tailscale #Headscale #infosec #VPN #OpenSource #linux @bsidesyxe

  46. Today I applied to do a 30-minute presentation for Bsides 2026. I offered to do a presentation and demo of Wireguard, where Wireguard is used in a TailScale/Headscale sort of way, but somewhat simpler. My solution is much more "pure-play" Wireguard - I wrote no software beyond using the conveniences provided by PiVPN. My "secret sauce" lies in being able to understand, and hand-edit wireguard conf files beyond a simplistic use. My solution has no "mesh" - it just uses a subnet where each node on the subnet is a working Wireguard client. My solution has no AI. I consider this to be a feature, not a bug. My solution uses conventional DNS, there is no "Magic DNS". My solution has no 2FA. It just uses Wireguard's default encryption methods, as are part of the mainline Linux kernel. The advantage to this is that all clients and server components are Open Source, whereas the Tailscale clients (Windows and macOS/iOS) are closed source.
    #Wireguard #Tailscale #Headscale #infosec #VPN #OpenSource #linux @bsidesyxe

  47. En el siguiente #tutorial les muestro como crear una #vpn #mesh y utilizarla con los equipos que desees sin restricciones gracias a #headscale y #tailscale sobre tu propio servidor o #selfhosted. Algo que me pareció muy útil para estos tiempos...

    Miralo en : luiszambrana.ar/como-instalar-

    Si te gusto compartilo con los tuyos!!!

  48. En el siguiente #tutorial les muestro como crear una #vpn #mesh y utilizarla con los equipos que desees sin restricciones gracias a #headscale y #tailscale sobre tu propio servidor o #selfhosted. Algo que me pareció muy útil para estos tiempos...

    Miralo en : luiszambrana.ar/como-instalar-

    Si te gusto compartilo con los tuyos!!!

  49. En el siguiente #tutorial les muestro como crear una #vpn #mesh y utilizarla con los equipos que desees sin restricciones gracias a #headscale y #tailscale sobre tu propio servidor o #selfhosted. Algo que me pareció muy útil para estos tiempos...

    Miralo en : luiszambrana.ar/como-instalar-

    Si te gusto compartilo con los tuyos!!!

  50. En el siguiente #tutorial les muestro como crear una #vpn #mesh y utilizarla con los equipos que desees sin restricciones gracias a #headscale y #tailscale sobre tu propio servidor o #selfhosted. Algo que me pareció muy útil para estos tiempos...

    Miralo en : luiszambrana.ar/como-instalar-

    Si te gusto compartilo con los tuyos!!!