Kodi on external network plays recorded programs, but doesn't work with LiveTV

[nwuser]

Hello folks,

My frontend is on a different network compared to my backend. I have setup port forwarding for the two ports that MythTV requires. But for some reason I can only watch the recordings and not live stream. Can you suggest why that is the case. I have used nextPVR previously and it has worked fine. Would like to get this going. Thanks for your time!

[nwuser]

Can somebody help me troubleshoot this issue? The same raspberry Pi frontend worked when it was on the same network. I tested another frontend on the same network but with the public IP address and no issues. The issue is when I move the Pi to a different network. I have setup port forwarding for both ports but cant get live stream to work. Only recordins playback with no issues. Thanks!

[bill6502]

No experience from me using a port forwarding solution.

And can't explain why recordings work and LiveTV doesn't.

Wondering if LiveTV uses a port that you haven't cared for.
Try: sudo netstat -pant | grep myth for a current list. Or,
look for: "Listening" in the backend log.

You'll need to provide some more details I think. Which two
ports did you forward, what actually happens when LiveTV
is selected (and is failing) and a complete (not snippet) frontend
log from startup to the error.

That's the best I can come up with for now. We have users that access
their backend over the public network, so I'm not sure why port forwarding
is required.

[nwuser]

Thanks, bill6502. I have forwarded 6543 and 6544. These are the ports that the Kodi mythtv pvr client addon requires. I need to port forward because my NUC (MythTV backend) is behind the router on an intranet. Is there another alternative?

sudo netstat shows 2 more ports 6554,6549. I believe I tried port forwarding this too but didnt work. I will give this another shot and get back to you along with the log file from Kodi.

[bill6502]

OK, I assumed frontend meant mythfrontend (changed your title to
get more eyes on it.) I know Kodi uses 6544, the Services API, and
6543 makes sense. Don't know if it uses other ports.

I'm sure you know that the Kodi plugin isn't a MythTV product, but there
should be other users of it here. Port forwarding, as described above
makes sense in this case.

[nwuser]

I finally got hold of my remote Rpi2. I tried opening a bunch more ports on my router based on netstat, flushed mythBE iptables and still no luck. Here is a freeze of netstat -pan | grep myth when I am watching liveTV on 192.168.1.101. 192.168.1.100 is my mythBE. 50.51.52.53 is my remote end that is unable to view. I have opened ports on router for port forwarding to 6543, 6544, 6554, 6549. Can you think of some means to help me troubleshoot it? Thank you so much for your time!

Code: Select all

tcp        0      0 192.168.1.100:6554      0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 127.0.0.1:6554          0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 192.168.1.100:6543      0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 127.0.0.1:6543          0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 192.168.1.100:6544      0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 127.0.0.1:6544          0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 192.168.1.100:6549      0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 127.0.0.1:6549          0.0.0.0:*               LISTEN      1543/mythbackend
tcp        0      0 127.0.0.1:56614         127.0.0.1:6543          ESTABLISHED 4344/mythcommflag
tcp        0      0 192.168.1.100:6543      192.168.1.101:59504     ESTABLISHED 1543/mythbackend
tcp        0      0 127.0.0.1:6543          127.0.0.1:56614         ESTABLISHED 1543/mythbackend
tcp        0      0 192.168.1.100:6543      50.51.52.53:44316       ESTABLISHED 1543/mythbackend
tcp        0      0 127.0.0.1:56616         127.0.0.1:6543          ESTABLISHED 4344/mythcommflag
tcp        0      0 192.168.1.100:6543      50.51.52.53:44338       ESTABLISHED 1543/mythbackend
tcp        0     13 192.168.1.100:6543      192.168.1.101:59494     ESTABLISHED 1543/mythbackend
tcp        0      0 192.168.1.100:6543      192.168.1.1:37620       ESTABLISHED 1543/mythbackend
tcp        0      0 192.168.1.100:6543      192.168.1.101:59570     ESTABLISHED 1543/mythbackend
tcp        0      0 192.168.1.100:6543      192.168.1.1:34032       ESTABLISHED 1543/mythbackend
tcp        0      0 192.168.1.100:6543      50.51.52.53:44296       ESTABLISHED 1543/mythbackend
tcp        0      0 127.0.0.1:6543          127.0.0.1:56616         ESTABLISHED 1543/mythbackend
tcp6       0      0 blah::blah:blah:bl:6554 :::*                    LISTEN      1543/mythbackend
tcp6       0      0 ::1:6554                :::*                    LISTEN      1543/mythbackend
tcp6       0      0 blah::blah:blah:bl:6543 :::*                    LISTEN      1543/mythbackend
tcp6       0      0 ::1:6543                :::*                    LISTEN      1543/mythbackend
tcp6       0      0 blah::blah:blah:bl:6544 :::*                    LISTEN      1543/mythbackend
tcp6       0      0 ::1:6544                :::*                    LISTEN      1543/mythbackend
tcp6       0      0 blah::blah:blah:bl:6549 :::*                    LISTEN      1543/mythbackend
tcp6       0      0 ::1:6549                :::*                    LISTEN      1543/mythbackend
udp        0      0 255.255.255.255:1900    0.0.0.0:*                           1543/mythbackend
udp        0      0 239.255.255.250:1900    0.0.0.0:*                           1543/mythbackend

[bill6502]

Hi,

Is the "remote Rpi2" running mythfrontend? If so, then I'd start it
with the -v playback switch.

If it's Kodi, I'm not of much help. If Kodi has logs, I'd go there.

Wireshark may help (if you can see FE or Kodi send something and get
an RST or perhaps nothing in response.

You can increase the backend logging while it's running with:
mythbackend --setverbose network.