The Things Network V2 is Permanently Shutting Down (completed)

[arjanvanb (Arjan)]

@htdvisser

As @descartes already wrote, this is indeed temporary, so you will have to reconfigure your gateways.

When I finally migrated a Kerlink using the Semtech UDP protocol a week ago, basically all I did on that gateway was this from the documentation:

If you are using a Semtech UDP Packet Forwarder, change the server_address in your global_conf.json to eu1.cloud.thethings.network

This used to refer to router.eu.thethings.network. I’m sure it has been considered, so what would break if somewhere after December 1st any remaining V2 gateway would just be migrated from V2 Console to V3 Console, and that old domain name would just become an alias for the new one?

This has come up earlier, but I don’t think it was answered:

@Kater

I wonder if it would be possible to automatically switch V2 gateways to V3 (of course still using the old packet forwarder) by simply DNS-resolving the old hostname router.eu.thethings.network to the new eu1.cloud.thethings.network (and similar for other regions)? If the V2 world is shut down anyway After the V2 world is shut down anyway, the host entry is no longer used, isn’t it?