I expect that once the infrastructure is in place then it will be co-opted by governments to enforce their control over the digital domain.

You keep the hash of the request so that you can reject a subsequent request with a different body. This has helped me surface bugs and data issues in other systems.

Do you support multi-pathing, for example, connecting using both ipv4 and ipv6?

That's a tricky one. Sort of - we just didn't have enough reason to implement it (nor IPv6 but this is a low lift, and we can get it done quickly).

We do suport VPD 0x83 and advertise consistent NAA/WWID, so linux will support multiple iscsiadm sessions to the same device, and it will be stitched across sessions as paths to the same disk.

We currently hardcode MC/S to 1 as part of login negotiations, advertise single portal and dropping a path will require a re-login.

So - theoretically yes, you can support multipath and it won't fall on its face, but without any practical benefits of it (no bandwidth aggregation and no failover - no ALUA) - at this point it's a single boring target.

But the underlying plumbing can support it - if you have a real usecase for it.

What's really insane is 40G - nobody wants it so you can buy kit for next to nothing. I got a 72×QSFP Cisco Nexus (with EVPN & VXLAN) for £50 inc P&P.

Old, hot and loud.

Industry went for 25G and 40G gear is long EoS and EoL.

I got an 8 port SFP+ managed switch from AliExpress for $100!

This is the correct answer.

Something that confused me for a while was the path "docker.io" used for pulling containers. There is not actually a container registry at "docker.io" - rather docker and podman are hard coded to convert it to either "registry-1.docker.io" or "index.docker.io".

Have you considered Unified Attestation [1] which is an alternative to Google's?

[1] https://uattest.net/

That just puts the power to allow/ban rooting and operating systems in the hands of a different set of companies. Its still unacceptable.

Oh dang, this is exactly what I've been looking for. Thank you.

Since you mentioned 4.4mm, thought I would chime in and mention pentaconn (the trade name) which is a TRRRS connection (which does include a ground connection as well as L+/L-/R+/R-. I still do not understand the purpose of the ground connection in these plugs since there's nothing to ground on the other end.

Isn’t it the only common variant of 4.4mm? Since portable balanced audio is audiophile-adjacent, no wonder it includes the common ground of dubious utility.

These are nice, but there is a risk if multiple units are plugged into an extension strip with a cord that is not large enough for the current.

Thanks for sharing! I am happy to see open-source BNG projects taking off in the last few months. These are a couple of others to look at:-

https://github.com/codelaboratoryltd/bng-edge-infra

https://github.com/veesix-networks/osvbng

I reached out to the maintainer of osvbng, and he was really receptive about it. I may contribute to the project in a few months.

Meanwhile, I also found another project that works with eBPF-accelerated BNGs for k8s edge deployments. https://github.com/codelaboratoryltd/bng (BUSL-1.1 license though)

Thank you for listing me the projects. Really helped me out!!

That is awesome! I was walking almost blind folded here, making decisions based on observations, intuition, some blogs, and RFC. These projects give me something to look against as I further develop my skills.