Thank you very much Christian,
I will give it a try and give you a feed back,

Kind Regards,

Mounir

On Tue, Nov 13, 2012 at 3:36 PM, Christian Esteve Rothenberg
<[email protected]> wrote:
> Mounir,
>
> find below an answer to your question.
>
> -Christian
>
>
>
> ---------- Forwarded message ----------
> From: Eder Leão Fernandes <[email protected]>
> Date: Tue, Nov 13, 2012 at 3:30 PM
> Subject: Re: [openflow-discuss] Announcing OpenFlow version 1.3 software
> switch and controller prototypes
> To: Mounir Azizi <[email protected]>
> Cc: Christian Esteve Rothenberg <[email protected]>,
> "[email protected]" <[email protected]>
>
> Hi,
> The reason for this problem was a missing file in the include directory. I
> just uploaded it on Github, so please make a git pull and try to compile
> again.
> Regards,
> Eder.
>
> On 12 November 2012 19:53, Mounir Azizi <[email protected]> wrote:
>>
>> Dear Christian,
>>
>> thank you for sharing this.
>
>>
>> I have problem when doing "make" for the nox13oflib, can you please
>> advice on how to resolve it.
>>
>> openflow@openflow-VBox:~/nox13oflib/build$ make
>> make  all-recursive
>> make[1]: Entering directory `/home/openflow/nox13oflib/build'
>> Making all in src
>> make[2]: Entering directory `/home/openflow/nox13oflib/build/src'
>> Making all in libopenflow
>> make[3]: Entering directory
>> `/home/openflow/nox13oflib/build/src/libopenflow'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/home/openflow/nox13oflib/build/src/libopenflow'
>> Making all in oflib-exp
>> make[3]: Entering directory
>> `/home/openflow/nox13oflib/build/src/oflib-exp'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/oflib-exp'
>> Making all in oflib
>> make[3]: Entering directory `/home/openflow/nox13oflib/build/src/oflib'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/oflib'
>> Making all in include
>> make[3]: Entering directory `/home/openflow/nox13oflib/build/src/include'
>> make[3]: *** No rule to make target `openflow/openflow-netlink.h',
>> needed by `all-am'.  Stop.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/include'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/home/openflow/nox13oflib/build/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/openflow/nox13oflib/build'
>> make: *** [all] Error 2
>> openflow@openflow-VBox:~/nox13oflib/build$
>>
>> Kind Regards,
>>
>> Mounir Azizi
>>
>> On Fri, Nov 9, 2012 at 8:41 PM, Christian Esteve Rothenberg
>> <[email protected]> wrote:
>> > Dear OpenFlow fellows,
>> >
>> > giving continuity to the OpenFlow 1.X developments by Ericsson and
>> > CPqD (cf. v1.2 Tool-Kit [1]) we are glad to announce the release of a
>> > version 1.3 software switch [2] (based on Stanford reference design
>> > extended by Ericsson for v1.1) and a companion NOX OpenFlow 1.3
>> > controller [3] (based on NOX Zaku and
>> > using oflib 1.3 of the software switch).
>> >
>> > Find below a quick user's guide.
>> >
>> > Early users, feedback, and contributions are very welcome!
>> >
>> >
>> > HOW-TO
>> >
>> > - For further instructions on how compile and deploy, please go to the
>> > READMEs of the software switch  [5] and NOXv1.3 [6].
>> > - See the learning switch and discovery apps examples on how to use
>> > oflib v1.3 APIs.
>> > - For quick testing you can use the dpctl switch built-in controller
>> > and watch the wireshark OFPv1.3 control traffic.
>> >
>> > CAVEATS
>> >
>> > - Performance: The software switch implementation prioritizes OpenFlow
>> > 1.3 feature compliance and overall correctness.
>> > - Feature completeness: See pending protocol optional features in the
>> > living TODO list [7]  based on Annex B.11 of the OpenFlow v1.3 spec
>> > [8]. Notably, the policy metering actions are not yet enforced in the
>> > data plane.
>> > - Limitations in dpctl: (no OXM mask support, lack of multipart
>> > messages,
>> > limited fields for set_field action)
>> > - Missing APIs in NOX to simplify access to oflib1.3
>> >
>> > NEXT STEPS
>> >
>> > - Complete implementation missing features (B.11.1, B.11.4, B.11.5,
>> > B.11.6). Please, track the TODO list [7].
>> > - Complete wireshark dissector OFP for newly introduced messages (e.g.
>> > flow metering messages) and some 1.2 pending decoding (e.g. stats
>> > bodies)
>> > - Extend dpctl
>> > - Testing: Interop with OpenFlow v1.3 controllers? OF-Test 1.3?
>> > - Put together a v.1.3 Tool-Kit in pre-configured VM (including
>> > Mininet with 1.3 components)
>> > - Make a github wiki page with detailed tutorials for OF1.X.
>> > - Performance optimization: Q1/2013
>> >
>> >
>> > REFERENCES
>> >
>> > [1]
>> > https://mailman.stanford.edu/pipermail/openflow-discuss/2012-July/003479.html
>> >
>> > [2] https://github.com/CPqD/ofsoftswitch13
>> >
>> > [3] https://github.com/CPqD/nox13oflib
>> >
>> > [4] https://github.com/CPqD/ofdissector/tree/of13
>> >
>> > [5] https://github.com/CPqD/ofsoftswitch13/blob/master/README.md
>> >
>> > [6] https://github.com/CPqD/nox13oflib/blob/master/README
>> >
>> > [7] https://github.com/CPqD/ofsoftswitch13/blob/master/TODO.md
>> >
>> > [8]
>> > https://www.opennetworking.org/images/stories/downloads/specification/openflow-spec-v1.3.0.pdf
>> >
>> >
>> > --
>> > Christian Esteve Rothenberg, Ph.D.
>> > Converged Networks Business Unit
>> > CPqD - Center for Research and Development in Telecommunications
>> > Tel. (+55 19) 3705 4479 / Cel. (+55 19) 8193-7087
>> > _______________________________________________
>> > openflow-discuss mailing list
>> > [email protected]
>> > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>> _______________________________________________
>> openflow-discuss mailing list
>> [email protected]
>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
>
> --
> Eder Leão Fernandes
> Bacharelado em Ciências de Computação
> Instituto de Ciências Matemáticas e de Computação
> Universidade de São Paulo
>
> --
> Christian Esteve Rothenberg, Ph.D.
> Converged Networks Business Unit
> CPqD - Center for Research and Development in Telecommunications
> Tel. (+55 19) 3705 4479 / Cel. (+55 19) 8193-7087
>
>
> On Mon, Nov 12, 2012 at 11:16 PM, Mounir Azizi <[email protected]>
> wrote:
>>
>> Dear community,
>>
>> I'm trying to install nox13oflib on my ubuntu 11.10 server, but I have
>> problem when doing "make" for the nox13oflib, can you please advice on
>> how to resolve it.
>>
>> openflow@openflow-VBox:~/nox13oflib/build$ make
>> make  all-recursive
>> make[1]: Entering directory `/home/openflow/nox13oflib/build'
>> Making all in src
>> make[2]: Entering directory `/home/openflow/nox13oflib/build/src'
>> Making all in libopenflow
>> make[3]: Entering directory
>> `/home/openflow/nox13oflib/build/src/libopenflow'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory
>> `/home/openflow/nox13oflib/build/src/libopenflow'
>> Making all in oflib-exp
>> make[3]: Entering directory
>> `/home/openflow/nox13oflib/build/src/oflib-exp'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/oflib-exp'
>> Making all in oflib
>> make[3]: Entering directory `/home/openflow/nox13oflib/build/src/oflib'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/oflib'
>> Making all in include
>> make[3]: Entering directory `/home/openflow/nox13oflib/build/src/include'
>> make[3]: *** No rule to make target `openflow/openflow-netlink.h',
>> needed by `all-am'.  Stop.
>> make[3]: Leaving directory `/home/openflow/nox13oflib/build/src/include'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/home/openflow/nox13oflib/build/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/openflow/nox13oflib/build'
>> make: *** [all] Error 2
>> openflow@openflow-VBox:~/nox13oflib/build$
>>
>> Kind Regards,
>>
>> Mounir Azizi
>
>
>
>
> --
> Christian

Reply via email to