Running Ventrilo on N5200 - Anyone got it to work?

[nibbles]

Hello,


Just wondering if anyone managed to get ventrillo to work fine under any of the thecus nas boxes.

I was able to install it fine but I was not able to get response from it even though it was showing running fine. I believe it's a security issue and wondering if anyone out there would share their results with us.

Thanks
Nibbles

[nibbles]

Not even 1 person considered doing this? :-).

Wow... I previously there was discussion in wishlist for using Teamspeak. Teamspeak is a little more of a pain to setup so I thought Ventrilo would be better place to start.

Nibbles.

[pit234a]

In fact I had to google to see, what ventrillo means and this shows, that I don't need it and dan't know, what I would do with it. But what I read in the instructions and in the FAQ section makes me wonder, whether you really could run it on your NAS. Didn't you get an error message? The FAQ describes an error, when starting on a redhat installation and where one set of libs are missing and I doubt, that those libs are found on the NAS, where busybox is a pretty limited OS. At least, with a fast view, I couldn't see those libs in the standard /lib-folders.
So, you tell us, that it looks like ventrillo would run, but you don't tell us, why you believe that and what you did to install and start it. You assume some problems with rights and user management, but you don't tell us, what you did to find this reasonable.
Sorry for that I sound like a bad tutor, but your question sounds a bit like: hey, who solves my problem for me, I don't want to do it myself! You don't deliver enough basic facts to make your problem transparent and interesting and you don't establish your level of investigation in the problem.

Ventrillo, as far as I can see, is not of any interest for me and as it looks, not for a lot of other Thecus Users too. The one thing you could want, is to operate a server on the NAS, where others could connect to. I doubt, but I don't know, that there is a open port for ventrillo established on the NAS.
So, I would suggest you first check, whether the server starts and is up and running. This you see with ps, as you might know and they mention something about a log-file, that should give information about problems and errors. You also could start the server without -d option to see the response directly in your ssh session. Next, if you find it running and got no errors, I would check against your Thecus IP with nmap, if that service opened a port and whether this is the one, you used in your client configuration.
Without detailed knowledge, I bet you find something that points to a problem in following this routine and if not, you should at least get some information that may be helpful for deeper trouble shooting.
As for now, all is left open: you'll have to fix something.

[nibbles]

Originally Posted by pit234a

But what I read in the instructions and in the FAQ section makes me wonder, whether you really could run it on your NAS. Didn't you get an error message?
The FAQ describes an error, when starting on a redhat installation and where one set of libs are missing and I doubt, that those libs are found on the NAS, where busybox is a pretty limited OS.
At least, with a fast view, I couldn't see those libs in the standard /lib-folders.

Ironically, I did not but I will be testing it again soon and will share whatever finding I have with you once I do.

In addtion, the errors you referred to may be true for certain scenario to a given flavor of a specific distro but I believe what you're referring to is more specific to redhat os since, I'm able to install it flawlessly on 2 other distro's and it worked find however, I had encountered similar symtom once with Ubuntu 7.04 and I remember it was something to do with security and why I was interested in this discussion. (happened using Ubuntu 7x series)

Originally Posted by pit234a

So, you tell us, that it looks like ventrillo would run, but you don't tell us, why you believe that and what you did to install and start it. You assume some problems with rights and user management, but you don't tell us, what you did to find this reasonable.

why I believe that it would run is that from all other installs I've performed on "other" O/S platforms in linux is that everything pretty much seems to installs itself in one directory path of my choice. Feel free to try installing it yourself and correct me if I'm wrong. Right now I'm not at home to provide results or logs that you'd like to see but would be happy to do it if it helps to shed some light.

4) Type "mkdir ventrilo"
5) Type "cd ventrilo"

The very basics of the installs are as follows once you have downloaded:
6) Copy the tar.gz file into this new directory. (out of memory using wget command I think)

extracting the file:
7) Type "gunzip " followed by the name of the tar.gz file.
8) Type "tar xf " followed by the name of the tar file. (gunzip removed the gz extension).

All the files extract to same location (the default directory you create)

10) Type: "./ventrilo_srv".

Depending on the flavour of your Linux - some require sudo command to allow it to run as root otherwise, it does not work.

Originally Posted by pit234a

Ventrillo, as far as I can see, is not of any interest for me and as it looks, not for a lot of other Thecus Users too. The one thing you could want, is to operate a server on the NAS, where others could connect to. I doubt, but I don't know, that there is a open port for ventrillo established on the NAS. So, I would suggest you first check, whether the server starts and is up and running. This you see with ps, as you might know and they mention something about a log-file, that should give information about problems and errors.

I've had no problem running the application - when I had checked it at the time I installed it but I will try to get all of the info you're looking for including any log files. However when I checked at the time when I tried, I believe there was no errors showing.

Originally Posted by pit234a

You also could start the server without -d option to see the response directly in your ssh session. Next, if you find it running and got no errors, I would check against your Thecus IP with nmap, if that service opened a port and whether this is the one, you used in your client configuration. Without detailed knowledge, I bet you find something that points to a problem in following this routine and if not, you should at least get some information that may be helpful for deeper trouble shooting.

I think you mentioned a good point using the -d to see what happens when I try to run it in ssh. I will be trying that as well to see if anything comes up. There is a default port that it uses so also checking nmap would be appropriate course to look at. my port is triggered on the router to point to my nas using 192.168.0.100 currently for it. However bear in mind that when I checked - Ventrilo doesn't bomb out on me nor is there any errors from last time I tried. I will document what I get and respond to the thread for others to see.

Sorry for the min. info but I'm not at home to test at this time.

Nibbles.

[pit234a]

Found some time this morning and tested this and yes, you are right, this ventrilo seems to run on the thecus without further changes.
I downloaded it, tar -xfz in the directory ventrilo and found a new directory ventsrv then.
cd ventsrv and ./ventrilo_srv started the server with some output. I show details here:

root@127.0.0.1:/raid/data/pit/ventrilo# tar -xzf ventrilo_srv-3.0.2-Linux-i386.tar.gz
root@127.0.0.1:/raid/data/pit/ventrilo# ls
ventrilo_srv-3.0.2-Linux-i386.tar.gz  ventsrv/
root@127.0.0.1:/raid/data/pit/ventrilo# cd ventsrv
root@127.0.0.1:/raid/data/pit/ventrilo/ventsrv# ls
LICENSE           ventrilo_srv*     ventrilo_srv.htm  ventrilo_srv.ini  ventrilo_status*
root@127.0.0.1:/raid/data/pit/ventrilo/ventsrv# ./ventrilo_srv
Ventrilo Server - Public - Version 3.0.2
(c)Copyright 1999-2007 Flagship Industries, Inc.

Version           = 3.0.2
Name              = Server 1
Phonetic          = Server 1
Auth              = 0
Duplicates        = 1
SendBuffer        = 131072
RecvBuffer        = 131072
LogonTimeout      = 5
CloseStd          = 1
TimeStamp         = 0
PingRate          = 10
ExtraBuffer       = 131072
ChanWidth         = 0
ChanDepth         = 8
ChanClients       = 0
DisableQuit       = 0
VoiceCodec        = 0 (GSM 6.10)
VoiceFormat       = 1 (11 KHz, 16 bit) - Bytes/Sec 2210
SilentLobby       = 0
AutoKick          = 0
MaxClients        = 8


READY:

----------
END: Shutting down the server.
END: Shutdown complete. Uptime was 0 00:11:18.

The end of the server in the last two lines was “STRG+C”.
When I inspected the running processes with ps, I found ventrilo active:

root@127.0.0.1:~# ps | grep ventr
30795 root        704 S   ./ventrilo_srv

There was no problem or error mentioned.
When I run nmap, I found:

[root@syo]~ # nmap 192.168.0.100

Starting Nmap 4.62 ( http://nmap.org ) at 2008-08-06 10:29 CEST
Interesting ports on 192.168.0.100:
Not shown: 1705 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
80/tcp   open  http
111/tcp  open  rpcbind
443/tcp  open  https
548/tcp  open  afp
631/tcp  open  ipp
850/tcp  open  unknown
2000/tcp open  callbook
2049/tcp open  nfs
MAC Address: 00:14:FD:11:30:AA (Thecus Technology)

Nmap done: 1 IP address (1 host up) scanned in 568.886 seconds

So, there seems to be no further port open for the ventrilo.
I don't know enough about that stuff and my time is over now, but /etc/services at least shows not a lot of free open ports for the NAS. Somehow, you probably have to give the ventrilo server a chance to open one port and listen to incoming calls on it.
Bye.

[nibbles]

Originally Posted by pit234a

Found some time this morning and tested this and yes, you are right, this ventrilo seems to run on the thecus without further changes.
I downloaded it, tar -xfz in the directory ventrilo and found a new directory ventsrv then.
cd ventsrv and ./ventrilo_srv started the server with some output. I show details here:
[code]

<snip>

When I inspected the running processes with ps, I found ventrilo active:

root@127.0.0.1:~# ps | grep ventr
30795 root        704 S   ./ventrilo_srv

There was no problem or error mentioned.
When I run nmap, I found:

[root@syo]~ # nmap 192.168.0.100

Starting Nmap 4.62 ( http://nmap.org ) at 2008-08-06 10:29 CEST
Interesting ports on 192.168.0.100:
Not shown: 1705 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
80/tcp   open  http
111/tcp  open  rpcbind
443/tcp  open  https
548/tcp  open  afp
631/tcp  open  ipp
850/tcp  open  unknown
2000/tcp open  callbook
2049/tcp open  nfs
MAC Address: 00:14:FD:11:30:AA (Thecus Technology)

Nmap done: 1 IP address (1 host up) scanned in 568.886 seconds

So, there seems to be no further port open for the ventrilo.
I don't know enough about that stuff and my time is over now, but /etc/services at least shows not a lot of free open ports for the NAS. Somehow, you probably have to give the ventrilo server a chance to open one port and listen to incoming calls on it.
Bye.

This pretty much the results I've done. And since the port is not being shown available so no doubt the application will not be able to respond to any incoming connections for the outside world. (subjective to having your router mapped with assigned port as well) Wondering if using the "nc" command to force the port open would make it work. If that fixes the problem then it would serve as another potental add on module for use.

Any linux Guru's out there reading this? I will continue playing around with it as ventrillo serves a huge population of gamers out there - notably those playing MMOG.

Cheers,
Nibbles