opensand team mailing list archive
-
opensand team
-
Mailing list archive
-
Message #00144
Re: Platform capasity for UDP-packets!?
-
To:
opensand@xxxxxxxxxxxxxxxxxxx
-
From:
Julien BERNARD <jbernard@xxxxxxxxxxxxxxxxxxx>
-
Date:
Thu, 13 Feb 2014 11:56:56 +0100
-
In-reply-to:
<CAH5fdj8AC2XXsLKTxjsvNu4hn2HKffaHrZ=JTBiBDu7L79gsaA@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
Hi Jussi,
We have tested ping from ST1 to GW with
*iperf -c 192.168.18.42 -u -b 10m*
*iperf -c ***192.168.18.42* -u -b 60m
**iperf -c ***192.168.18.42* -u -b 100m *
If you are using the default IP configuration you should use
192.168.42.1 as destination address because with your command, you does
not send your traffic through OpenSAND.
With iperf it is recommended to use 192.168.42.3 that is the tun
interface address to be sure that the server report will be correctly
received.
Moreover, there is a lot of configuration parameters to change to expect
reaching high rates and return link is limited to approximately 70Mb/s:
65Mb/s CRA + 8Mb/s RBDC.
The configuration parameters to be changed are:
Global>global>up_return_band: increase bandwidth and symbol_rate in
carriers_distribution
ST1 >dvb_rcs_tal: increase rt_fixed_bandwidth (CRA), fifos size_max
(for BE if you don't use QoS) and max_rbdc
It seems even 100 bandwidth go trough without loss almost rate of
90Mbits/s. I´d like make sure that encapsulation really work? I
undestood that installation from packets includes these plugins.
For the encapsulation, by default you have AAL5/ATM on return link and
ULE/MPEG2-TS on forward link.
You can install the packets for GSE encapsulation that will be available
on forward link.
Regards,
--
Julien BERNARD
Viveris Technologies
+33 (0)5 61 00 31 84
Follow ups
References