Gateways connected to V2 endpoints will keep forwarding traffic to V3 networks through Packet Broker for some time after V2 shutdown, so they won’t go offline on December 1st.
There are several reasons why we won’t just create CNAMEs, here are some of them:
- The current solution with “legacy infrastructure” that forwards traffic to Packet Broker works fine.
- It’s actually a good thing for people to upgrade the firmware of their gateways while they’re re-configuring them. And if you don’t have secure remote access, you should set that up anyway.
- Not everyone wants to migrate their gateway to
eu1.cloud.thethings.network. If we keep these gateways on the “legacy infrastructure” it’s easier to migrate to the network of their choice instead of being forced ontoeu1.cloud.thethings.network. - V3 requires all gateways to be registered, whereas V2 (and the “legacy infrastructure” that forwards to Packet Broker) allows unregistered gateways, and we have quite a few of those. If we would just create a CNAME to V3, all those unregistered gateways would immediately disappear from the network, and we want to avoid that. We don’t have a final solution for these gateways yet, maybe we will eventually make the old DNS records point directly to Packet Broker.