Notices by Alex Haydock (alexhaydock@infosec.exchange)

Did you leave your Wii at the #EMF2024 Swap Shop?

If so, it's now hosting my blog:

https://blog.infected.systems/posts/2025-04-21-this-blog-is-hosted-on-a-nintendo-wii/

Huge credit to @jmcwhatever for the effort porting NetBSD to the Wii!

In retrospect, I definitely picked the wrong game to test this setup with :blobcatfacepalm:

On the plus side, the realism of Stray running at 4K has definitely been approved by committee.

#caturday

My assistant is honestly not being particularly helpful

#caturday

An #ageverification story in two parts

Off-grid mesh networking never looked so adorable

Having great fun with Meshtastic at #38c3

@libreleah This one hits fairly close to home as I only just retired my Pi 4 routing setup a few months ago. I didn’t dare try USB Ethernet though. It was all just VLANs and the single Ethernet port. Did very well routing VDSL for 4 years :blob_grinning_sweat:

@libreleah It does sound ideal for what I’m looking to build and is essentially what I had in mind already but I’m just surprised that it’s free. That’s definitely a good project for me to work on in the future then. Nice.

@libreleah Oh, it is! That sounds ideal, thank you!

@libreleah I’ll definitely have to check these out since I like the idea of having the redundant routes configured.

I’ve been trying to work out how I could fall back to 5G in a failure scenario without needing to face the problem that my /29 and /48 are bound to the hardwired connection, but I might have to investigate A&A’s L2TP for that…

@libreleah Glad to be of help! :ablobcatnod:

Big fan of the Libreboot project, by the way!

As promised, my post about building an IPv6-focused OpenBSD home router :puffer:

Featuring NAT64, DNS64, PREF64, all of the 64s!

https://blog.infected.systems/posts/2024-12-07-building-an-ipv6-focused-openbsd-home-router/

#openbsd #ipv6

@dalias Definitely sounds much nicer from a security perspective.

What would be a 'trusted upstream' in your mind though? Sounds like it'd be a real challenge for a project to select their upstream without any controversy. I remember a fair bit of it when Mozilla partnered with Cloudflare to provide DoH.

If you've deployed an IPv6-only or IPv6-mostly network and you're having issues with Apple devices 'forgetting' they have DNS servers after they've been in sleep mode, I described the bug and some workarounds in this post since I haven't seen anyone else do it yet:

https://blog.infected.systems/posts/2024-12-18-working-around-macos-and-ios-rdnss-expiry-bug/

#ipv6 #ipv6only

Connecting to Tor from IPv6-only clients 🧅

https://blog.infected.systems/posts/2024-12-05-connecting-to-tor-from-ipv6-only-clients/

(Yes I'm still going with the #IPv6 thing. Don't worry, I'll get to IoT devices next...)

I took @nixCraft's 'No NAT November' challenge and switched my network to IPv6-only! :blobcat_thisisfine:

New blog post: No NAT November - My Month Without IPv4

https://blog.infected.systems/posts/2024-12-01-no-nat-november/

#ipv6

@aral @x_cli @apicultor @briankrebs @Mer__edith

It's marked as unofficial quite clearly on Flathub but this is a confusion point I've seen before with store fronts like GNOME Software & co, which don't pass through that clear visual to the end-user.

I definitely echo the suggestion though. It would be good if Signal would officially take over the Flatpak maintenance. It would help make Signal more (officially) accessible on distros other than Debian/Ubuntu.