← Back to team overview

opensand team mailing list archive

Re: opensand 1.0.0

 

Yannis,

Le 14/12/2012 13:14, thomasi@xxxxxxx a écrit :

Hello Julien.
Thank you for your quick response.

Your first advice, about using "sudo opensand_tun; sudo sand-daemon -f" really helped me a lot. I found that there was a problem with the daemon.conf file, where I should have added an lan_ipv6 address as well. Now I'm able to start deamon but lots of warnings arise. Also using ifconfig I dont see an opensand interface, just eth0, eth1 and lo.

/output of sand-daemon -f:
2012-12-14 13:56:01,691 - sand-daemon - WARNING - IPv4 forwarding on interface opensand is disabled, you won't be able to route packets toward WS behind this host [sand-daemon:215] 2012-12-14 13:56:01,692 - sand-daemon - WARNING - IPv4 forwarding on interface eth1 is disabled, you won't be able to route packets toward WS behind this host [sand-daemon:215] 2012-12-14 13:56:01,692 - sand-daemon - WARNING - IPv6 forwarding on interface eth1 is disabled, you won't be able to route packets toward WS behind this host [sand-daemon:223] 2012-12-14 13:56:01,692 - sand-daemon - WARNING - IPv4 ip_forward is disabled, you should enable it [sand-daemon:226] 2012-12-14 13:56:01,693 - sand-daemon - WARNING - wmem_max should be set to a value greater than 1048580 in order to support high bitrates through OpenSAND [sand-daemon:233] 2012-12-14 13:56:01,693 - sand-daemon - WARNING - rmem_max should be set to a value greater than 1048580 in order to support high bitrates through OpenSAND [sand-daemon:233] 2012-12-14 13:56:01,693 - sand-daemon - WARNING - wmem_default should be set to a value greater than 1048580 in order to support high bitrates through OpenSAND [sand-daemon:233] 2012-12-14 13:56:01,693 - sand-daemon - WARNING - rmem_default should be set to a value greater than 1048580 in order to support high bitrates through OpenSAND [sand-daemon:233]/

This part is only warning on some parameters for UDP buffers and IP forwarding. IP forwarding is necessary if you use workstations behind ST, UDP buffer length should be increased if you need to send high traffic throughputs. To enable IP forwarding set /proc/sys/net/IP_VERSION/conf/INTERFACE/forwarding to 1. To increase UDP buffer length, modify the /proc/sys/net/core/{rmem_max, rmem_default, wmem_max and wmem_default} values.

You were completely right about the second issue as well.
I have missed the part where I should copy the plugin scripts in manager's modules directory. As soon as I copied the files, the manager passed this step. Unfortunately, now crashes when loading the topology file. Below is the output:

/2012-12-14 14:02:16,418 - sand-manager - ERROR - failed to initialize OpenSAND Manager: need more than 1 value to unpack
Traceback (most recent call last):
  File "/usr/bin/sand-manager", line 110, in __init__
    self._model = Model(self._manager_log, options.scenario)
File "/usr/lib/python2.6/dist-packages/opensand_manager_core/opensand_model.py", line 96, in __init__
    self.load()
File "/usr/lib/python2.6/dist-packages/opensand_manager_core/opensand_model.py", line 144, in load
self.load_topology()
File "/usr/lib/python2.6/dist-packages/opensand_manager_core/opensand_model.py", line 177, in load_topology
    except IOError, (_, strerror):
ValueError: need more than 1 value to unpack/

The real error was masked behind this one that seems to be a bug. I think your problem is that the topology.conf and topology.xsd files are missing. Try to follow the part beginning with "Deploy some other opensand-core configuration files to MANAGER:" in the opensand-core installation (http://opensand.org/support/wiki/doku.php?id=installation_manual#build_and_install_module_opensand-core) this should help.


Finally, Im running 32bit ubuntu release and I would be more than happy to install openSAND from debs, but I need to use the v.1.0.0 because of this bug (https://bugs.launchpad.net/opensand/+bug/1015156) and the loss model plugin.

It should be really easier with the packages. I hope that we will be able to release a new version in early 2013 for more recent linux distributions and with 64 bits support.

The bug you mentioned was corrected in the 0.9.0 version (as you noticed below) but I forgot to mark it as released when the 0.9.0 version was created.
But you effectively need the 1.0.0 version for loss model plugin.
As it is written in release notes, the physical layer models are experimental so they are disabled by default. You can enable them easily clicking to the option on the manager configuration tab but you will have to take very a critical look on the results you got.

Thank you a lot for your help.

You're welcome.

Regards,

--
Julien



Follow ups

References