I'm glad it isn't, @mattgrayyes@chaos.social
Remote
Wouter 🛰️
@pa3weg@mastodon.social
mastodon 4.8.0-nightly.2026-10-06Professional satellite builder 🛰️
Radio amateur - callsign PA3WEG📡
Sound engineer 🎶
Videographer 🎥
allround electronics nutter⚡️.
Weirdly motivational
He/Him
0 Followers
0 Following
16 Posts
Joined October 28, 2022
Website:
Pixelfed:
PeerTube:
Achievement unlocked: finally implemented a corporate IPv6 network
long overdue, but so many hurdles to take!
RE: @arstechnica@mastodon.social
I'd say "not interested" is not strong enough, "Actively against" is better
Fuck those US killing machines, get the fuck off our roads!
It's going to be really weird when everyone is going to get to know #Nextcloud from their workplace, while I've been running it since it's inception/fork and OwnCloud before that.
What a journey. I am still on the same install that has survived all the migrations, the fork, and updates since 2012!
Replying to
Read the post, and the caveats. Just released, proof of concept etc.
No warranties (which we would void any way)
Replying to
@jon@social.vivaldi.net @Vivaldi@social.vivaldi.net I've been with you a few years now and haven't looked back a single time. Okay, maybe one time. to FireFox.
Promoting the hell out of Vivaldi. I might need to get myself some stickers
THANK YOU
Replying to
Replying to
@hpr@infosec.exchange @ken_fallon@mastodon.sdf.org @angrynerdspodcast@mastodon.nl @tdose@fosstodon.org it was great to have you at the table, Ken!
Amazing to see the statistics of HPR, and the dedication to keep it all running smoothly.
Replying to
@goetz@ipv6.social that's correct, the ISP takes care of the redundancy and terminates a BGP session, and presents me with two physical connections and a virtual IP between those two (VRRP)
This is the same on v4
My backup WAN does not provide IPv6 yet, so I haven't looked at multi-wan for that
Replying to
@goetz@ipv6.social my implementation uses two redundant firewalls with high availability and virtual IPs for the WAN side. Getting this to work was a challenge because the ISP ended up misconfiguring their next hop and I spent quite some time "learning" about IPv6 from trying to get a link to work that was misconfigured upstream. This is my first time doing it so everything could have been wrong. It took quite some effort to explain my issues to the ISP not always using the right vocabulary
Replying to
@goetz@ipv6.social Some of the lessons might be obvious to some:
- Don't assume your ISPs implementation is functional - I had to diagnose the WAN link with them.
- Virtual IPs for redundancy run on link local IPs even if the bonded interfaces do not (fe80:...)
- Every VLAN needs a separate link local address
- SLAAC takes the interface prefix unless configured otherwise
- Run a test network in IPv6 only so there's no fallback to IPv4 and failure is immediately obvious
- Turn VPNs OFF!
Replying to
@Dany @bert_hubert Ik moest vanochtend al lachen, het is een goeie ja! Net nog maar een keer geluisterd