mythtv-setup won't allow some addresses to be selected

[Bill Meek <keemllib@…>]

0a40fff4d7c2d1f1b07eb1f0524a89b06e1270a7 adds combo boxes to mythtv-setup for Backend Server IP settings.

This code presents the user with a list of IPv{4|6} addresses that match the following conditions:

1. The address is already in Backend ServerIP[6]
2. They are Loopback addresses
3. They are Link-Local addresses
4. Backend ServerIP[6] is empty

If a user has (for example) Backend ServerIP set to 127.0.0.1 and their NIC has that Localhost address and 192.168.1.123, the Private Network address won't be displayed and can't be added.

The same applies to IPv6 addresses that aren't in Backend Server IP6, Localhost or Link-Local.

The comment in the existing source:

"restrict autoconfiguration to RFC1918 private networks"

no longer applies with this patch and was removed!

For IPv6, Unique Local Addresses are allowed, but not other globally routable addresses e.g. 2001:db8:...

0.27-pre2 workarounds. Use before starting mythtv-setup:

IPv4:

UPDATE settings SET data = '' WHERE value = 'BackendServerIP'
    AND hostname = '<yourBEhost>' LIMIT 1;

IPv6:

UPDATE settings SET data = '' WHERE value = 'BackendServerIP6'
    AND hostname = '<yourBEhost>' LIMIT 1;

[Bill Meek <keemllib@…>]

v0.27-pre2-598-g37827bc-dirty, with this patch

[Raymond Wagner]

The issue with the combo boxes in 0a40fffd47c2d1f1b07eb1f0524a89b06e1270a7 is known, and is the result of StuartM not understanding the purpose of that DefaultListen? variable when adding them. However, the solution is not to change the contents of that variable, but to add a new variable containing the full list of available addresses.

The planned solution is to remove the single-address limitation, and replace the combo boxes with a multi-select box, which lists all available addresses on the system, highlighting those currently enabled for use. This will coincide with the IP address lookup being moved from direct database queries to protocol queries to the master backend, along with applications registering their listen address during connection to the backend, as well as the ability to rescan the available addresses at times other than initial startup. Ideally, this would all be managed from the master backend and the new web UI, rather than reworking mythtv-setup, but it is likely that will not be ready for 0.27.

I will keep the use of IPv6 ULA addresses in mind as an analog to the RFC1918 private network addresses when I rework this.