atyvr

Really thoughtful take. That exact gap: bridging identity-aware tunneling (like WireGuard) with protocol-aware proxy decisions is exactly what we set out to solve with Border0.

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/

what routers run on JAR files?

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.

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

Interesting, need to check that out. Is this available in the Go Standard library?

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.

ARIN’s free pool of IPv4 address space was depleted on 24 September 2015. As a result, we no longer can fulfill requests for IPv4 addresses unless you meet certain policy requirements that reserved blocks of IPv4 addresses for special cases. https://www.arin.net/resources/guide/ipv4/ ie. you have virtually no other option than to buy on the private market

i disagree. skuhn posted a link to some historical data https://auctions.ipv4.global/prior-sales

Based on data from the IPv4 brokerage ipv4.global, the cost of IPv4 addresses has seen a notable increase. In 2014, the price ranged from $6 to $24 per IP, depending on the size of the subnet. By 2021, this range had jumped to between $23 and $60 per IP. The fluctuation between the lowest and highest sales prices for each IPv4 address remained relatively stable until 2021, when we began to see more significant spikes.

The peak prices for IPv4 addresses in 2021 were observed in September and October. During these months, IP addresses allocated by RIPE NCC and ARIN fetched as much as $60 each. Specifically, a /24 block from RIPE NCC sold for $15,360, while ARIN's /22 and /23 blocks went for $61,440 and $30,720, respectively.

Fast forward to October 2022, and the highest sale of the year was recorded: IP addresses allocated by ARIN sold for $60.70 each, or $15,540 for a complete /24 block. Despite these peaks, the IPv4 market appears to have reached a more stable pricing structure, especially when compared to the more volatile price shifts seen in 2021.

You'll need to become a member of one of the regional Internet route registries, like RIPE or ARIN. Then you can buy, say a /24, and transfer it into your RIPE/ARIN account. Now you have your own IPv4 range. And you can start for example start to use it for your own servers. To do so you need to "announce" this new /24 to the internet, using a protocol known as BGP. You can do that yourself, using a router, assuming you have an Autonomous system number (AS). You can get these via RIPE or ARIN as well. Or rely on your hosting provider to do that. For example AWS support "bring your own IP address". In that case they will announce the ip prefix in BGP for you, and you can assign your ec2 instances public IP's out of your range. Equinix Metal, (previously Packet), also makes it easy to do this.

Yah, it certainly seems like maybe that was peak pricing. This write up has some more data on historical pricing https://www.ipxo.com/blog/ipv4-price-history/ I've also heard folks pay quite a bit over the average price for novelty IP addresses, so perhaps that skewed the data? I'd love to be able to buy 2.2.2.0/23 or my favorite 42.42.42.0/24

I thought this one is interesting too https://awsipv6.neveragain.de/

correct, direct url is https://toonk.io/aws-ipv4-estate-now-worth-4-5-billion/index... More interestingly, perhaps, is a forward look at how much new revenue AWS will generate once AWS starts charging ($44 per IP per year) as of 2024. I think it's not unlikely that AWS will generate a few hundred million to a billion in additional revenue with this new charge.

It's better to buy your own IPv4 addresses :) The price of single IPv4 address, is about the same as renting it for a year from AWS for $43.

Wow, $43 per year, that's not cheap! It's likely the price AWS pays to acquire a single new IP at the current market price.

Three years ago, they had about just over 100 Million IPv4 addresses, which at the estimated market price back then, would have been worth ~$2.5 billion worth of IPv4 addresses! https://toonk.io/aws-and-their-billions-in-ipv4-addresses/in...

AWS has been the most active buyer of IPv4 addresses over the last few years, so it's probably quite a bit more now. And in the AWS blog they mentioned "the cost to acquire a single public IPv4 address has risen more than 300% over the past 5 years. "

Should have bought some IPv4 in 2014 or so, would have been a great investment. Back then it was about $11 or so per IP.