Here is the setup:
- Computer running mythtbackend on ubuntu 20.10, dual stack (ipv6 and ipv4). DNS properly configured (A and AAAA records).
- Computer running mythfrontend on ubuntu 20.10, ipv4 only.
- Computer running mariadb 10.5 on debian 10, dual stack just like mythbackend.
All computers belong to same IPv4 subnet and same LAN, firewalls disabled. Backend and database belong to same IPv6 subnet too.
If I fire up mythfrontend, it does connect to database, retrieves FQDN of backend (masterIP and masterIP6 both contain backend's FQDN) and resolves it to IPv6, then it tries to connect to that IPv6 address and of course fails (as IPv6 is not configured in frontend). It retries several times, but it never uses ipv4.
Error shown (repeated several times) is:
2021-01-28 13:18:05.870 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 2001:XXXX55f::70:6543 (try 1 of 1)
2021-01-28 13:18:05.871 E MythSocket(7f5d4c006310:-1): Failed to connect to (2001:XXXX55f::70:6543) Network unreachable
2021-01-28 13:18:05.871 E Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
Tried in mythtv/31 and mythtv/32. Same result.
Of course, enabling IPv6 on frontend, or disabling IPv6 in backend (and correcting settings in database) solves this.
IPv4-only frontend cannot connect to dual-stack backend
Moderator: Forum Moderators
Re: IPv4-only frontend cannot connect to dual-stack backend
The workaround is to set the backend address to the ipv4 address via setup
Re: IPv4-only frontend cannot connect to dual-stack backend
Reading again my post, now it sounds quite rude. I'd like to apologize.