←
NetBird469 posts
NetBird avatar

NetBird

@netbird

Next Generation of Network Access and Security. github.com/netbirdio/netbird

◷ Joined January 2021▧ 204 Photos and videos
NetBird avatar
NetBird@netbird·Nov 14

Self-hosted NetBird behind Nginx or Cloudflare There's now an official guide for running the server behind Nginx or Cloudflare's proxy. It covers the gRPC and SSL settings Cloudflare needs, an external STUN server because UDP doesn't pass the proxy, and the firewall rules that close the direct path. docs.netbird.io/selfhosted/e…

Victoria Slocum avatar
⟳ NetBird retweeted
Victoria Slocum@victorialslocum·Nov 11

You’re traveling and want to check the security cameras on your home network, or grab a file off the NAS sitting in your closet. The cameras definitely can’t run a VPN client, and the NAS might be able to, but setting it up there can get complicated. So how do you connect? 𝗥𝗼𝘂𝘁𝗶𝗻𝗴 𝗽𝗲𝗲𝗿𝘀! A routing peer is a normal device in your mesh network that can forward incoming traffic to other devices on its local network. So something like a Raspberry Pi or a small server running the VPN client would sit at home with your cameras and NAS, and then you would reach the cameras or NAS through it without having to install the VPN client directly on those devices. Let’s break it down more: 1. Your laptop encrypts the packet over WireGuard and sends it to the routing peer. 2. The routing peer forwards it on the local network to the resource. It rewrites the source address to its own local IP, so to the cameras it just looks like a request from another device at home, and they don’t need to know anything about the mesh. 3. Any replies just go back the same way. You can run it as an 𝗲𝘅𝗶𝘁 𝗻𝗼𝗱𝗲 too, so all your internet traffic goes out through the routing peer and looks like it’s coming from wherever the routing peer is, like your home network while you’re traveling. Access policies make sure the whole LAN isn’t open to everyone. You decide which devices can reach which resources, so your phone could reach the cameras but nothing else on your home network. and NO OPEN PORTS Learn more: docs.netbird.io/manage/netwo…

Post attachment
NetBird avatar
NetBird@netbird·Nov 10

You can self-host all of NetBird on your own server, with no user or device caps on the Community Edition. P2P connections, network routes, exit nodes, and the built-in reverse proxy are all included. Full walkthrough on a fresh VPS 👇

Post attachment
NetBird avatar
NetBird@netbird·Nov 5

CrowdSec AppSec is a web app firewall that inspects every HTTP request for anything malicious. As soon as you spin up a fresh server, you’ll have bots hammering /.𝚎𝚗𝚟 and trying every SSH password they know. This is where CrowdSec comes in, blocking malicious IP addresses based on a community-curated blocklist. So when any server running CrowdSec catches an IP misbehaving, that IP gets blocked for everyone else too. NetBird Proxy publishes your internal services to the internet, so on top of CIDR allowlists and country blocking, you can turn on CrowdSec for each service and set it to observe or enforce. If you self-host NetBird with NetBird Proxy and CrowdSec, you can go a step further and put AppSec in front of the NetBird dashboard itself! AppSec checks what the request actually asks for, which means that, for example, a probe for /.env from an IP that isn't on any blocklist will still get a 403. It covers the dashboard, its API and the sign-in endpoints, through the CrowdSec plugin for Traefik and runs on the same container as CrowdSec. Read the full guide: netbird.io/knowledge-hub/pro…

Post attachment
NetBird avatar
NetBird@netbird·Nov 3

Set a different login rule for each path in the reverse proxy! The reverse proxy lets you have private apps on a public web address without opening ports + protected by some sort of auth (SSO, password, PIN, etc) Before, one login rule applied to the entire app. But now path-based auth changes that. Under the target settings for the reverse proxy, you have three optional access settings: • Use service authentication: Apply the authentication configured on the service, default. • Bypass authentication: Skip SSO, password, PIN, and header authentication for this path. CIDR, country, and CrowdSec restrictions will still apply • Block access: Return 𝟺𝟶𝟹 without contacting the backend. So now a service can require SSO on /, skip entirely auth for a webhook or health check on /𝚠𝚎𝚋𝚑𝚘𝚘𝚔𝚜/ or /𝚑𝚎𝚊𝚕𝚝𝚑𝚣, and block /𝚊𝚍𝚖𝚒𝚗/ or /𝚖𝚎𝚝𝚛𝚒𝚌𝚜 from the public domain entirely. Docs: docs.netbird.io/manage/rever…

Post attachment
Harshit Chaudhary avatar
⟳ NetBird retweeted
Harshit Chaudhary@Harshitc007·Nov 1

Vortix 0.6 is out 🚀: it now runs your @netbird networks, next to WireGuard and OpenVPN. New to Vortix? One terminal UI for every VPN you use. One kill switch, leak checks, works over SSH. Already using it? Upgrade, press i, type netbird. github.com/Harry-kp/vortix

NetBird avatar
NetBird@netbird·Oct 29

Connected should not mean trusted. Zero trust means removing the layer of automatic trust that usually comes from being inside a network. Instead, every connection requires a policy that explicitly allows it. This means one compromised laptop cannot move laterally throughout a network. For example: If you had a production orders application with web, app, and database layers, you could structure the zero trust network policies like this. • Users → web on TCP/443 • Web → app on TCP/8443 • App → database on TCP/5432 • Monitoring to all on 9100 and 9200 • Relevant groups to DNS on UDP and TCP/53 So if a support laptop is compromised, is can still only reach the web, and not the prod database directly. This doesn't stop the attack from happening, but it does stop the attacker from accessing any resource inside the network. Read the full guide on implementing ZTN: netbird.io/knowledge-hub/imp…

Post attachment
NetBird avatar
NetBird@netbird·Oct 27

PHP2Shell and three other major security issues hit self hosted services last week. PHP2Shell had a vulnerability that let attackers run code on PHP servers without logging in. If you self-host anything, there’s a good chance PHP is running on one of your containers. Here’s what to do: • Make sure everything is updated. Rebuild your PHP containers, including NextCloud and WordPress, on the patched base. • If a service doesn’t need to be public, take it off the open internet. • Assume anything old and exposed was compromised, and rotate any credentials. Check out Brandon’s full breakdown here on YouTube: youtube.com/watch?v=ksmWCWw5…

Post attachment
TimRambo🐧 avatar
⟳ NetBird retweeted
TimRambo🐧@TimRamboReal·Oct 24

Finally second omarchy PC, going up! 👀 Now to see if my auto installer for @mullvadnet & @netbird works fully offline too! 😁 Kitchen reveal #Arcblock 🤣🚀 The installer also takes, new key for Netbird and ollama gets prompted by me, but packages of netbird, firedragon and mullvad gets taken also cache for firedragon browser. And the keys also gets encrypted. Which type of device will I setup next? A phone, another laptop maybe or a server. 🤔💭

Post attachment
NetBird avatar
NetBird@netbird·Oct 22

All the cool people have home servers nowadays. You don’t? It’s way easier than you might think to start! You can just use an old desktop tower if you have one, or get a low-power mini PC like the ZimaBoard 2. 8 GB of RAM and an SSD will definitely cover a light setup to run things like Home Assistant, DNS filtering, network monitoring, or a password manager with Docker. If you plan on Proxmox with 2 or 3 VMs plus containers, 16 GB is the minimum, ideally 32 to give you more room to grow. It’s best to start with a few services you actually need though, then grow from there! You’re going to get a lot more value out of your homelab if you can access it outside of your own network. Most homelab guides will send you to port forwarding tutorial and a dynamic DNS service. Don’t do that. You can setup an overlay network that allows your devices to connect directly to each other without exposing your home ports to the wide open internet. More in this guide: netbird.io/knowledge-hub/hom…

Post attachment