Full Node with StarLink ISP and CGNAT Issues

I'm trying to set up a full node on my RPi 5 NMVe, but I'm a bit worried about incoming connections since I'm using StarLink. They run CGNAT on their home plans and don’t give out a public IPv4 address. They do provide static IPv6 addresses though. So, if I set up my RPi 5 (Bookworm 12) to handle both IPv4 and IPv6, will Bitcoin Core default to using the IPv6 address? I can tweak my router for IPv6 and open the necessary ports, which should keep things stable. But that public IPv4 address isn’t reliable. If I get TOR running, will that help with the inbound connection issues?

TOR will allow you to have inbound connections without doing any network adjustments. It is important to clarify the difference between an incoming and an outgoing connection though. An incoming connection doesn't mean that you don't receive anything from other nodes. It just means that the node that will initiate the connection process will always be yours. Once the connection between two nodes is established, it doesn't matter who initiated it or not. The transferring process will be the same. Finally, TOR is often slow. This is just a side-note.

It makes sense that hardly any residential provider is using static IP addresses anymore because the address space is getting exhausted. I would've suggested port forwarding to you but 1) that only works if the wider network supports static addresses and you're behind a dedicated router and 2) I don't know if starlink has such a configuration directive in the first place.

You don't have to use IPV4 at all, and you can just portforward and point Bitcoin Core at the IPV6 address. Tor will also solve the problem with inbound connections without any issues, you just need an additional network layer ontop of the IPV4 that you have.

Since you're shitposting on the tech boards, I feel the need to point out you're spewing BS.