teleporter doesn't save all settings

[PA3DSS]

Versions

Pi-hole version is v5.3.1 (Latest: v5.3.1)
AdminLTE version is v5.5.1 (Latest: v5.5.1)
FTL version is v5.8.1 (Latest: v5.8.1)

Platform

Raspberry pi with Buster include all updates.

It is not really a bug but teleporter doesn't save these 2 settings i noticed

[yubiuser]

Actually, all these options are exported but not imported by teleporter. The options are saved to /etc/pihole/setupVars.conf which is included in the *.zip file. However, it is not restored on import.

I just wonder if the behavior should be changed, as Pi-hole so not going to use the information anymore:
pi-hole/FTL#1111
#4246

[dschaper]

If it's a bug that needs to be fixed then we should fix it and not wait until a later date where things may be different.

[yubiuser]

@DL6ER

You wrote the initial teleporter function (pi-hole/web#369). It already contained setupVars.conf, but only exported it, but never imported it. There was/is also no checkbox for it. Was there a reason behind it? Or was it simply forgotten?

[DL6ER]

setupVars.conf is/was intentionally not imported because an import of an exported teleporter file from a *different Pi-hole could have lead to severe issues due to the incorrect IPV{4,6}_ADDR. Now that the IP address is gone, we could add importing setupVars.conf.

Pi-hole v6.0 is going to make a lot of things different, including not using setupVars.conf for the web interface. However, for the time being, importing setupVars.conf should be safe.

[ramdyne]

I am sure the devs know this, but for users like me: things like DHCP server settings are not restored. This is preventing me from migrating my current install to a different setup which is really a bummer.

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/teleporter-doesnt-backup-basic-dhcp-settings/53885/3

[yubiuser]

If you used static DHCP assignments for your devices you should find "04-pihole-static-dhcp.conf in your teleporter backup archive. Just copy this to /etc/dnsmasq.d/

[unikitty37]

Sorry, I deleted the original comment because it felt a fair bit too ranty.

The static DHCP assignments were copied across — I could see them in the UI. But DNS lookups were failing. I hadn't manually copied setupVars.conf, which would have helped with the missing DHCP settings, but I can't really see anything in there that would have broken the DNS.

When I've got time to restart the Pi-hole, I'll try manually copying that across and seeing if it fixes it.

[unikitty37]

Copying setupVars.conf across sort of fixed it, but DNS entries only showed for entries in the new server's lease table; most devices weren't resolvable until their leases expired or were force-renewed, meaning DNS was wonky for 24 hours.

I'm guessing the leases aren't stored in a file that can be simply copied across easily, though. Would definitely prefer it if static DHCP leases could be put into DNS without having had to see the device first, but that's for another ticket…

[yubiuser]

A meantioned above Pi-hole v6 will handle Teleporter via FTL. It does export/restore DNSSEC and theme settings/boxed layout

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/teleporter-import-fails/63640/3