DP has an option to transmit HDMI signals instead, this is what passive adapters use and will still have the same HDMI 2.0 issue. A DP source can be passively adapted to HDMI, but a HDMI source cannot be passively adapted to DP.
You can also get active HDMI adapters which actively convert the signal, and can work with HDMI 2.1. Intel actually has an active converter chip built into their ARC GPUs, and is how they get around this issue.
Yep, but it’s required, and also present in every frame sent between your router and the ISP BNG.
I was trying to think of a reason why ASUS would still be showing.
I’m also interested in IPv6 related things and Apalrd’s adventures on YouTube has some cool videos on translation mechanisms and stuff. I thought you might be interested.
he was referring to historical data
DHCP can also send a hostname, so it’s possible your ASUS router previously sent its hostname, and then the Pi doesn’t send one. What ever software they use might not clear the old hostname when there isn’t one.
Edit: For example, this is what my current ISP lets me see:
If you just want an IPv6 prefix and don’t need the encryption a VPN provides, you can use an IPv6 broker. Hurricane Electric’s broker is a popular one.
That’s the OPs reply, not the AI.
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.
It’s even weirder than just an NZ company too:
While MetraWeather is the official supplier of lightning data to the BOM, it is a US weather company called AccuWeather that owns and maintains the Australian Lightning Network.
Also I haven’t heard great things about those “relatively cheap” AS3935 sensors, and personally haven’t had much luck using one with ESP Home.
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.
keyring lets you set backends with environment variables, I believe you can try PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring which is the simplest backend as it doesn’t save anything.
Edit: You can also try keyrings.alt as it has an insecure file backend, if you absolutely need password saving.
Fun fact: there actually is an IP version 5, and the reason we went from v4 to v6.
Fair enough. It seems like vibrant visuals is possible with GPU spoofing, but I haven’t tried it.
You can also play the Android release fine with Waydroid.
It doesn’t really matter how you setup dynamic DNS and SSL. I prefer to handle dynamic DNS on the router, incase it’s smart enough to refresh the IP after DHCP renews it. I do SSL on a seperate nginx instance, but I run a few other sites; it might be easier to configure it directly on home assistant, but I haven’t tried.
If you want some extra security, I’d look into mTLS, as that establishes some cert based authentication at the TLS layer before HTTP, but it can be complicated to configure.