News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu

Locating server - doesn't respond -

Started by luis, February 15, 2006, 22:04:45

Previous topic - Next topic

luis

Hi, first of all congratulations for this great idea, I'm looking forward to have it running.

I promise I've read same topic in the forum and checked everything, even added some log's into the vompserver sources to try to find the reason, but I can't....

- I've got MediaMVP at 192.168.1.12.
- DHCP is working perfect, it allways receives same IP.
- I'm using dongle-0.1.1
- I can telnet to the MediaMVP,
- I even killall vompclient and started it manually '-d' just to see
  that it stays at:
  :
  02:27:11.210139 [notice] VDR - Broadcasting for server   

- On the server I've got vdr-1.3.42, vompserver from CVS (today)
- Compiles fine and runs and listen in 3024 (tcp/udp)
tcp        0      0 0.0.0.0:3024        0.0.0.0:*               LISTEN      24456/vdr           
udp        0      0 0.0.0.0:3024        0.0.0.0:*                           24456/vdr           
- I see packets comming into my box (I discard then any firewall issue...)
# tcpdump -ni eth0 host 192.168.1.12
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
23:02:19.697364 IP 192.168.1.12.3024 > 255.255.255.255.3024: UDP, length 11
23:02:21.197270 IP 192.168.1.12.3024 > 255.255.255.255.3024: UDP, length 11
23:02:22.697384 IP 192.168.1.12.3024 > 255.255.255.255.3024: UDP, length 11     
:

But... vompserver doesn't seem to receive them or it's receiving but not answering...

Any idea / tip to try to troubleshoot it.

thanks in advance



luis

I forgot to add ouput from lsof | grep UDP:
:
:
vdr       26882    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26883    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26902    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26903    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26920    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26921    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26926    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26927    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26928    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26929    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26930    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26931    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26932    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26937    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26947    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26954    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26955    vdr   13u     IPv4    5882780                   UDP *:3024
vdr       26956    vdr   13u     IPv4    5882780                   UDP *:3024 

luis

Hi again (busy night here :-))

I've downloaded and installed vompserver-0.1.0.tar.gz and this version works.

As I've seen in another thread the vompserver cvs works only with cvs dongle.bin.

Any option to get cvs dongle.bin?

thanks again.

Chris

Hi, glad you got that working. The latest binary is 0.1.1 for the client which works with 0.1.0 server. (I think. It's been a while!) I agree it's all a bit confusing at the moment... I don't plan on making regular CVS-latest dongles, but the latest dongle on my vomp web page will always be fairly up to date. Ish. :)