A German ISP also has an IP6 issue and confirmed it over the phone but is not fixing it.
It persists for years and can be observed on multiple households I checked.
Most don't notice it, as refreshing the address or happyeyeballs works around it.
It's seriously infuriating receiving these "Critical vulnerability reports" customers let other agencies do, and having to justify why you have no Referer-Policy header.
Nice to read that you are reasonable.
Also, they want a strict CSP while serving 10 different ad networks :)
You can write a network device driver, which exports the network packages into JavaScript. The author already wrote a console device. So, not much of a deal.
Doable for http and https, but if you're running it in a browser environment, you'll eventually run into issues with CORS and other protocols. To get around this you need a proxy server running elsewhere that exposes the lower layers of the network stack.
They allow netbooting to a recovery OS from which the disks can be provisioned via an ssh session too, for custom setups.
Likely there are cases that require the remote "keyboard", but I wanted to mention that.
But in practice they usually rely on attestation by an approved vendor, and the vendor won't let you control your private key, so they'll leverage it for lock-in.