It's just a protocol to tunnel IPv6 within IPv4 datagrams. The "RD" stands for "Rapid Deployment" and it was meant to be a temporary solution that would go away when the edge was updated. I'm not sure why it's still around.
The assigned IPs are dynamic, and hosting from a residence is probably against the ToS. I've never checked to see if any ports are blocked, but I know that UDP 51820 (Wireguard) is open.
At least the Vegas place has IPv6 provided by the same ISP. I've got another place in greater Los Angeles with Frontier fiber. It costs more money for half the bandwidth, and they have NO IPv6 support, or any plans for IPv6 support. For that location, I use an HE IPv6 (RFC4312) tunnel, which generally works fine, except many websites such as YouTube require authentication before they provide content. They're probably countering the AI training bots, and have flagged the HE IPv6 blocks.
The assigned IPs are dynamic, and hosting from a residence is probably against the ToS. I've never checked to see if any ports are blocked, but I know that UDP 51820 (Wireguard) is open.
At least the Vegas place has IPv6 provided by the same ISP. I've got another place in greater Los Angeles with Frontier fiber. It costs more money for half the bandwidth, and they have NO IPv6 support, or any plans for IPv6 support. For that location, I use an HE IPv6 (RFC4312) tunnel, which generally works fine, except many websites such as YouTube require authentication before they provide content. They're probably countering the AI training bots, and have flagged the HE IPv6 blocks.