/etc/pihole/pihole-FTL.conf can be customized to set values used at FTL startup.
It makes sense to export it to be saved.
I think all those files should be exported/teleported for settings backup or moving to another device:
/etc/pihole/whitelist.txt
/etc/pihole/black.list
/etc/pihole/blacklist.txt
/etc/pihole/regex.list
/etc/pihole/adlists.list
/etc/pihole/dhcp.leases
/etc/pihole/pihole-FTL.conf
/etc/pihole/setupVars.conf
DL6ER
May 12, 2020, 6:42pm
3
This feature request will be implemented by
pi-hole:devel
← pi-hole:fix/teleporter
opened 06:39PM - 12 May 20 UTC
**By submitting this pull request, I confirm the following:**
- [X] I have r… ead and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template.
- [X] I have made only one major change in my proposed changes.
- [X] I have commented my proposed changes within the code.
- [X] I have tested my proposed changes, and have included unit tests where possible.
- [X] I am willing to help maintain this change if there are issues with it later.
- [X] I give this submission freely and claim no ownership.
- [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
- [X] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
---
Even our extensive beta phase didn't reveal a few issues with Teleporter. They will be fixed in this PR. Changes:
- Add export & import for missing tables: `group`, `client` + the group linking tables.
- Rename Teleporter Ex-/Import to Backup and Restore to highlight that they are meant for being done on one and the same device rather than for transporting stuff between different installations (even when this is and will stay possible).
- Add pihole-FTL.conf ans custom.list (Local DNS Records) to Teleporter Backup
- Add import for Local DNS Records
- Improve arrangement of check boxes in the Teleporter Import box
- Log number of imported group assignments