opensand_cli ethernet xml issues

[JohnFWeston]

Hi,

Just trying opensand for the first time, and had difficulty running the ethernet cli example. I had to correct a number of the xml files. Please find them as attached. I assume these are just a little out of date, and that other examples may suffer the same issues.

The most obscure issue was that in the infrastructure.xml example, the GW node picked up the last terminal section and interpreted that entry as the entity ID, and fails to start the GW.

Happy to formalise these changes and help with the project, but just be good to know if Im on the right track.

Please find attached my updates. Great project, very interesting!

BR
st.tar.gz
gw.tar.gz

John Weston

[Kniyl]

Hi,

I’m in the process of finalizing the update of the whole opensand_cli folder in an internal branch. I will have a look at your modifications to make sure I didn't miss anything. It should be available in dev in a short while.

In the meantime, you can use an hybrid solution where you make network to configure your interfaces properly and install the opensand-deploy packet to use the configuration frontend to generate proper XML files.

Regards

[JohnFWeston]

Hi Mathias, Thanks for the quick reply. Look forward to the updated dev branch, and happy to contribute any further findings. BR John

…

On Thu, Jul 20, 2023 at 6:48 PM Mathias Ettinger ***@***.***> wrote: Hi, I’m in the process of finalizing the update of the whole opensand_cli folder in an internal branch. I will have a look at your modifications to make sure I didn't miss anything. It should be available in dev in a short while. In the meantime, you can use an hybrid solution where you make network to configure your interfaces properly and install the opensand-deploy packet to use the configuration frontend to generate proper XML files. Regards — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJMP2VNO7HTH4KI3EWHARJLXRDWEHANCNFSM6AAAAAA2NSFCJQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>