2017-04-19, 07:24 PM
It is not just NEWA, the internal web server which web client uses also has private IP masks.
Martin
Martin
NextPVR Forums
Information
Community Announcements
New NextPVR client for Raspberry Pi 2 and 3.
New NextPVR client for Raspberry Pi 2 and 3.
|
2017-04-19, 07:50 PM
pBS, you may want to have a look at this: https://en.wikipedia.org/wiki/Private_ne...ess_spaces
 Setting all of the devices on your LAN back to a private address block should rid your network of many gremlins. 
i3-3570k, 8GB RAM, Win10 Pro, Nvidia GT710, HDHomeRun Prime, NPVR 5.2.3.211114
On a clear disk, you can seek forever...
2017-04-19, 08:17 PM
i've known about this for years, i think i first assigned it before they ran out of ip4 internet addresses back in 05, so now they started using these also..
one of the rfc's said it wasn't supposed to be routable, but i think it got superceded... either way, my router's nat translation has kept me working away fine since then.. so even tho it's a public type address, the public internet never sees it, so no conflict.. newer technologies and security have started using it by the book now tho, so i guess i have to change it finally..  lots of stuff to change on router and devices/machines so it may take a bit..lol
Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie
2017-04-19, 08:27 PM
Back on topic if you change the PIN and have the 2 remote streaming settings in config.xml Fred's client should work.
Martin
2017-04-20, 07:03 AM
mvallevand Wrote:Back on topic if you change the PIN and have the 2 remote streaming settings in config.xml Fred's client should work. ATM there is no way to provide a custom PIN to the Client. I guess the only way to get it working with the current version is to use a private ip address range. I will probably add PIN support in a future release, but canât tell when exactly. /Fred
2017-04-20, 09:23 PM
these settings? or is there another?
<AllowRemoteAPI>true</AllowRemoteAPI> <AllowRemoteTranscode>true</AllowRemoteTranscode> <AllowRemoteStreaming>true</AllowRemoteStreaming> as this is my entire subnet using these ip's, will have to wait till i have time when not recording as i use a hdhr prime.. but this weekend for sure..
Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie
2017-04-20, 10:37 PM
Yes but I think the PIN needs to be non-zero too. What about just calling the private IPv6 subnet fe80:::? Not sure if you can force Fred's client to use it but the web client server supports it.
Martin
2018-07-05, 09:41 PM
Looks like it's been awhile since anyone posted on this.. assume it's a dead project now?
2018-07-09, 12:55 AM
it's true Fred250 isn't on as often anymore, but afaik this should still work as the client itself is built-in to NextPVR - the "NextPiVR" piece just provides a way to present the web client and tie the playback functions into omxplayer.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2019-03-30, 12:18 PM
Sorry to resurrect an old thread but I'd like to give this a go.
However I can't get it to install because libcec3 is a dependency and is no longer available. I've installed libcec4 but that doesn't work. Is libcec3 available anywhere or failing that how do I update the package to use libcec4? Thanks Eric |
|
|
