Hype for the Future 149D: Central Rutherford County, North Carolina

Introduction Much of the County of Rutherford in the State of North Carolina is identified as an urban cluster at town size, combining the communities of Rutherfordton, Ruth, Forest City, and Spindale. Today, each municipality is associated with the heritage of the entire county, with distinct perspectives within each individual community and beyond. Travel Rutherford County, North Carolina, is associated with United States Routes 64, 74, 74A, 74 Business, 221, and 221A; and North Carolina […]

https://novatopflex.wordpress.com/2026/03/29/hype-for-the-future-149d-central-rutherford-county-north-carolina/

Hype for the Future 149D: Central Rutherford County, North Carolina

Introduction Much of the County of Rutherford in the State of North Carolina is identified as an urban cluster at town size, combining the communities of Rutherfordton, Ruth, Forest City, and Spind…

novaTopFlex

Hype for the Future 148G: City of Enid, Oklahoma

Introduction The City of Enid is a community in and the county seat of Garfield County in north-central Oklahoma. Today, the community is accessible from United States Highways 64, 81, and 412, depending on the direction of travel. Amenities Within the City of Enid, the community is home to the Cherokee Strip Regional Heritage Center, the Glidewell Pioneer Homestead, the East Maine “Shark Bridge,” Simpson’s Old Time Museum, the Klemme Gallery and Event Space, the Railroad Museum of […]

https://novatopflex.wordpress.com/2026/03/28/hype-for-the-future-148g-city-of-enid-oklahoma/

Hype for the Future 148G: City of Enid, Oklahoma

Introduction The City of Enid is a community in and the county seat of Garfield County in north-central Oklahoma. Today, the community is accessible from United States Highways 64, 81, and 412, dep…

novaTopFlex

My ISP upgraded my fiber connection. On the + side it's supposed to be 10Gbit/s (which I cannot really test, I only have a single machine capable of more than 1GBit/s).

The new router is dumb, doesn't support IPv6 and the DHCP implementation is crap (cannot override default DNS servers)

For the IPv6 issue, I recently set up a tunnel using Route64, and it’s working very nicely. Hopefully I got the fire-walling rules right and did not expose my entire network to the internet.

#IPV6 #route64

Looking for a sponsoring LIR for my ASN.
I run a small non‑commercial network with a WireGuard uplink via Route64 and plan a second upstream (HE POP) for redundancy and BGP/IPv6 learning.
I can maintain IRR/RPKI. Any LIR willing to sponsor an ASN is welcome.

#BGP #ASN #IPv6 #Multihoming #HomeLab #NetOps #NetworkEngineering #RIPE #LIR #NOG #PLNOG #DENOG #NLNOG #UKNOF #Routing #Sysadmin #Route64 #HurricaneElectric

My latest blog post is talking about how I have configured a #tunnelbroker on my #mikrotik thanks to #route64
Now I'm a happy owner of a #ipv6 subnet

#networking #homelab #selfhosted #wireguard #vpn #cgnat

https://www.schwitzd.me/posts/mikrotik-tunnelbroker-with-route64/

Mikrotik - Tunnelbroker with Route64

For learning purposes, I started looking into IPv6. First, I enabled a Unique local address subnet to leverage K3s dual-stack on my Home Cluster. Then I thought it would be cool to be able to connect to my home from abroad, so I started investigating VPNs. It is at this point that I discovered that my ISP currently is only offering IPv4 behind CGNAT for mobile devices (My Mikrotik connects to internet over LTE. Surfing the web I learned about tunnel broker is a service that provides IPv6 connectivity over an existing IPv4-only internet connection by encapsulating IPv6 traffic inside IPv4 packets.

Schwitzd
Is #route64 broken for anyone else? I get an 500 Internal Server Error when trying to create a tunnel.
Also, the ticket page shows an php error.

Quit my peering/transit with #route64 and shut the BGP session down - their ticket system appears to by dysfunc as well, haven't got a reply to my ticket in some says.

#bgp

#bgp #networking #route64
Uh, yes. Recreated the BGP session with "transit" only.
Now I actually only get the default route as requested.

I guess peering is for "hey, let me communicate with all route64 members"?

I think I chose the wrong option "peering" when creating a #BGP tunnel at #route64 ?
Should I have selected "transit" to get my route announced "outside"?
#bgp
#route64 confuses me. I need to create an AS set, but my AS set must not contain my peering partners?
Huh?
What's it there for, then?