Elektrine
Log in Register

#routing

9 posts · Last used 15d

Back to Timeline
Larvitz
Larvitz :fedora: @Larvitz@burningboard.net · Jul 30, 2026
I really don’t need any more peers for my AS201379! (Okay, maybe a few more...) Started back in December 2025, and now this "little" infrastructure is running: 14 individual eBGP sessions 3 Internet Exchanges Multiple transit providers 110+ direct peers All 100% IPv6 (2a06:9801:1c::/48) because legacy IP belongs in the last century. Powered entirely by FreeBSD :freebsd: 4 routers on 15.1-RELEASE running FRR and PF. #BGP #IPv6 #FreeBSD #Routing #Networking #sysadmin
17
4
8
jti42
JTI @jti42@infosec.exchange · Jul 28, 2026
Looks like Flatpak discovery will move from one mostly generally accepted hub to a gazillion of repos since the performative LLM complaints have befallen the possible single hub. (Partially half-understandable arguments, partially performative fluff for my taste) Which is ok as it triggers competition that might lead to better outcomes. (bazaar vs cathedral and all, rite? 😏 ) And removes a possible single point of failure. Now what I'd like to see is an approach that does discovery of those repos and enables search across those repos without a single point of failure. As e.g. a single, centrally hosted index for repos to register to would be. Flatpak already uses a reverse-dns-namespace structure internally. Anything that would leverage that? Wouldn't help with enumeration though. Something something DHT/Gossip/...? (as the cool thing from the past) Clearly a problem that will arise with more of the expectable decentralized systems that need uniform discovery and search. What's the Fedis wisdom on current academic approaches that might be interesting around this? Or bastardized routing tech, yet another idea on how to twist DNS into a pretzel, etc? Dare I say: Blockchain (as the unpopular thing before the LLMs 🤣 ) Throw you best Arxiv posts etc. at me. I'm just curious about the state-of-the-art techn for now, all smirk and sarcasm aside. #discovery #search #decentralized #routing #dns #fedimeta #flathub #dht #cooltechfromthepast #llm #selfhosting #fossdrama #spof #singlepointoffailure
3
0
2
mlundblad
Marcus Lundblad @mlundblad@fosstodon.org · Jul 09, 2026
I dusted off an old idea to show duration for walking segments of public transit itineraries that I played with a year or so back. Now that the list is using flowboxes, which can wrap contents to multiple lines when needed I think it will probably look better: #gnomemaps #PublicTransport #PublicTransit #transitous #routing #Gnome
65
4
10
meshy
Meshy @meshy@mstdn.social · Jul 02, 2026
🎉 #Meshy 26.07 is out: https://codeberg.org/sesivany/meshy/releases/tag/26.07 The release brings lots of fixes and improvements, but the biggest feature is smart routing. Currently, you have to enable it in the contact details for each contact, but it's definitely worth trying out. You can find out exactly how it works in the new user docs: https://meshy-app.org/docs/guide/contacts/#routing #meshcore
0
0
0
Larvitz__dup_34529
Larvitz :fedora: :redhat: @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
fell
Fell 🚄 SIGGRAPH @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
1
1
5
stefano
Stefano Marinelli @stefano@mastodon.bsd.cafe · Feb 06, 2026
Nice. My FTTC provider (Fastweb) is having some routing problems, so reaching the BSD Cafe is...slow. One small change in my router settings and switching to the other provider. #Routing
5
0
0

You've seen all posts