opensand team mailing list archive

[Jedrzej Gorski <andy.gorski.dev@xxxxxxxxx>]

Hi Dider,

I've manage to run my daemon through existing package installation. It
seams that my update works fine. In attached file you can find generated
patch. I used for it suggest command

$ cd opensand-trunk/
$ bzr diff > fix_bug_1051711.patch

If there is no suggestions for additional changes i'll make commit. Full
listing of changes is described in previous report.

$ bzr commit -m "Lack of consistent naming for AAL5/ATM plugin"

If you have any suggestion for next task, I'm ready to work on it :)

Regards,
Andy

2012/10/1 Didier Barvaux <didier.barvaux@xxxxxxxxxxxxxxxxxxxx>

> Andy,
>
> > I was working with source compilation. I did it with fresh Ubuntu
> > installation. Everything just to check if that set of changes which
> > I've made can be compiled. Compilation process goes well but for some
> > reason I can't start sand daemon. I know that there are some issues
> > but even then I wasn't able to start it properly. I did some
> > investigation about previous successful scenarios and I came to
> > conclusion that performing packages installation and making source
> > code compilation after that it might cover some issues with daemon.
> >
> > Question is what is a difference between these two approaches? What
> > needs to be done in order to start sand daemon properly?
>
> Doing compilation or installing packaging shall give you the same
> result. The main difference is that packaging automates some
> operations.
>
> The installation manual lists all the steps for both modes. I tested
> both procedures on fresh installations. Be careful to check all notes I
> added to workaround some bugs. I might however have miss something...
>
>
> > Please check attached log file. I did full source compilation for
> > single VM (sat). Manager is running but there is no sign of a daemon
> > of any kind.
>
> If you got trouble running the daemon, please run it manually without
> using the init script. Check any traces that may be printed on the
> console. Check also the system logs in /var/log/ for errors.
>
> Regards,
> Didier
>
> --
> Mailing list: https://launchpad.net/~opensand
> Post to     : opensand@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~opensand
> More help   : https://help.launchpad.net/ListHelp
>

=== modified file 'opensand-core/conf/core_global.conf'
--- opensand-core/conf/core_global.conf	2012-06-14 13:47:07 +0000
+++ opensand-core/conf/core_global.conf	2012-09-28 00:17:39 +0000
@@ -27,7 +27,7 @@
         </ip_options>
         <!-- The uplink/return link encapsulation schemes -->
         <up_return_encap_schemes>
-            <scheme pos="0" encap="ATM/AAL5" />
+            <scheme pos="0" encap="AAL5/ATM" />
         </up_return_encap_schemes>
         <!-- The downlink/forward link encapsulation schemes -->
         <down_forward_encap_schemes>

=== modified file 'opensand-core/conf/xsd/core_global.xsd'
--- opensand-core/conf/xsd/core_global.xsd	2012-06-14 13:47:07 +0000
+++ opensand-core/conf/xsd/core_global.xsd	2012-09-28 00:17:38 +0000
@@ -46,7 +46,7 @@
 
 <xsd:simpleType name="EncapScheme">
     <xsd:restriction base="xsd:string">
-        <xsd:enumeration value="ATM/AAL5" />
+        <xsd:enumeration value="AAL5/ATM" />
         <xsd:enumeration value="MPEG2-TS" />
         <xsd:enumeration value="ULE" />
         <xsd:enumeration value="GSE" />

=== removed file 'opensand-core/src/common/tests/icmp_28/aal5_atm.pcap'