[SOLVED] Connecting to VNSI Server remotley
#1
Hey.

So I'm using the following:
Code:
XBMC: 12.1
VNSI Add In: 1.6.4


And VDR:
Code:
vdr (1.7.28/1.7.28) - The Video Disk Recorder
epgsearchonly (0.0.1) - Direct access to epgsearch's search menu
xineliboutput (1.0.90-cvs) - X11/xine-lib output plugin
conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu
vnsiserver3 (0.9.1) - VDR-Network-Streaming-Interface (VNSI) Server
quickepgsearch (0.0.1) - Quick search for broadcasts
epgsearch (1.0.1) - search the EPG for repeats and more
streamdev-server (0.6.0) - VDR Streaming Server

When I connect on the same machine as the vdr server and use IP address 127.0.0.1 it works. However when I use the 192.168.1.X ip it doesn't and I get the following in the xbmc logs:

Code:
21:41:17 T:140227776100096  NOTICE: PVRManager - starting up
21:41:17 T:140226924115712  NOTICE: Thread PVR manager start, auto delete: false
21:41:17 T:140226915723008  NOTICE: Thread PVR add-on updater start, auto delete: false
21:41:17 T:140226915723008   ERROR: AddOnLog: VDR VNSI Client: SignalConnectionLost - connection lost !!!
21:41:17 T:140226915723008   ERROR: AddOnLog: VDR VNSI Client: Login - failed to read greeting from server
21:41:17 T:140226915723008   ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
21:41:17 T:140226915723008 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1
21:41:17 T:140227757143808  NOTICE: Thread CAddonStatusHandler:pvr.vdr.vnsi start, auto delete: true
21:41:22 T:140226915723008   ERROR: AddOnLog: VDR VNSI Client: SignalConnectionLost - connection lost !!!
21:41:22 T:140226915723008   ERROR: AddOnLog: VDR VNSI Client: Login - failed to read greeting from server
21:41:22 T:140226915723008   ERROR: ADDON: Dll VDR VNSI Client - Client returned bad status (1) from Create and is not usable
21:41:22 T:140226915723008 WARNING: UpdateAndInitialiseClients - failed to create add-on VDR VNSI Client, status = 1

My allowed hosts looks like this, note I built this from FernetMenta's git and no allowed_hosts exsisted so I manually created it:
Code:
/etc/vdr/plugins/vnsiserver3$ cat allowed_hosts.conf
192.168.1.0/24
0.0.0.0/0
Any ideas what I'm doing wrong?
Reply
#2
the only thing I see is

Code:
/etc/vdr/plugins/vnsiserver3

for me this is

Code:
/etc/vdr/plugins/vnsiserver
(or vnsiserver4 on new timeshift code)

could it be it doesn't find the allowed_hosts in vnsiserver dir and uses the default one which got no allowed host named 192.168.xx?
Reply
#3
Hey,

I copied my allowed_hosts to /etc/vdr/plugins/vnsiserver/allowed_hosts.conf and still no joy.

I can still connect using 127.0.0.1 but can't connect using 192.168.1.1 from the same computer.

Also can't connect to 192.168.1.1 from a remote computer.
Reply
#4
vnsiserver3 is correct for vnsi3.

192.168.1.1
This is certainly not the ip of your remote pc. Looks like the ip of your router.
Reply
#5
No you are right 192.168.1.1 was for ease

The server is 192.168.1.116 (and that is the number I'm putting into the add in config in XBMC)
Reply
#6
I've just updated vnsiserver4 and the Frodo addin and still have the same problem.

I've just uploaded db logs here:

Using 127.0.0.1 as the IP
http://xbmclogs.com/show.php?id=9215

Using 192.168.1.116 as the IP:
http://xbmclogs.com/show.php?id=9217

Can anyone see if I've done something silly?
Reply
#7
Found /var/log/syslog and found this:

Apr 2 20:28:00 fox vdr: [29604] VNSI-Error: Invalid or missing '/var/lib/vdr/plugins/vnsiserver4/allowed_hosts.conf'. falling back to 'svdrphosts.conf'.

so pretty obvious what the problem is - created the file and it works now.
Reply
#8
FernetMenta: is it possible to make the installation copy/create this file for editing? I had to manually create it.
Reply
#9
That's what packagers do when distributing binaries. At compilation time you don't know where the user wants to have those files at runtime.
Reply
#10
Presumably the "make" is also installing it though? Otherwise how does VDR pick up the new vnsiserver4 and why doesn't it work when not run as sudo? I'm guessing the parameters passed in to the make are something to do with this?

I guess at least people that are compiling should be able to find the problem so possibly no big deal especially if we have this thread to point to the issue.
Reply
#11
Well, if you type "make install" for installing vdr, it won't install the config files either. Make install is no package install, you can't just simply overwrite existing config files.
Reply

Logout Mark Read Team Forum Stats Members Help
[SOLVED] Connecting to VNSI Server remotley1