Well, your router is trying, but your ISP isn’t replying, so I’d say you don’t have IPv6 yet.

I have had ISPs where if you send a bunch of DHCP solicits/discovers too quickly, then they stop replying. So maybe disable DHCPv6 for a few hours, and enable it while watching it on the packet sniffer, incase it sends a weird response.

Also it shouldn’t make any difference, but in IPv6/ND change all to bridge; your router looks like it’s advertising itself as a default route to your ISP’s router, and that just seems wrong.

I see is coming from a couple of Amcrest cameras

Oh yeah, that still seems to be from your LAN. On the Mikrotik set your WAN interface in the filters tab of the packet sniffer. Also if you haven’t already, your WAN shouldn’t be bridged with your LAN, since your router will route between them, a bridge is like a network switch.

Basically I’d like to see the Router Solicitation on your WAN from your Router, and hope that your ISP responds back with a Router Advertisement; or a Solicit for DHCPv6, and the whole exchange.

Also 2001:470:1f06:redacted looks like a Hurricane Electric IP.

Yeah thats normal, fe80:: is link local, ff02:: is broadcast. Is the source always your router’s address, or is there another addresses there? DHCPv6 and ICMPv6 (for SLAAC), are the important protocols there.

Your WAN shouldn’t be part of your bridge. Are you getting any traffic in Wireshark? You do also need to enable packet sniffer on the router and point it to the IP of the computer you’re running Wireshark on.

Ahh okay, could you at least see your router trying to request an IPv6? You might have to disconnect and reconnect the WAN while the packet capture is going.

It might be worth doing a packet capture on your WAN, you can stream it straight to wireshark’s udpdump, and look if there’s any sort of reply to DHCP or any RA broadcasts, you can just use ipv6 as a filter.

Also come to think of it, DHCPv6 is usually still used for your prefix so that should work regardless of SLAAC. SLAAC is often just used for your default routes and the router’s own IP (as allocating that from your prefix manually is often considered a misconfiguration).

Some ISPs use SLAAC instead of DHCPv6, maybe that’s the case for you? To enable it, you’ll need to run /ipv6/settings/set accept-router-advertisements=yes and reboot. The current RouterOS beta also lets you pick which interfaces to allow SLAAC on.

Funny thing, time.is uses Cloudflare, and I only found out because of the outage.

Yeah thats fair enough. The ACS override patch should still have better isolation and speed than anything else you can do without native ACS, the security implications are just it’s theoretically possible to intercept another PCIe device’s traffic through the NIC; you can read more here.

SR-IOV works by presenting one device as many, which you can passthrough one of those to your VM. Meaning SR-IOV only works through PCIe passthrough, so you’d have to figure that out first. The GPU guides should get you most of the way there.

Some distros include an ACS patch into their kernel (e.g. Proxmox, and I think CachyOS), which lets you passthrough devices without hardware support (but lacking some security features).

I believe it might be possible to ‘passthrough’ the VF from the host without PCIe passthrough (I’ve only done this with containers though), but performance is often worse than just using a bridge.

Fun fact: there actually is an IP version 5, and the reason we went from v4 to v6.

To prove your point even more, WannaCrypt has a platinum rating on WineHQ.

I’ve always wondered, why do we put the GPU drivers and their firmware into the initramfs? Can’t we just rely on the framebuffer drivers until the root partition is mounted? Since most of the firmware size is from GPUs, that should reduce initramfs size, and speed up booting as there’s less to load into memory.

The EMC2101 is a slightly modified clone of the LM63, so if you connect it to your board’s I2C bus and instantiate the lm63 driver to the right address, it should show up in lm-sensors like a normal PC fan. Or there’s userspace python drivers, if you don’t need a kernel hwmon interface or can’t get it to work.

They probably mean the QEMU guest tools. But you set it up once, and never touch it again.