#bgp

6 posts · Last used 24d

Back to Timeline
@Larvitz@burningboard.net · Apr 03, 2026
Successful surgery on my BGP core for AS201379 done. Got a third edge-router online, reorganized local-preferences and optimizing packet flows for efficiency and cost. Monitoring with Grafana is perfectly fine. RIPE Atlas measurement looks amazing for central Europe 🙂 Great connectivity for my 2a06:9801:1c::/48 Looking Glass: https://lg.hofstede.it Peering information: https://hofstede.it/as201379.html #networking #bgp #ipv6 #freebsd #frr #ripe
8
0
2
@zooper@mstdn.kernel-panic.lol · Mar 27, 2026
I've been mentioning my little hobby project Netpulse a few times, so I wrote a blog post about it now. https://as215855.net/posts/building-netpulse #homelab #ipv6 #networking #bgp
4
0
0
@Larvitz__dup_34529@burningboard.net · Mar 17, 2026
Put some information about my Autonomous System, connectivity and peering policy on my website: https://hofstede.it/as201379.html #internetrouting #networking #routing #bgp #sovereignty #freebsd
0
0
0
@Larvitz__dup_34529@burningboard.net · Feb 26, 2026

I just published a new guide on evolving a single BGP router into a multi-homed, two-PoP network using FreeBSD, FRR, and PF.

  • Native peering on Vultr + 3 GRE transits
  • Tying it together with iBGP
  • Why stateful firewalls break asymmetric transit (and how to fix it)

All for ~€18/mo.

Read it here: https://blog.hofstede.it/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/

#FreeBSD #BGP #IPv6 #Networking #Sysadmin #FRR #Homelab

0
0
0
@Larvitz__dup_34529@burningboard.net · Feb 25, 2026

Got my AS201379 (2a06:9801:1c::/48) well connected to European networks. RIPE Atlas measurements are pretty satisfying now 🙂

My website (hofstede.it / blog.hofstede.it) is reachable in <10ms from most of Europe via my own address space.

  • 4 Upstream providers
  • Two BGP routers
  • Stable for > 48hrs and reasonable ingress and egress paths 🙂

Very, VERY pleased with the result!

Next stop: Own NAT64 setup 🙂

Big thanks to @UnderEu@mas.to , @tschaefer@ipv6.social and @Hypopheralcus@det.social for giving me the Atlas credits for Measurements! Highly appreciated!

#ipv6 #networking #it #ripe #bgp

0
0
0
@fell@ma.fellr.net · Feb 11, 2026
Since this year I have massive trouble accessing anything hosted on AWS during the evening hours like these. My ISP is Deutsche Telekom AG (AS3320) and it looks like the only route to AWS (AS16509) leads through Cogent (AS174). MTR is showing more than 30% packet loss through Cogent to an AWS target. I know peering between DTAG and Cogent has been historically bad, but I never noticed issues until now. What happened? Do any BGP nerds know more? #BGP #Routing #Internet #Backbone #AskFedi
0
0
0

You've seen all posts