atyvr
Joined 3 years ago
Karma
253
Submissions
26
Member since
Jun 27
Recent submissions
Comment · 1 year ago
Comment · 2 years ago
what routers run on JAR files?
Comment · 2 years ago
Outages are inevitable, but the Rogers outage in 2022 had some devastating consequences.
Route leaks can happen to anyone, but the fact that it brought down their entire network, including voice and internet services, across all provinces, was unacceptable.
What's even more concerning is that they had no out-of-band access, which meant no management access to their network. This explains why the outage lasted a whopping 24 hours.
In my opinion, the lack of OOB was the most critical and yet the most preventable. Proper OOB is a must; I wouldn't operate a network without it, I don't understand why Rogers thought that was acceptable.
Comment · 2 years ago
Thanks for the suggestion. I added this method using Go's packetConn, and its WriteBatch() function, which appears to be using sendmmsg()
https://github.com/atoonk/go-pktgen/blob/main/pktgen/packetC...
I want to try and add it to the af_inet_syscall.go method, but seems like a bit more work than I have time for now. I'm surprised it's already quite fast, even without it.
FYI Latest results in README (pkt_conn is the new one) https://github.com/atoonk/go-pktgen/blob/main/README.md
Comment · 2 years ago
Interesting, need to check that out. Is this available in the Go Standard library?
Comment · 2 years ago
I've had a great experience with Tailscale, but when it comes to databases, I lean towards Border0. What stands out for me is the seamless single sign-on access it offers to my database, eliminating the need for a traditional perimeter VPN and shared database credentials.
Another aspect I appreciate is the granular control it provides. With Border0, I can define specific database access levels, like Select, Delete, Insert, etc., which can be tailored based on various flexible policies, including SSO identity, IP addresses, or country-specific parameters. Also, the detailed query logs tied to each SSO identity are invaluable for accurate attribution and tracking.
We pair WireGuard-style tunnels with real-time identity (sso, device, group context) and protocol aware proxies for SSH, RDP, HTTP, psql, Mysql, mssql, ES, and Kubernetes. Our policy engine lets you write rules like “only the DBA group can run DELETEs in Prod” or “Support can exec into this pod,” and we log every query, command, or request, all tied back to the user and device.
Think of it as combining the modern VPN experience of Tailscale with the deep authZ and observability of Teleport. I call it VPN plus PAM. Would love your thoughts if you give it a look.
Quick 2-minute overview: https://www.youtube.com/watch?v=hU7QixSqnSM&t=3s
https://www.border0.com/