[mythtv-users] What to check/change when changing LAN subnet

Bill Meek keemllib at gmail.com
Tue May 13 00:30:25 UTC 2014


On 05/12/2014 05:18 PM, Craig Huff wrote:
> Many moons ago I set up my LAN with a unique subnet -- 192.168.nn.* --
> where nn was _not_ 1.
...
> What else do I need to address, especially with the mythTV FE/BE systems?

Don't know what version of MythTV you're running, but lets assume 0.26 or
greater, so you don't need to worry about mysql.txt, just config.xml. And,
if you used hostnames, rather than IPs you needn't fire up the FE setup GUI
to change them. All users (all copies.)

Then there's /etc/mysql/my.cnf which you surely /never/ change, so you
just need to look in /etc/mysql/conf.d/<allNames>.cnf for changes like:
bind-address=x.x.x.x. And if it's 0.0.0.0, no work there either. Hika's
method would catch potential problems here too.

Do you have any custom scripts with IPs stored in:

     Pre-shutdown-check command
     Miscellaneous status application

or in User Jobs/System Events? You could do:

     SELECT * FROM settings WHERE value LIKE '%command%' AND hostname IS NULL;

For me, it's only the two I listed above where I have a need to use
netstat -n.

Then there's external things like tablets/phones that may require IPs.

But I tend to agree with Sam's idea. For all the planning you do, it's
likely that nobody here knows enough about your system to identify all
the places you've had to use IPs.

-- 
Bill


More information about the mythtv-users mailing list