Avalpa Community

The place where we can talk freely about Avalpa product and services
It is currently Thu May 26, 2022 7:33 pm

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 1 post ] 
Author Message
PostPosted: Thu Dec 18, 2014 5:42 pm 
Offline

Joined: Wed Sep 25, 2013 11:38 am
Posts: 4
Hello everybody.

My name's Federico Allegretti and i'm a long term follower of this project since the time it was named Cinecast :D

After a long period of overwhelming jobs, i'm returning experiemnting with the tools provided to the comunity from Avalpa.

I build up a machine (core2 duo at 2.6 ghz and 2GB of ram) equipped with a Linear Systems Ltd. DVB Master FD.
Operating system is a Debian Unstable (jessie 8.0), ip of opencaster server is 192.168.1.120
added the multicast route with:
route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0

so my Kernel IP routing table is:
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
224.0.0.0 * 240.0.0.0 U 0 0 0 eth0

Now i'm following the manual (http://www.avalpa.com/assets/freesoft/o ... l-v3.0.pdf) trying the tips step by step.

But the first halt comes trying to find the command tsasisend (pag 13) on my linux shell ... no trace of it.

Second test failed when trying to broadcast with "tsudpsend sample.ts 224.0.1.2 12345 13271000" the clip you provided trough the "second package" archive (http://www.avalpa.com/assets/freesoft/o ... .3.2.2.tgz).

on my windows machine vlc cannot find the stream from udp://224.0.1.2:1234 (1234 or 12345 ? typo error?)
pinging from it to the multicast (ping 224.0.0.1) returns (windows ping application do not support the -t option):

Esecuzione di Ping 224.0.0.1 con 32 byte di dati:
Richiesta scaduta.

Statistiche Ping per 224.0.0.1:
Pacchetti: Trasmessi = 1, Ricevuti = 0,
Persi = 1 (100% persi)

disabling the windows firewall and retrying ping 224.0.0.1
C:\Users\allegfede>ping 224.0.0.1
Esecuzione di Ping 224.0.0.1 con 32 byte di dati:
Risposta da 192.168.1.200: byte=32 durata=1ms TTL=64
Risposta da 192.168.1.200: byte=32 durata<1ms TTL=64
Risposta da 192.168.1.3: byte=32 durata=1ms TTL=255
Risposta da 192.168.1.200: byte=32 durata=1ms TTL=64

Statistiche Ping per 224.0.0.1:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 1ms, Medio = 0ms

pinging from linux pc (ping -t 1 -c 2 224.0.0.1) returns:

PING 224.0.0.1 (224.0.0.1) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=255 time=1.09 ms
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=2.71 ms (DUP!)
64 bytes from 192.168.1.3: icmp_seq=2 ttl=255 time=1.09 ms

who is 192.168.1.3? who is 192.168.1.200? Other machines on my lan serving udp packets?

Thanks for the reading and i'll continue trying to understand your interesting suite of applications :D


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group