[mythtv-users] SOLVED ongoing commo issues with compiled frontend / backend

[Mepis Rocks]

thanks for the replies folks...

stumbled across a seemingly unrelated post on code.mythtv, but reading more
it made sense...

i had ipv6 disabled on my system but the loopback was still set to use ipv6
and i couldn't see a way to disable it on lo...

DEFINITELY an IPV6 issue....

i re-enabled IPV6, rebooted, reinstalled mythtv from the repo...

because i had been running a compiled version i needed to restore my
database to the version before installing the newest compiled code (good
example of making backups BEFORE making serious changes)

re-ran mythtv-setup and set the backend IPs to 192.168.1.xxx, then started
the backend.

started up the mythfrontend, went into setup and changed the IPs for the
backend to 192.168.1.xxx

viola! i have mythtv running again!!!!

this ipv4/ipv6 issue effects both the debian multimedia package AND the
compiled version that i tested...

i've seen ipv6 cause issues with other software. unrelated to mythtv, but
an ipv6 compatibility issue, wget doesn't do ipv6. you can use an command
line option, or config option tell it to use just ipv4.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20111212/1513a9fb/attachment.html