Hi Stephen!
Thanks for coming to my rescue again!
> sudo su
> mysql
> use mythconverg;
> select * from settings where data like '%192.168.%';
> exit
> exit
Here got:
+-------------------+------------------------------------------+-----------+
| value | data + hostname |
+-------------------+------------------------------------------+-----------+
| BackendServerAddr | 192.168.0.3 | backend-3 |
| EventCmdAll | mythsgu event -h 192.168.0.4 %EVENTNAME% | backend-3 |
+-------------------+------------------------------------------+-----------+
2 rows in set (0.04 sec)
MariaDB [mythconverg]>
- - -
> Then check all the different config.xml files:
/etc/mythtv/config.xml ==> localhost
//home/mythtv//.mythtv/config.xml ==> localhost
//home//<mythfrontend user>/.mythtv/config.xml ==> u = barry ==>
192.168.4.3
- - -
> It can also be a good idea to check all settings in /etc for the old
> IP address, such as /etc/hosts:
>
> sudo su
> cd /etc
> grep -r "192.168." *
> exit
4^th line down – bolded in my draft – is a backup copy. Appears to be
the only instance of the old IP, though habe no idea why some other
networks are in there (the new LAN is 192.168.4.x)
root@Backend-3:/etc# grep -r "192.168.*"
NetworkManager/system-connections/Static
IP:address1=192.168.4.3/24,192.168.4.1
NetworkManager/system-connections/Static IP:dns=192.168.4.1;8.8.8.8;
*mythtv/config.xml_original: <Host>192.168.0.3</Host>*
cups/cups-browsed.conf:# BrowseAllow 192.168.1.12
cups/cups-browsed.conf:# BrowseAllow 192.168.1.0/24
cups/cups-browsed.conf:# BrowseAllow 192.168.1.0/255.255.255.0
cups/cups-browsed.conf:# BrowseDeny 192.168.1.13
cups/cups-browsed.conf:# BrowseDeny 192.168.3.0/24
cups/cups-browsed.conf:# BrowseDeny 192.168.3.0/255.255.255.0
ppp/options:# ms-dns 192.168.1.1
ppp/options:# ms-dns 192.168.1.2
ppp/options:# ms-wins 192.168.1.50
ppp/options:# ms-wins 192.168.1.51
security/access.conf:#+ : root : 192.168.200.1 192.168.200.4 192.168.200.9
security/access.conf:# User "root" should get access from network
192.168.201.
security/access.conf:# The same is 192.168.201.0/24 or
192.168.201.0/255.255.255.0
security/access.conf:#+ : root : 192.168.201.
ntp.conf:#restrict 192.168.123.0 mask 255.255.255.0 notrust
ntp.conf:#broadcast 192.168.123.255
fstab://192.168.0.120/Backups/Backend_3 /media/NSA320_BE_3 cifs
username=Barry,password=B********6,iocharset=utf8,gid=1000,uid=1000,file_mode=0777,dirmode=0777,vers=1.00
0
avahi/hosts:# 192.168.0.1 router.local
avahi/avahi-daemon.conf:#publish-dns-servers=192.168.50.1, 192.168.50.2
sane.d/dell1600n_net.conf:#named_scanner: 192.168.0.20
sane.d/magicolor.conf:# net 192.168.0.1
sane.d/saned.conf:#192.168.0.1
sane.d/saned.conf:#192.168.0.1/29
sane.d/epson2.conf:# net 192.168.1.123
sane.d/epsonds.conf:# net 192.168.1.123
sane.d/kodakaio.conf:#net 192.168.1.2 0x4041
sane.d/kodakaio.conf:#net 192.168.1.17 0x4067
fwupd/redfish.conf:# ex:
https://192.168.0.133:443 systemd/system/local-network-pingable.service:ExecStartPre=/bin/bash -c
"/usr/lo
ffserver.conf:ACL allow 192.168.0.0 192.168.255.255
dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes:#
new_rfc3442_classless_static_routes='24 192 168 10 192 168 1 1 8 10 10
17 66 41'
dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes:# 192.168.10.0/24
via 192.168.1.1
root@Backend-3:/etc#
Visually scanned that list -- not sure what some of it is though looks
like with the power failure I had this morning some of the devices
automatically updated to the new network. Tried a grep command to make
sure only the one old (192.168.0.3) noted during the visual scan:
root@Backend-3:/etc# grep -r "192.168.*" | grep 192.168.0.3
mythtv/config.xml_original: <Host>192.168.0.3</Host>
Half-thinking to delete or otherwise modify that file -- my old MS-DOS
8.3 days is kicking in: filenames were a max of eight characters, dot,
max. of three characters. Decided to post and await instructions!
TIA
Barry