search

braice / MuMuDVB

A DVB IPTV streaming software
http://mumudvb.braice.net/
GNU General Public License v2.0
219 stars 133 forks source link

no multicast traffic with following conf (help please) #63

Closed ovidiu31 closed 10 years ago

ovidiu31 commented 10 years ago

with full autoconfig i have multicast traffic but channels are having bottlenecks with partial config when i tcpdump for check traffic i got no multicast packets just root@debian:~# tcpdump -n host 192.168.50.2 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 02:53:59.806751 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2881423504:2881423700, ack 1650496469, win 148, length 196 02:53:59.853052 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 196, win 256, length 0 02:54:00.807875 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 196:472, ack 1, win 148, length 276 02:54:01.054256 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 472, win 255, length 0 02:54:01.325682 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 2940033849:2940034320, ack 1531971463, win 16425, length 471 02:54:01.325704 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 471, win 330, length 0 02:54:01.425955 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 1:1255, ack 471, win 330, length 1254 02:54:01.666682 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 1255, win 16111, length 0 02:54:01.808963 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 472:1164, ack 1, win 148, length 692 02:54:02.055668 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 1164, win 252, length 0 02:54:02.810003 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 1164:1408, ack 1, win 148, length 244 02:54:03.056578 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 1408, win 251, length 0 02:54:03.326481 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 471:942, ack 1255, win 16111, length 471 02:54:03.326503 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 942, win 330, length 0 02:54:03.426732 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 1255:2344, ack 942, win 330, length 1089 02:54:03.667909 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 2344, win 16425, length 0 02:54:03.811075 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 1408:2084, ack 1, win 148, length 676 02:54:04.057423 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 2084, win 256, length 0 02:54:04.812114 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2084:2344, ack 1, win 148, length 260 02:54:05.058459 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 2344, win 255, length 0 02:54:05.327108 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 942:1413, ack 2344, win 16425, length 471 02:54:05.327130 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 1413, win 330, length 0 02:54:05.427367 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 2344:3263, ack 1413, win 330, length 919 02:54:05.667152 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 3263, win 16195, length 0 02:54:05.813173 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2344:3020, ack 1, win 148, length 676 02:54:05.997797 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 246 02:54:05.997807 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997819 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997823 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 239 02:54:05.997827 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 244 02:54:05.997831 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997835 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243 02:54:05.997838 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997841 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 241 02:54:05.997850 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997853 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243 02:54:05.997857 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243

routing table is set ok i think

root@debian:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 0 0 0 eth0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lo 239.255.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lo 239.255.1.0 0.0.0.0 255.255.255.0 U 0 0 0 lo

CONF used

------------ TUNING -------------

card=0

The Transponder frequency

freq=12092

The polarisation (can be h, v, l, r)

pol=h

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the defined channels)

autoconfiguration=partial

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234

Do we need to change the default multicast TTL (if you have routers, default value : 2) ?

multicast_iface4=eth0

multicast_ttl=10

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10

---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite the PAT pid

rewrite_pat=1

---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will be used

cam_number=2

----------------------- THE CHANNELS ---------------------

Configuration for 12 channels

Channel number : 0

ip=239.255.0.0 port=1234 name=Mooz Dance HD service_id=11001 pids=5001 5101 5201

Channel number : 1

ip=239.255.0.1 port=1234 name=AXN White cam_pmt_pid=5002 service_id=11002 pids=5002 5102 5202 5302 5402 5502 5602 5702 5802 5902 oscam=1

Channel number : 2

ip=239.255.0.2 port=1234 name=AXN Black cam_pmt_pid=5003 service_id=11003 pids=5003 5103 5203 5303 5403 5503 5603 5703 5803 5903 oscam=1

Channel number : 3

ip=239.255.0.3 port=1234 name=AXN CE cam_pmt_pid=5004 service_id=11004 pids=5004 5104 5204 5304 5404 5604 5704 oscam=1

Channel number : 4

ip=239.255.0.4 port=1234 name=AXN Romania cam_pmt_pid=5005 service_id=11005 pids=5005 5105 5205 5305 5405 oscam=1

Channel number : 5

ip=239.255.0.5 port=1234 name=AXN Czech cam_pmt_pid=5006 service_id=11006 pids=5006 5106 5206 5306 oscam=1

Channel number : 6

ip=239.255.0.6 port=1234 name=Mooz Dance service_id=11007 pids=5007 5107 5207

Channel number : 7

ip=239.255.0.7 port=1234 name=Inedit TV service_id=11008 pids=5008 5108 5208

Channel number : 8

ip=239.255.0.8 port=1234 name=TVSudEst service_id=11009 pids=5009 5109 5209

Channel number : 9

ip=239.255.0.9 port=1234 name=Mynele TV service_id=11010 pids=5010 5110 5210

Channel number : 10

ip=239.255.0.10 port=1234 name=TV Sonce service_id=11011 pids=5011 5111 5211

Channel number : 11

ip=239.255.0.11 port=1234 name=TV Sutel service_id=11013 pids=5013 5113 5213

End of config file

braice commented 10 years ago

Hello

You are dumping on the IP address of your ethernet card but you route multicast on the lo (still the SAP seems to be seen) and you are using special multicast adresses 239.255

is there a reason for that ?

6.1 http://tools.ietf.org/html/rfc2365#section-6.1. The IPv4 Local Scope -- 239.255.0.0/16

239.255.0.0/16 is defined to be the IPv4 Local Scope. The Local Scope is the minimal enclosing scope, and hence is not further divisible. Although the exact extent of a Local Scope is site dependent, locally scoped regions must obey certain topological constraints. In particular, a Local Scope must not span any other scope boundary. Further, a Local Scope must be completely contained within or equal to any larger scope. In the event that scope regions overlap in area, the area of overlap must be in its own local scope. This implies that any scope boundary is also a boundary for the Local Scope. The more general topological requirements for administratively scoped regions are discussed below.

2014-05-10 10:05 GMT+02:00 ovidiu notifications@github.com:

with full autoconfig i have multicast traffic but channels are having bottlenecks with partial config when i tcpdump for check traffic i got no multicast packets just root@debian:~# tcpdump -n host 192.168.50.2 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 02:53:59.806751 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2881423504:2881423700, ack 1650496469, win 148, length 196 02:53:59.853052 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 196, win 256, length 0 02:54:00.807875 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 196:472, ack 1, win 148, length 276 02:54:01.054256 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 472, win 255, length 0 02:54:01.325682 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 2940033849:2940034320, ack 1531971463, win 16425, length 471 02:54:01.325704 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 471, win 330, length 0 02:54:01.425955 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 1:1255, ack 471, win 330, length 1254 02:54:01.666682 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 1255, win 16111, length 0 02:54:01.808963 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 472:1164, ack 1, win 148, length 692 02:54:02.055668 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 1164, win 252, length 0 02:54:02.810003 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 1164:1408, ack 1, win 148, length 244 02:54:03.056578 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 1408, win 251, length 0 02:54:03.326481 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 471:942, ack 1255, win 16111, length 471 02:54:03.326503 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 942, win 330, length 0 02:54:03.426732 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 1255:2344, ack 942, win 330, length 1089 02:54:03.667909 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 2344, win 16425, length 0 02:54:03.811075 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 1408:2084, ack 1, win 148, length 676 02:54:04.057423 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 2084, win 256, length 0 02:54:04.812114 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2084:2344, ack 1, win 148, length 260 02:54:05.058459 IP 5.13.13.115.50203 > 192.168.50.2.22: Flags [.], ack 2344, win 255, length 0 02:54:05.327108 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [P.], seq 942:1413, ack 2344, win 16425, length 471 02:54:05.327130 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [.], ack 1413, win 330, length 0 02:54:05.427367 IP 192.168.50.2.8888 > 5.13.13.115.50483: Flags [P.], seq 2344:3263, ack 1413, win 330, length 919 02:54:05.667152 IP 5.13.13.115.50483 > 192.168.50.2.8888: Flags [.], ack 3263, win 16195, length 0 02:54:05.813173 IP 192.168.50.2.22 > 5.13.13.115.50203: Flags [P.], seq 2344:3020, ack 1, win 148, length 676 02:54:05.997797 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 246 02:54:05.997807 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997819 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997823 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 239 02:54:05.997827 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 244 02:54:05.997831 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997835 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243 02:54:05.997838 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997841 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 241 02:54:05.997850 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 242 02:54:05.997853 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243 02:54:05.997857 IP 192.168.50.2.53388 > 224.2.127.254.9875: UDP, length 243

routing table is set ok i think

root@debian:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 0 0 0 eth0 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 224.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lo 239.255.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lo 239.255.1.0 0.0.0.0 255.255.255.0 U 0 0 0 lo

CONF used

------------ TUNING -------------

card=0

The Transponder frequency

freq=12092

The polarisation (can be h, v, l, r)

pol=h

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the

defined channels) autoconfiguration=partial

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234 #

Do we need to change the default multicast TTL (if you have routers,

default value : 2) ?

multicast_iface4=eth0

multicast_ttl=10 #

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1 #

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10 ---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite

the PAT pid

rewrite_pat=1

# ---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will

be used

cam_number=2

----------------------- THE CHANNELS ---------------------

Configuration for 12 channels

Channel number : 0

ip=239.255.0.0 port=1234 name=Mooz Dance HD service_id=11001 pids=5001 5101 5201

Channel number : 1

ip=239.255.0.1 port=1234 name=AXN White cam_pmt_pid=5002 service_id=11002 pids=5002 5102 5202 5302 5402 5502 5602 5702 5802 5902 oscam=1

Channel number : 2

ip=239.255.0.2 port=1234 name=AXN Black cam_pmt_pid=5003 service_id=11003 pids=5003 5103 5203 5303 5403 5503 5603 5703 5803 5903 oscam=1

Channel number : 3

ip=239.255.0.3 port=1234 name=AXN CE cam_pmt_pid=5004 service_id=11004 pids=5004 5104 5204 5304 5404 5604 5704 oscam=1

Channel number : 4

ip=239.255.0.4 port=1234 name=AXN Romania cam_pmt_pid=5005 service_id=11005 pids=5005 5105 5205 5305 5405 oscam=1

Channel number : 5

ip=239.255.0.5 port=1234 name=AXN Czech cam_pmt_pid=5006 service_id=11006 pids=5006 5106 5206 5306 oscam=1

Channel number : 6

ip=239.255.0.6 port=1234 name=Mooz Dance service_id=11007 pids=5007 5107 5207

Channel number : 7

ip=239.255.0.7 port=1234 name=Inedit TV service_id=11008 pids=5008 5108 5208

Channel number : 8

ip=239.255.0.8 port=1234 name=TVSudEst service_id=11009 pids=5009 5109 5209

Channel number : 9

ip=239.255.0.9 port=1234 name=Mynele TV service_id=11010 pids=5010 5110 5210

Channel number : 10

ip=239.255.0.10 port=1234 name=TV Sonce service_id=11011 pids=5011 5111 5211

Channel number : 11

ip=239.255.0.11 port=1234 name=TV Sutel service_id=11013 pids=5013 5113 5213

End of config file

— Reply to this email directly or view it on GitHubhttps://github.com/braice/MuMuDVB/issues/63 .

ovidiu31 commented 10 years ago

Bonjour Braice

Yes im using 239.255 class ip's because the QAM modulator which im using doesn't allow me to use another type of ip addresses. Could you please advise in this specific case how should i setup multicast routes?

at this moment in rc.local i have

ifconfig lo multicast ip route add 239.255.0.0/24 dev lo src 127.0.0.1 ip route add 239.255.1.0/24 dev lo src 127.0.0.1 ip route flush cache

Should be different?

With full autoconfig i have DVR buffer overrun errors

braice commented 10 years ago

Ok some more question

How your cam modulated is connected ? it seems that you send the multicast trafic on the lo interface, is that what you really want ? You can say to MuMuDVB which interface send the multicast traffic to, see the readme_conf

You can also use iptraf to see the amount of traffic on each interface.

Concerning DVR error, try to increase DVR buffer size.

Best regards

2014-05-11 9:26 GMT+02:00 ovidiu notifications@github.com:

Bonjour Braice

Yes im using 239.255 class ip's because the QAM modulator which im using doesn't allow me to use another type of ip addresses. Could you please advise in this specific case how should i setup multicast routes?

at this moment in rc.local i have

ifconfig lo multicast ip route add 239.255.0.0/24 dev lo src 127.0.0.1 ip route add 239.255.1.0/24 dev lo src 127.0.0.1 ip route flush cache

Should be different?

With full autoconfig i have DVR buffer overrun errors

— Reply to this email directly or view it on GitHubhttps://github.com/braice/MuMuDVB/issues/63#issuecomment-42764074 .

ovidiu31 commented 10 years ago

Thank you for reading and helping out Braice.

So the equation is simple , i have 1) system (pc) with a dual tunner pcie (TBS) and 1 eth0 gigabit interface (192.168.50.2) 2) router TP Link gigabit (multicast capable) (192.168.50.1) 3) qam modulator (gigabit) (192.168.50.3) (multicast ip class 239.x.x.x only)

I can use a direct conection pc -> qam modulator with a cross cable to eliminate de router and to have clean gigabit badwidth between pc and qam.

What i need Braice is 2 example conf files for tuner 1 and tuner 2 with some exact parameters to be able to broadcast at least 5 channels from one tuner (freq 12092 V thor 1W) and 5 channels from second tuner(freq 11938 H thor 1w) without bottlenecks.

I mean im able to do this but for some reason i have some bottlenecks and streams are not working fine ( i have signal quality 96%) so imo the problem is networking related , mostlikely because of the huge traffic generated by multicast.

how much can i increase the buffer size? eliminating the router could be a helpfull thing? is there any other specific option in the conf file that can help to optimise the multicast traffic and avoid bottlenecks?

Thank you

braice commented 10 years ago

Hello

try anything but 239.255 like 239.100

Also route the multicast on the eth0 interface

For DVR buffer see http://www.mumudvb.net/doc/mumudvb-2.0.0/README_CONF.html#_various_parameters dvr_buffer_size option

I'll provide you example files tomorrow but meanwhile I hope these few advises will be helpful

Best

2014-05-11 17:23 GMT+02:00 ovidiu notifications@github.com:

Thank you for reading and helping out Braice.

So the equation is simple , i have 1) system (pc) with a dual tunner pcie (TBS) and 1 eth0 gigabit interface (192.168.50.2) 2) router TP Link gigabit (multicast capable) (192.168.50.1) 3) qam modulator (gigabit) (192.168.50.3) (multicast ip class 239.x.x.x only)

I can use a direct conection pc -> qam modulator with a cross cable to eliminate de router and to have clean gigabit badwidth between pc and qam.

What i need Braice is 2 example conf files for tuner 1 and tuner 2 with some exact parameters to be able to broadcast at least 5 channels from one tuner (freq 12092 V thor 1W) and 5 channels from second tuner(freq 11938 H thor 1w) without bottlenecks.

I mean im able to do this but for some reason i have some bottlenecks and streams are not working fine ( i have signal quality 96%) so imo the problem is networking related , mostlikely because of the huge traffic generated by multicast.

how much can i increase the buffer size? eliminating the router could be a helpfull thing? is there any other specific option in the conf file that can help to optimise the multicast traffic and avoid bottlenecks?

Thank you

— Reply to this email directly or view it on GitHubhttps://github.com/braice/MuMuDVB/issues/63#issuecomment-42773446 .

braice commented 10 years ago

Some news on this issue ?

2014-05-11 23:01 GMT+02:00 Brice Dubost braice@braice.net:

Hello

try anything but 239.255 like 239.100

Also route the multicast on the eth0 interface

For DVR buffer see

http://www.mumudvb.net/doc/mumudvb-2.0.0/README_CONF.html#_various_parameters dvr_buffer_size option

I'll provide you example files tomorrow but meanwhile I hope these few advises will be helpful

Best

2014-05-11 17:23 GMT+02:00 ovidiu notifications@github.com:

Thank you for reading and helping out Braice.

So the equation is simple , i have 1) system (pc) with a dual tunner pcie (TBS) and 1 eth0 gigabit interface (192.168.50.2) 2) router TP Link gigabit (multicast capable) (192.168.50.1) 3) qam modulator (gigabit) (192.168.50.3) (multicast ip class 239.x.x.x only)

I can use a direct conection pc -> qam modulator with a cross cable to eliminate de router and to have clean gigabit badwidth between pc and qam.

What i need Braice is 2 example conf files for tuner 1 and tuner 2 with some exact parameters to be able to broadcast at least 5 channels from one tuner (freq 12092 V thor 1W) and 5 channels from second tuner(freq 11938 H thor 1w) without bottlenecks.

I mean im able to do this but for some reason i have some bottlenecks and streams are not working fine ( i have signal quality 96%) so imo the problem is networking related , mostlikely because of the huge traffic generated by multicast.

how much can i increase the buffer size? eliminating the router could be a helpfull thing? is there any other specific option in the conf file that can help to optimise the multicast traffic and avoid bottlenecks?

Thank you

— Reply to this email directly or view it on GitHubhttps://github.com/braice/MuMuDVB/issues/63#issuecomment-42773446 .

ovidiu31 commented 10 years ago

Bonjour Braice

Please have a look to these 2 configs and tell me please if something wrong asking because if i set parameter multicast_iface4=eth0 starting to receive buffer run errors not matter how big is the DVR buffer set. At the moment is stabilised with full auto config but i would like to choose some specific channels only to be multicasted not all the channels from transponder.

Thank you

CONFIG 1

------------ TUNING -------------

card=1

The Transponder frequency

freq=12265

The polarisation (can be h, v, l, r)

pol=V

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the defined channels)

autoconfiguration=partial #

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234 #

Do we need to change the default multicast TTL (if you have routers, default value : 2) ?

multicast_ttl=10 multicast_iface4=eth0 #

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1 #

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10

---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite the PAT pid

rewrite_pat=1

#

---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will be used

cam_number=2

----------------------- THE CHANNELS ---------------------

End of global part

#

Configuration for 16 channels

Channel number : 0

ip=239.255.1.0 port=1234 name=Eurosport cam_pmt_pid=100 service_id=30901 pids=100 101 110 111 112 113 120 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 1

ip=239.255.1.1 port=1234 name=MTV Music cam_pmt_pid=150 service_id=30902 pids=150 151 162 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 2

ip=239.255.1.2 port=1234 name=Discovery Channel cam_pmt_pid=200 service_id=30903 pids=200 201 210 211 212 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 3

ip=239.255.1.3 port=1234 name=Viasat Explorer cam_pmt_pid=250 service_id=30904 pids=250 251 259 261 262 273 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 4

ip=239.255.1.4 port=1234 name=CBS Reality cam_pmt_pid=300 service_id=30905 pids=300 301 310 311 312

Channel number : 5

ip=239.255.1.5 port=1234 name=Test cam_pmt_pid=350 service_id=30906 pids=350 351 360 361 362 363

Channel number : 6

ip=239.255.1.6 port=1234 name=SuperTV2 cam_pmt_pid=400 service_id=30907 pids=400 401 410

Channel number : 7

ip=239.255.1.7 port=1234 name=National Geographic RO cam_pmt_pid=450 service_id=30908 pids=450 451 463 473 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 8

ip=239.255.1.8 port=1234 name=Daring!TV cam_pmt_pid=500 service_id=30909 pids=500 501 512

Channel number : 9

ip=239.255.1.9 port=1234 name=Pro TV cam_pmt_pid=550 service_id=30910 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 10

ip=239.255.1.10 port=1234 name=Sport5 cam_pmt_pid=600 service_id=30911 pids=600 601 611

Channel number : 11

ip=239.255.1.11 port=1234 name=FEM3 cam_pmt_pid=650 service_id=30912 pids=650 651 660

Channel number : 12

ip=239.255.1.12 port=1234 name=JOJ Plus cam_pmt_pid=700 service_id=30913 pids=700 701 714

Channel number : 13

ip=239.255.1.13 port=1234 name=Cinemax2 cam_pmt_pid=750 service_id=30914 pids=750 751 760 761 762 763 770 771 772 773

Channel number : 14

ip=239.255.1.14 port=1234 name=Duna TV cam_pmt_pid=800 service_id=30916 pids=800 801 810 820 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 15

ip=239.255.1.15 port=1234 name=Pro TV International cam_pmt_pid=850 service_id=30917 pids=850 851 863 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

End of config file

CONFIG 2

------------ TUNING -------------

card=0

The Transponder frequency

freq=11727

The polarisation (can be h, v, l, r)

pol=V

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the defined channels)

autoconfiguration=partial #

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234 multicast_ipv4=1

multicast_iface4=eth0

multicast_ttl=2

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1 #

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10

---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite the PAT pid

rewrite_pat=1

#

---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will be used

cam_number=2

----------------------- THE CHANNELS ---------------------

Configuration for 18 channels

Channel number : 7

ip=239.255.0.7 port=1234 name=HBO cam_pmt_pid=100 service_id=30101 pids=100 101 110 112 119 120 oscam=1

Channel number : 8

ip=239.255.0.8 port=1234 name=NOVA Cinema cam_pmt_pid=150 service_id=30102 pids=150 151 161 170

Channel number : 10

ip=239.255.0.10 port=1234 name=Sport1 cam_pmt_pid=250 service_id=30104 pids=250 251 260 oscam=1

Channel number : 11

ip=239.255.0.11 port=1234 name=CT1 cam_pmt_pid=350 service_id=30106 pids=350 351 361 370

Channel number : 12

ip=239.255.0.12 port=1234 name=TV Markiza cam_pmt_pid=400 service_id=30107 pids=400 401 414 420

Channel number : 13

ip=239.255.0.13 port=1234 name=TA3 cam_pmt_pid=450 service_id=30108 pids=450 451 464

Channel number : 14

ip=239.255.0.14 port=1234 name=Prima TV cam_pmt_pid=500 service_id=30109 pids=500 501 511 520 oscam=1

Channel number : 17

ip=239.255.0.17 port=1234 name=TV Paprika cam_pmt_pid=650 service_id=30112 pids=650 651 660 661 670 oscam=1

End of config file

braice commented 10 years ago

Hello why not using autoconf_sid_list to choose you channel

Also, is it working with channels in clear (without oscam) ?

Just to see if it is an oscam issue.

Best

2014-05-18 8:33 GMT+02:00 ovidiu notifications@github.com:

Bonjour Braice

Please have a look to these 2 configs and tell me please if something wrong asking because if i set parameter multicast_iface4=eth0 starting to receive buffer run errors not matter how big is the DVR buffer set. At the moment is stabilised with full auto config but i would like to choose some specific channels only to be multicasted not all the channels from transponder.

Thank you

CONFIG 1

------------ TUNING -------------

card=1

The Transponder frequency

freq=12265

The polarisation (can be h, v, l, r)

pol=V

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the

defined channels) autoconfiguration=partial #

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234 #

Do we need to change the default multicast TTL (if you have routers,

default value : 2) ? multicast_ttl=10 multicast_iface4=eth0

#

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1 #

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10

---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite

the PAT pid

rewrite_pat=1

# ---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will

be used

cam_number=2

----------------------- THE CHANNELS ---------------------

End of global part

#

Configuration for 16 channels

Channel number : 0

ip=239.255.1.0 port=1234 name=Eurosport cam_pmt_pid=100 service_id=30901 pids=100 101 110 111 112 113 120 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 1

ip=239.255.1.1 port=1234 name=MTV Music cam_pmt_pid=150 service_id=30902 pids=150 151 162 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 2

ip=239.255.1.2 port=1234 name=Discovery Channel cam_pmt_pid=200 service_id=30903 pids=200 201 210 211 212 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 3

ip=239.255.1.3 port=1234 name=Viasat Explorer cam_pmt_pid=250 service_id=30904 pids=250 251 259 261 262 273 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 4

ip=239.255.1.4 port=1234 name=CBS Reality cam_pmt_pid=300 service_id=30905 pids=300 301 310 311 312

Channel number : 5

ip=239.255.1.5 port=1234 name=Test cam_pmt_pid=350 service_id=30906 pids=350 351 360 361 362 363

Channel number : 6

ip=239.255.1.6 port=1234 name=SuperTV2 cam_pmt_pid=400 service_id=30907 pids=400 401 410

Channel number : 7

ip=239.255.1.7 port=1234 name=National Geographic RO cam_pmt_pid=450 service_id=30908 pids=450 451 463 473 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 8

ip=239.255.1.8 port=1234 name=Daring!TV cam_pmt_pid=500 service_id=30909 pids=500 501 512

Channel number : 9

ip=239.255.1.9 port=1234 name=Pro TV cam_pmt_pid=550 service_id=30910 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 10

ip=239.255.1.10 port=1234 name=Sport5 cam_pmt_pid=600 service_id=30911 pids=600 601 611

Channel number : 11

ip=239.255.1.11 port=1234 name=FEM3 cam_pmt_pid=650 service_id=30912 pids=650 651 660

Channel number : 12

ip=239.255.1.12 port=1234 name=JOJ Plus cam_pmt_pid=700 service_id=30913 pids=700 701 714

Channel number : 13

ip=239.255.1.13 port=1234 name=Cinemax2 cam_pmt_pid=750 service_id=30914 pids=750 751 760 761 762 763 770 771 772 773

Channel number : 14

ip=239.255.1.14 port=1234 name=Duna TV cam_pmt_pid=800 service_id=30916 pids=800 801 810 820 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

Channel number : 15

ip=239.255.1.15 port=1234 name=Pro TV International cam_pmt_pid=850 service_id=30917 pids=850 851 863 oscam=1 ring_buffer_size=32768 decsa_delay=1500000 send_delay=2500000

End of config file

CONFIG 2

------------ TUNING -------------

card=0

The Transponder frequency

freq=11727

The polarisation (can be h, v, l, r)

pol=V

The symbol rate

srate=28000

the FEC

coderate=7/8

---------- AUTOCONFIGURATION -----------

We want the partial autoconfiguration (ie we discover the pids of the

defined channels) autoconfiguration=partial #

--------- NETWORKING --------------

Do we want to have the same port for all the channels ?

common_port=1234 multicast_ipv4=1

multicast_iface4=eth0

multicast_ttl=2

--------- SAP ANNOUNCES --------------

The sap announces are sent automatically with full autoconfiguration

Do we want to send the announces ?

sap=1 #

What is the default playlist group for the SAP announces (optionnal) ?

sap_default_group=My channels

Who is the organisation wich send the stream (optionnal) ?

sap_organisation=my_organisation

The intervall between the SAP announces in second (default 5)

sap_interval=10

---------- PAT REWRITING ----------

If some of the clients are set top boxes we will probably need to rewrite

the PAT pid

rewrite_pat=1

# ---------- SCRAMBLED CHANNELS ----------

Do we want hadware descrambling ?

cam_support=1

scam_support=1 ring_buffer_default_size=32768 decsa_default_delay=500000 send_default_delay=1500000

If you have multiple CAMs you can specify the number of the one wich will

be used

cam_number=2

----------------------- THE CHANNELS ---------------------

Configuration for 18 channels

Channel number : 7

ip=239.255.0.7 port=1234 name=HBO cam_pmt_pid=100 service_id=30101 pids=100 101 110 112 119 120 oscam=1

Channel number : 8

ip=239.255.0.8 port=1234 name=NOVA Cinema cam_pmt_pid=150 service_id=30102 pids=150 151 161 170

Channel number : 10

ip=239.255.0.10 port=1234 name=Sport1 cam_pmt_pid=250 service_id=30104 pids=250 251 260 oscam=1

Channel number : 11

ip=239.255.0.11 port=1234 name=CT1 cam_pmt_pid=350 service_id=30106 pids=350 351 361 370

Channel number : 12

ip=239.255.0.12 port=1234 name=TV Markiza cam_pmt_pid=400 service_id=30107 pids=400 401 414 420

Channel number : 13

ip=239.255.0.13 port=1234 name=TA3 cam_pmt_pid=450 service_id=30108 pids=450 451 464

Channel number : 14

ip=239.255.0.14 port=1234 name=Prima TV cam_pmt_pid=500 service_id=30109 pids=500 501 511 520 oscam=1

Channel number : 17

ip=239.255.0.17 port=1234 name=TV Paprika cam_pmt_pid=650 service_id=30112 pids=650 651 660 661 670 oscam=1

End of config file

— Reply to this email directly or view it on GitHubhttps://github.com/braice/MuMuDVB/issues/63#issuecomment-43432667 .

ovidiu31 commented 10 years ago

in Clear Cam everything seems to work ok no issues.

Can you please be more specific of how to use parameter : autoconf_sid_list to choose specific channels from a transponder.

braice commented 10 years ago

If you want the channels with service IDs 304 598 and 1345 just do

autoconf_sid_list=304 598 1345 autoconf=full

Best regards

2014-05-26 11:10 GMT+02:00 ovidiu notifications@github.com:

in Clear Cam everything seems to work ok no issues.

Can you please be more specific of how to use parameter : autoconf_sid_list to choose specific channels from a transponder.

— Reply to this email directly or view it on GitHub https://github.com/braice/MuMuDVB/issues/63#issuecomment-44171199.

ovidiu31 commented 10 years ago

braice close this as it is solved.

braice commented 10 years ago

closed

2014-08-03 10:24 GMT+02:00 ovidiu notifications@github.com:

braice close this as it is solved.

— Reply to this email directly or view it on GitHub https://github.com/braice/MuMuDVB/issues/63#issuecomment-50984954.