True... however assuming it exports it to anything sane/readable you could likely bodge it into whatever format the next router wanted to import using sed/awk/perl/c [selection based on complexity of the bodge]. JSON seems to be the current darling and that is easy to process.That's great if the export actually includes the DHCP client data. Mine has an export also, but it appears to only export the router settings, and not the DHCP client data (at least no hint of that in the gui).Where a router is also the dhcp server, like most domestic networks there are some routers that allow the import / export of the configurations to a simple generic format as csv to aid the backup and migration to new routers. It’s important to have a backup and restore capability anyway. This would cover all of the other configs too, NATs, port forwards etc all of which would need to be addressed if you migrate router.
I just checked, I’ve got config import/export on mine, I didn’t even know.
In commercial environments dhcp is more likely to be on a server than a router, have failover capability, replication etc.
Still, unless there's a standard for exporting the DHCP client data, it seems unlikely to me that it would work between routers of different vendors, because what vendor wants to make it easy for their customers to switch brands?
Statistics: Posted by bjtheone — Tue May 21, 2024 6:24 pm