Mailing List Archive

On Mon, 14 Jun 2021 14:40:36 -0500, you wrote:

>A few weeks ago I successfully migrated a MythTV 31 backend to a new PC.
>Recently I noticed the backend was set up to listen on all interfaces so
>I thought I'd reconfigure it to listen on just the PC's primary IP,
>192.168.4.7. It didn't go very well:
>
>1. Stop mythbackend
>2. Launch mythtv-setup
>3. General.
>4. Host Address Backend Setup
>5. Uncheck Listen on All IP Addresses
>6. Select Primary IP Address/DNS Name
>7. The only IP listed was 192.168.1.5 which was an old IP for the old
>PC. The old PC's IP was 192.168.4.5 at the time I took the database
>backup which I imported into the new backend's database. None of the new
>PC's IPs--192.168.4.7 or 127.0.0.1--were listed.
>8. Select New Entry and enter 192.168.4.7.
>9. Exit Settings / Save and Exit
>10. Redo steps 4 - 7. The Primary IP is still 192.168.1.5.
>
>I ended up going back to Listen on All IP Addresses. This lets me
>connect on 192.168.4.7 OK. I'd just like to turn off listening on the
>other IPs.
>
>Is this a bug or might I have migrated a stale database entry with the
>old 192.168.1.5 IP? Any way to get this straightened out?
>
>Thanks,
>Dave

Check your settings in the database - what does this query show?

sudo mysql
use mythconverg;
select * from settings where data like '192.%';
quit

I get this:

MariaDB [mythconverg]> select * from settings where data like '10.%';
+-------------------+----------+----------+
| value | data | hostname |
+-------------------+----------+----------+
| MasterServerIP | 10.0.2.4 | NULL |
| BackendServerIP | 10.0.2.4 | mypvr |
| BackendServerAddr | 10.0.2.4 | mypvr |
+-------------------+----------+----------+
3 rows in set (0.002 sec)

but I believe BackendServerIP is historical and no longer used.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

MariaDB [mythconverg]> select * from settings where data like '192.168.%';
+-------------------+-------------+----------------+
| value             | data        | hostname       |
+-------------------+-------------+----------------+
| BackendServerIP   | 192.168.1.5 | calvin.home.du |
| MasterServerIP    | 192.168.4.7 | NULL           |
| BackendServerAddr | 192.168.4.7 | calvin.home.du |
+-------------------+-------------+----------------+

BackendServerIP has the same 'data' value that is being used by
mythtv-frontend.

Dave


On 6/15/21 4:20 AM, Stephen Worthington wrote:
> On Mon, 14 Jun 2021 14:40:36 -0500, you wrote:
>
>> A few weeks ago I successfully migrated a MythTV 31 backend to a new PC.
>> Recently I noticed the backend was set up to listen on all interfaces so
>> I thought I'd reconfigure it to listen on just the PC's primary IP,
>> 192.168.4.7. It didn't go very well:
>>
>> 1. Stop mythbackend
>> 2. Launch mythtv-setup
>> 3. General.
>> 4. Host Address Backend Setup
>> 5. Uncheck Listen on All IP Addresses
>> 6. Select Primary IP Address/DNS Name
>> 7. The only IP listed was 192.168.1.5 which was an old IP for the old
>> PC. The old PC's IP was 192.168.4.5 at the time I took the database
>> backup which I imported into the new backend's database. None of the new
>> PC's IPs--192.168.4.7 or 127.0.0.1--were listed.
>> 8. Select New Entry and enter 192.168.4.7.
>> 9. Exit Settings / Save and Exit
>> 10. Redo steps 4 - 7. The Primary IP is still 192.168.1.5.
>>
>> I ended up going back to Listen on All IP Addresses. This lets me
>> connect on 192.168.4.7 OK. I'd just like to turn off listening on the
>> other IPs.
>>
>> Is this a bug or might I have migrated a stale database entry with the
>> old 192.168.1.5 IP? Any way to get this straightened out?
>>
>> Thanks,
>> Dave
> Check your settings in the database - what does this query show?
>
> sudo mysql
> use mythconverg;
> select * from settings where data like '192.%';
> quit
>
> I get this:
>
> MariaDB [mythconverg]> select * from settings where data like '10.%';
> +-------------------+----------+----------+
> | value | data | hostname |
> +-------------------+----------+----------+
> | MasterServerIP | 10.0.2.4 | NULL |
> | BackendServerIP | 10.0.2.4 | mypvr |
> | BackendServerAddr | 10.0.2.4 | mypvr |
> +-------------------+----------+----------+
> 3 rows in set (0.002 sec)
>
> but I believe BackendServerIP is historical and no longer used.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Deleting the value of BackendServerIP changes the issue. Now 127.0.0.1
is treated as the one-and-only Primary IP Address plus it is assigned to
a new instance of BackendServerIP:

1. Stop mythbackend
2. Launch mythtv-setup
3. General.
4. Host Address Backend Setup
5. Uncheck Listen on All IP Addresses
6. Select Primary IP Address/DNS Name
7. The only IP listed is 127.0.0.1.
8. Select New Entry and enter 192.168.4.7.
9. Exit Settings / Save and Exit
10. Redo steps 4 - 7. The Primary IP is still 127.0.0.1.

From the database:

MariaDB [mythconverg]> select * from settings where data like '127.0.0.1';
+-------------------+-----------+----------------+
| value             | data      | hostname       |
+-------------------+-----------+----------------+
| BackendServerIP   | 127.0.0.1 | calvin.home.du |
| MasterServerIP    | 127.0.0.1 | NULL           |
| BackendServerAddr | 127.0.0.1 | calvin.home.du |
+-------------------+-----------+----------------+

Dave


On 6/15/21 8:09 AM, Dave Ulrick wrote:
> MariaDB [mythconverg]> select * from settings where data like
> '192.168.%';
> +-------------------+-------------+----------------+
> | value             | data        | hostname       |
> +-------------------+-------------+----------------+
> | BackendServerIP   | 192.168.1.5 | calvin.home.du |
> | MasterServerIP    | 192.168.4.7 | NULL           |
> | BackendServerAddr | 192.168.4.7 | calvin.home.du |
> +-------------------+-------------+----------------+
>
> BackendServerIP has the same 'data' value that is being used by
> mythtv-frontend.
>
> Dave
>
>
> On 6/15/21 4:20 AM, Stephen Worthington wrote:
>> On Mon, 14 Jun 2021 14:40:36 -0500, you wrote:
>>
>>> A few weeks ago I successfully migrated a MythTV 31 backend to a new
>>> PC.
>>> Recently I noticed the backend was set up to listen on all
>>> interfaces so
>>> I thought I'd reconfigure it to listen on just the PC's primary IP,
>>> 192.168.4.7. It didn't go very well:
>>>
>>> 1. Stop mythbackend
>>> 2. Launch mythtv-setup
>>> 3. General.
>>> 4. Host Address Backend Setup
>>> 5. Uncheck Listen on All IP Addresses
>>> 6. Select Primary IP Address/DNS Name
>>> 7. The only IP listed was 192.168.1.5 which was an old IP for the old
>>> PC. The old PC's IP was 192.168.4.5 at the time I took the database
>>> backup which I imported into the new backend's database. None of the
>>> new
>>> PC's IPs--192.168.4.7 or 127.0.0.1--were listed.
>>> 8. Select New Entry and enter 192.168.4.7.
>>> 9. Exit Settings / Save and Exit
>>> 10. Redo steps 4 - 7. The Primary IP is still 192.168.1.5.
>>>
>>> I ended up going back to Listen on All IP Addresses. This lets me
>>> connect on 192.168.4.7 OK. I'd just like to turn off listening on the
>>> other IPs.
>>>
>>> Is this a bug or might I have migrated a stale database entry with the
>>> old 192.168.1.5 IP? Any way to get this straightened out?
>>>
>>> Thanks,
>>> Dave
>> Check your settings in the database - what does this query show?
>>
>> sudo mysql
>> use mythconverg;
>> select * from settings where data like '192.%';
>> quit
>>
>> I get this:
>>
>> MariaDB [mythconverg]> select * from settings where data like '10.%';
>> +-------------------+----------+----------+
>> | value             | data     | hostname |
>> +-------------------+----------+----------+
>> | MasterServerIP    | 10.0.2.4 | NULL     |
>> | BackendServerIP   | 10.0.2.4 | mypvr    |
>> | BackendServerAddr | 10.0.2.4 | mypvr    |
>> +-------------------+----------+----------+
>> 3 rows in set (0.002 sec)
>>
>> but I believe BackendServerIP is historical and no longer used.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Tue, 15 Jun 2021 08:17:26 -0500, you wrote:

Ignore the BackendServerIP setting - I checked in a new MythTV install
I have in a virtual machine and it is not present there, so that value
is historical and no longer used. The BackendServerAddr setting is
the current one.

>Deleting the value of BackendServerIP changes the issue. Now 127.0.0.1
>is treated as the one-and-only Primary IP Address plus it is assigned to
>a new instance of BackendServerIP:
>
>1. Stop mythbackend
>2. Launch mythtv-setup
>3. General.
>4. Host Address Backend Setup
>5. Uncheck Listen on All IP Addresses
>6. Select Primary IP Address/DNS Name
>7. The only IP listed is 127.0.0.1.

I am guessing that this is the problem. Mythtv-setup is not seeing
all the IP addresses in use on the PC for some reason, and is only
allowing you to set an IP address that it sees as being present. On
my backend, where I have two IPv4 addresses and two IPv6 addresses on
br0 (bridged eth0/tap0), it puts all those addresses in the drop down
list, along with 127.0.0.1 and ::1 and the IPv6 link-local addresses
and the address on my OpenVPN tun0 interface. If you are only getting
127.0.0.1, there must be something that is preventing mythtv-setup
from seeing the Ethernet interface - it is only seeing the lo
interface. So what does the "ifconfig" or "ip addr" command show? Do
all the expected IP addresses show up? Do you get different results
running those commands as user mythtv and root?

You could try manually changing the MasterServerIP and
BackendServerAddr entries directly in the database. But if
mythbackend then can also not see the Ethernet interface, it will not
work very well.

When the "Listen on All IP Addresses" option is on, mythbackend will
ignore the IP address settings and listen on both 0.0.0.0 and :: (for
an IPv6 enabled PC), or 0.0.0.0 only (for an IPv4 only PC). You can
see what it is listening on with this command:

netstat -anp | grep mythbackend | grep tcp

I am not sure if netstat will need to be run as root to see all the
connections - I always run it as root. This is what I get:

root@mypvr:~# netstat -anp | grep mythbackend | grep tcp
tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN
3276/mythbackend
tcp 0 0 0.0.0.0:6544 0.0.0.0:* LISTEN
3276/mythbackend
tcp 0 0 0.0.0.0:6549 0.0.0.0:* LISTEN
3276/mythbackend
tcp 0 0 0.0.0.0:6554 0.0.0.0:* LISTEN
3276/mythbackend
tcp 0 0 127.0.0.1:6543 127.0.0.1:44296
ESTABLISHED 3276/mythbackend
tcp 0 0 127.0.0.1:6543 127.0.0.1:44298
ESTABLISHED 3276/mythbackend
tcp 0 0 127.0.0.1:6543 127.0.0.1:41406
ESTABLISHED 3276/mythbackend
tcp 0 0 127.0.0.1:6543 127.0.0.1:41404
ESTABLISHED 3276/mythbackend
tcp 0 0 10.0.2.4:6543 10.0.2.4:49678 ESTABLISHED
3276/mythbackend
tcp6 0 0 :::6543 :::* LISTEN
3276/mythbackend
tcp6 0 0 :::6544 :::* LISTEN
3276/mythbackend
tcp6 0 0 :::6549 :::* LISTEN
3276/mythbackend
tcp6 0 0 :::6554 :::* LISTEN
3276/mythbackend

So mythbackend has four listening TCP ports on each of 0.0.0.0 and ::,
plus some established TCP connections.

Sorry about the line wrapping - my email client does not have a way of
turning that off.

>8. Select New Entry and enter 192.168.4.7.
>9. Exit Settings / Save and Exit
>10. Redo steps 4 - 7. The Primary IP is still 127.0.0.1.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Under normal operation, the PC is logged in to ZeroTier One and Cisco
AnyConnect VPN, thus giving it multiple IPs:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
    link/ether 34:e8:94:db:6c:bc brd ff:ff:ff:ff:ff:ff
    inet 192.168.4.7/24 brd 192.168.4.255 scope global dynamic
noprefixroute enp5s0
       valid_lft 84957sec preferred_lft 84957sec
/* ZeroTier One */
4: <redacted>: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel
state UNKNOWN group default qlen 1000
    link/ether <redacted> brd ff:ff:ff:ff:ff:ff
    inet <redacted> brd 192.168.194.255 scope global <redacted>
       valid_lft forever preferred_lft forever
/* Cisco AnyConnect VPN */
5: cscotun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1390 qdisc
fq_codel state UNKNOWN group default qlen 500
    link/none
    inet <redacted> brd <redacted> scope global cscotun0
       valid_lft forever preferred_lft forever

Note that I can recreate my host IP address issue if I disable ZeroTier
One and the Cisco AnyConnect VPN.

In order to support local DNS while logged in to the Cisco VPN, I have
NetworkManager configured to use DNSmasq for the sake of providing split
DNS.

Just now, I think I stumbled on the reason why mythtv-setup is stuck on
127.0.0.1 as my PC's IP. Evidently it runs gethostbyaddr6 like 'getent
hosts' does:

$ getent hosts calvin.home.du
::1             calvin.home.du localhost

Then, detecting that I disabled IPv6 at boot, it resolves localhost to
127.0.0.1.

'getent ahosts' supposedly calls getaddrinfo which ignores IPv6:

$ getent ahosts calvin.home.du
192.168.4.7     STREAM calvin.home.du
192.168.4.7     DGRAM
192.168.4.7     RAW

I had disabled IPv6 because my LAN router isn't configured to support
IPv6 (for instance, no DHCPv6 server) and I'd seen some services (e.g.,
iSCSI) experience issues due to trying to use IPv6. When I had IPv6
enabled at the kernel level, I had disabled IPv6 on my PC's Ethernet
interface yet an IPv6 IP was still assigned to it. It didn't seem right
to have services trying to use IPv6 when I have done nothing to make
IPv6 work on my LAN.

Now Google turns up some forum posts that suggest that MythTV >= 0.26
can have issues when IPv6 is disabled.

So what am I to do? Turn IPv6 back on at the kernel and deal with any
IPv6-related service issues as they crop up? Please advise...

Dave



On 6/15/21 9:39 AM, Stephen Worthington wrote:
> On Tue, 15 Jun 2021 08:17:26 -0500, you wrote:
>
> Ignore the BackendServerIP setting - I checked in a new MythTV install
> I have in a virtual machine and it is not present there, so that value
> is historical and no longer used. The BackendServerAddr setting is
> the current one.
>
>> Deleting the value of BackendServerIP changes the issue. Now 127.0.0.1
>> is treated as the one-and-only Primary IP Address plus it is assigned to
>> a new instance of BackendServerIP:
>>
>> 1. Stop mythbackend
>> 2. Launch mythtv-setup
>> 3. General.
>> 4. Host Address Backend Setup
>> 5. Uncheck Listen on All IP Addresses
>> 6. Select Primary IP Address/DNS Name
>> 7. The only IP listed is 127.0.0.1.
> I am guessing that this is the problem. Mythtv-setup is not seeing
> all the IP addresses in use on the PC for some reason, and is only
> allowing you to set an IP address that it sees as being present. On
> my backend, where I have two IPv4 addresses and two IPv6 addresses on
> br0 (bridged eth0/tap0), it puts all those addresses in the drop down
> list, along with 127.0.0.1 and ::1 and the IPv6 link-local addresses
> and the address on my OpenVPN tun0 interface. If you are only getting
> 127.0.0.1, there must be something that is preventing mythtv-setup
> from seeing the Ethernet interface - it is only seeing the lo
> interface. So what does the "ifconfig" or "ip addr" command show? Do
> all the expected IP addresses show up? Do you get different results
> running those commands as user mythtv and root?
>
> You could try manually changing the MasterServerIP and
> BackendServerAddr entries directly in the database. But if
> mythbackend then can also not see the Ethernet interface, it will not
> work very well.
>
> When the "Listen on All IP Addresses" option is on, mythbackend will
> ignore the IP address settings and listen on both 0.0.0.0 and :: (for
> an IPv6 enabled PC), or 0.0.0.0 only (for an IPv4 only PC). You can
> see what it is listening on with this command:
>
> netstat -anp | grep mythbackend | grep tcp
>
> I am not sure if netstat will need to be run as root to see all the
> connections - I always run it as root. This is what I get:
>
> root@mypvr:~# netstat -anp | grep mythbackend | grep tcp
> tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN
> 3276/mythbackend
> tcp 0 0 0.0.0.0:6544 0.0.0.0:* LISTEN
> 3276/mythbackend
> tcp 0 0 0.0.0.0:6549 0.0.0.0:* LISTEN
> 3276/mythbackend
> tcp 0 0 0.0.0.0:6554 0.0.0.0:* LISTEN
> 3276/mythbackend
> tcp 0 0 127.0.0.1:6543 127.0.0.1:44296
> ESTABLISHED 3276/mythbackend
> tcp 0 0 127.0.0.1:6543 127.0.0.1:44298
> ESTABLISHED 3276/mythbackend
> tcp 0 0 127.0.0.1:6543 127.0.0.1:41406
> ESTABLISHED 3276/mythbackend
> tcp 0 0 127.0.0.1:6543 127.0.0.1:41404
> ESTABLISHED 3276/mythbackend
> tcp 0 0 10.0.2.4:6543 10.0.2.4:49678 ESTABLISHED
> 3276/mythbackend
> tcp6 0 0 :::6543 :::* LISTEN
> 3276/mythbackend
> tcp6 0 0 :::6544 :::* LISTEN
> 3276/mythbackend
> tcp6 0 0 :::6549 :::* LISTEN
> 3276/mythbackend
> tcp6 0 0 :::6554 :::* LISTEN
> 3276/mythbackend
>
> So mythbackend has four listening TCP ports on each of 0.0.0.0 and ::,
> plus some established TCP connections.
>
> Sorry about the line wrapping - my email client does not have a way of
> turning that off.
>
>> 8. Select New Entry and enter 192.168.4.7.
>> 9. Exit Settings / Save and Exit
>> 10. Redo steps 4 - 7. The Primary IP is still 127.0.0.1.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 6/15/21 11:38 AM, Dave Ulrick wrote:
> Under normal operation, the PC is logged in to ZeroTier One and Cisco AnyConnect VPN, thus giving it multiple IPs:
>
> $ ip a

...

>>> 4. Host Address Backend Setup
>>> 5. Uncheck Listen on All IP Addresses <-----------------

Hi,

Haven't been following, but note the help text:

"Listen on All IP Addresses""Allow this backend to receive "
"connections on any IP Address assigned to it. "
"Recommended for most users for ease and "
"reliability."

I suggest turning this back on in order to see addresses
available on the backend host.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

When I turn on Listen on All IP Addresses, 192.168.4.7 is listed among
the set of IP addresses. I can then choose it as my primary IP.
192.168.4.7 is saved if I choose Save and Exit. Good. Then, if I turn
off Listen on All IP Addresses, 192.168.4.7 is replaced with 127.0.0.1,
thus recreating my original issue.

Just now I booted Linux with IPv6 enabled. The mythtv-setup issue with
the back end host address is the same: 127.0.0.1 is my only option if I
turn off Listen on All IP Addresses.

Looks like I'm stuck with listening on all IPs...

Dave




On 6/15/21 11:49 AM, Bill Meek wrote:
> On 6/15/21 11:38 AM, Dave Ulrick wrote:
>> Under normal operation, the PC is logged in to ZeroTier One and Cisco AnyConnect VPN, thus giving it multiple IPs:
>>
>> $ ip a
> ...
>
>>>> 4. Host Address Backend Setup
>>>> 5. Uncheck Listen on All IP Addresses <-----------------
> Hi,
>
> Haven't been following, but note the help text:
>
> "Listen on All IP Addresses""Allow this backend to receive"
> "connections on any IP Address assigned to it. "
> "Recommended for most users for ease and "
> "reliability."
>
> I suggest turning this back on in order to see addresses
> available on the backend host.
>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Tue, 15 Jun 2021 11:38:51 -0500, you wrote:

[snip]
>I had disabled IPv6 because my LAN router isn't configured to support
>IPv6 (for instance, no DHCPv6 server) and I'd seen some services (e.g.,
>iSCSI) experience issues due to trying to use IPv6. When I had IPv6
>enabled at the kernel level, I had disabled IPv6 on my PC's Ethernet
>interface yet an IPv6 IP was still assigned to it. It didn't seem right
>to have services trying to use IPv6 when I have done nothing to make
>IPv6 work on my LAN.
>
>Now Google turns up some forum posts that suggest that MythTV >= 0.26
>can have issues when IPv6 is disabled.
>
>So what am I to do? Turn IPv6 back on at the kernel and deal with any
>IPv6-related service issues as they crop up? Please advise...
>
>Dave

Having local IPv6 working is usually OK if no global unicast IPv6
addresses are assigned. Since your router does not do IPv6, it should
not be sending any IPv6 Router Advertisement packets, so with IPv6
enabled, your interfaces should only get link-local IPv6 addresses -
which they may be able to use to talk to each other on the same
subnet, but should not cause any problems. Windows and Linux boxes
these days all have IPv6 enabled, but if the routers do not do IPv6,
they mostly work just fine without having to disable IPv6.

However, just to be safe, you would want to make sure that your DNS
server(s) did not provide any IPv6 addresses for things. I run ISC
Bind 9 for my DNS servers, and on a special test subnet where IPv6 is
enabled and global unicast IPv6 addresses are assigned, but there is
no working routing to the wider Internet via IPv6, I had a similar
problem, where connections to the Internet frequently failed when they
tried to use IPv6, and if they eventually switched to IPv4 and got a
connection, it took a while and slowed everything down. So I just
configured bind 9 to temporarily only report IPv4 addresses, until I
can fix the IPv6 routing problem. To do that in the latest versions
of bind 9 you have to do two things:

1) Stop bind from listening on IPv6 addresses. Just comment out any
"listen-on-v6" options.

2) Stop bind from returning AAAA addresses. The web pages I found for
this were out of date. They say to just add an option
"filter-aaaa-on-v4 yes;". But in recent bind 9 versions (from 9.13
on), that filter capability has been moved to a plugin library, so you
need to do this instead:

plugin query "filter-aaaa.so" {
filter-aaaa-on-v4 yes;
}

If you are using multiple views in bind 9 as I am, then those lines go
inside the config for each view they apply to. The filter-aaaa.so
library file is part of the main bind9 package on Ubuntu, so it should
already be installed.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 2021-06-15 12:55 p.m., Dave Ulrick wrote:
> When I turn on Listen on All IP Addresses, 192.168.4.7 is listed among
> the set of IP addresses. I can then choose it as my primary IP.
> 192.168.4.7 is saved if I choose Save and Exit. Good. Then, if I turn
> off Listen on All IP Addresses, 192.168.4.7 is replaced with 127.0.0.1,
> thus recreating my original issue.
>
> Just now I booted Linux with IPv6 enabled. The mythtv-setup issue with
> the back end host address is the same: 127.0.0.1 is my only option if I
> turn off Listen on All IP Addresses.
>
> Looks like I'm stuck with listening on all IPs...

This looks like it might be a mysql mis-configuration.
Search your my.cnf or the files in my.cnf.d for 'bind-address'
and comment out that line. Restart mysqld. Test.

If you have no bind-address set, then mysql listens ONLY to localhost.
If you have bind-address=0.0.0.0 then mysql listens to any network.

If you have bind-address=192.168.20.20 then *this* mysql instance will
only accept connections from that IP.
In BE/FE setups, 127.0.0.1 works fine.
If you have a remote front end, the mysql *CLIENT* must be told to
connect to the mysql server using the server's address.

Not sure from this thread whether yours is a BE/FE or remote FE setup.

Geoff

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Just now I changed bind-address to 192.168.4.7 in my.cnf (I have FEs on
multiple PCs) and restarted MySQL. Then I stopped mythbackend and ran
mythtv-config. No change: 127.0.0.1 is still the only accepted host IP
when Listen on All IP Addresses is unchecked.

Dave




On 6/15/21 2:25 PM, R. G. Newbury wrote:
> On 2021-06-15 12:55 p.m., Dave Ulrick wrote:
>> When I turn on Listen on All IP Addresses, 192.168.4.7 is listed
>> among the set of IP addresses. I can then choose it as my primary IP.
>> 192.168.4.7 is saved if I choose Save and Exit. Good. Then, if I turn
>> off Listen on All IP Addresses, 192.168.4.7 is replaced with
>> 127.0.0.1, thus recreating my original issue.
>>
>> Just now I booted Linux with IPv6 enabled. The mythtv-setup issue
>> with the back end host address is the same: 127.0.0.1 is my only
>> option if I turn off Listen on All IP Addresses.
>>
>> Looks like I'm stuck with listening on all IPs...
>
> This looks like it might be a mysql mis-configuration.
> Search your my.cnf or the files in my.cnf.d for 'bind-address'
> and comment out that line. Restart mysqld. Test.
>
> If you have no bind-address set, then mysql listens ONLY to localhost.
> If you have bind-address=0.0.0.0 then mysql listens to any network.
>
> If you have bind-address=192.168.20.20 then *this* mysql instance will
> only accept connections from that IP.
> In BE/FE setups, 127.0.0.1 works fine.
> If you have a remote front end, the mysql *CLIENT* must be told to
> connect to the mysql server using the server's address.
>
> Not sure from this thread whether yours is a BE/FE or remote FE setup.
>
> Geoff
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org