Posts: 81
Joined: May 2014
Reputation:
0
2014-07-21, 04:58
(This post was last modified: 2014-07-21, 05:05 by xmjsilverx.)
I just installed a new router and now I cannot get the cmyth PVR client to work on the master or any of the slaves. I went to backend setup and changed the ip address to the correct one and did the same in cmyth but it will not work. I am not sure what else would have changed. I am able to watch tv using mythtv frontend. Can anyone tell me what to do?
Previously the IP address was 125 and now it is 3. For some reason I am thinking it needs to be over 100. Is that the case? I am trying to figure out how to change it with my new router.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
No it doesn't have to be over 100, don't be silly.
It is a mistake to change the hostname or ip address of the backend though.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 81
Joined: May 2014
Reputation:
0
Well the new router changed the IP address of the backend machine. So don't I need to change all the IP addresses to match that new address in the mythtv backend and in the PVR clients?
Posts: 81
Joined: May 2014
Reputation:
0
I ran the 2 grep commands I was given when setting up the backend and this is what I get when the backend setup IPs are set to 192.168.1.2
micah@micah-HTPC:~$ sudo netstat -tanp |grep 3306
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 3439/mysqld
tcp 1 0 127.0.0.1:43949 127.0.0.1:3306 CLOSE_WAIT 2534/xbmc.bin
tcp 0 0 127.0.0.1:3306 127.0.0.1:43949 FIN_WAIT2 -
micah@micah-HTPC:~$ sudo netstat -tanp|grep myth|grep LISTEN
tcp 0 0 127.0.0.1:6543 0.0.0.0:* LISTEN 2324/mythbackend
tcp 0 0 127.0.0.1:6544 0.0.0.0:* LISTEN 2324/mythbackend
tcp6 0 0 fe80::beee:7bff:fe:6543 :::* LISTEN 2324/mythbackend
tcp6 0 0 ::1:6543 :::* LISTEN 2324/mythbackend
tcp6 0 0 fe80::beee:7bff:fe:6544 :::* LISTEN 2324/mythbackend
tcp6 0 0 ::1:6544 :::* LISTEN 2324/mythbackend
When I set the PVR client to this address it says no PVR clients have been started yet.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
2014-07-22, 04:36
(This post was last modified: 2014-07-22, 04:38 by nickr.)
I recommend you set a static IP in the backend machine either with /etc/network/interfaces (well documented on the internet) or by getting your router to reserve the correct address for it.
The former methiod will survive changes of router.
Or you could go to mythtv-setup on the backend and sort out the IP addresses on the first panel of the first menu option.
Also post one said the new backend address ended in 3, in post four you say you set it to .2.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 81
Joined: May 2014
Reputation:
0
It was 3 but then the router changed it to 2. I have it reserved on the router as 3 now but when changing it in myth-setup and in the pvr clients it still doesn't work. It will work from myth frontend and in the PVR client with everything set to 127.0.0.1
Posts: 81
Joined: May 2014
Reputation:
0
Ok, something really weird is going on and I am not sure why. When I change the backend addresses back to 127.0.0.1 I can tune the channels using cmyth on that same machine even though that address is set to 192.168.1.3 and from my phone it will upload all of the tv information when cmyth is set to 192.168.1.3 but it will not play the channels. If I change the backend setup to 192.168.1.3 nothing works. Is there some setting in the router that could be preventing that? In the LAN setup section of the router there is something called RIP version. Should that be changed?
Posts: 81
Joined: May 2014
Reputation:
0
I somehow got it working but I am not sure why or how. I changed the RIP form disabled to the 3 versions and by the last one everything started working. So to make sure that was the issue I switched it back to disabled. It is still working after that. So somehow after 3 days of messing with it, it's fixed.
