kevinbird61 / p4-researching

Testbed/Tutorials/Researching work on P4.

p4-researching

My Researching work on P4.

Notice: Current testing environment are not based on the latest version of P4. You can using the scripts under docker/ to build a docker image for these tests. And all the examinations are running on software switch, a.k.a "bmv2", and I use simple_switch_grpc as demonstration.

Environment Setting

Before getting started with P4 programming, we need a P4-capabled environment for running those scenario. And this repository summarize several methods and provide several way to accomplish.

• Build sucessfully with Ubuntu 16.04.05:
  • Installation scripts - P4
  • (Optional) Installation script - ONOS
• Also you can build your own test environment in docker:
  • Installation for Docker
  • Build your own P4 testbed with docker image
• Using P4 virtual machine (via Oracle VirtualBox):
  • P4.ova download : Completed P4 environment (Updated at: 2018/9/30).
  • P4 (only with deps).ova download : For develop environment of P4-related tools.

---

About this repository

P4 (with Mininet)

• More details under src/
• Contain lots of P4 practices and scenarios, which based on the open source software switch - BMv2 and mininet, with P4Runtime support to finish those work.

Notice:

v0 users: You can found some tutorials in branch:tutorials

v1 users: Use the master branch directly.

P4 with ONOS

Learning how to build an ONOS application which support P4. See more detail under onos/

Tracing P4Runtime

• Look here, have some diagram about P4Runtime's dependencies.

Build network namespace

• If you don't want to use mininet, you can use ip netns instead.
• Under net/, have a demo script for building several network namespace.

Learning Materials

• Provide some learning resources about Networking, which located in course/.
• Welcome to contribute!

---

Author

National Cheng Kung University, 瞿旭民 (Kevin Cyu), [email protected]

Activities

• (2018/09/12) DigitalOcean - Hsinchu: Learning P4 from example (slide), (meetup.com)
• (2018/12/08) SDN x Cloud Native Taiwan User Group - P4 Intro & Demonstration (slide), (kktix.com)

---

Reference

• p4.org - P4_16 Spec - v1.0.0
• p4.org - P4 PSA Spec - v1.0.0
  • v1model.p4
  • psa.p4
• p4.org - P4Runtime Spec - v1.0.0
  • v1/p4runtime.proto
  • v1/p4data.proto
  • config/v1/p4info.proto
  • config/v1/p4types.proto
• p4.org - In-band Network Telemetry(INT) Dataplane Specification
• p4.org - Telemetry Report Format Specification
• p4lang/tutorials
• p4lang/p4factory/apps/int

p4-researching's Issues

packet out not performed

I am using the learning switch and I noticed in the s1.log log and also in the controller processing (messages left by the controller after starting it) that the processing (while true) does not end in all received packets (packet in), or that is, the final message is not displayed at all packet-in. As if processing is stuck. The problem occurs when s1.PacketOut (packetout) is executed. Any idea why?

Monitor support

• using python + matplotlib to plot the result monitor.
• using python + web application to support real-time monitor.

Any scenario or example that using P4 is welcome!

If you have any SDN-related scenario that using P4/OpenFlow with software switch and controller, feel free to send Pull Request to master, which your scenario is under src/<your_scenario_name>.

advanced-topo pingall not working

Hi @kevinbird61, thanks for sharing this repo. I've been exploring some of the folders in src/fundamental/. I tested out basic-tutorial-switch and learning-switch, and they are working well. However, when testing advanced-topo, the pingall is not working correctly.

I did not change any code. I only used the provided scripts ./build.sh and make controller.

Also, another thing is that for basic-tutorial-switch, when I try to change the topology.json to my own topology, and also update the controller to install the correct rules, then it does not work as well. I am unable to ping any hosts. Any idea why this might happen?

Thanks!

Tutorials or Courses

Any tutorials or courses are welcome, too!
You can create a folder under courses/<your_tutorals_or_courses_name> for your precious materials!

learning switch loop after multiple switches

Greetings,

I am using your p4 learning switch program, but I have a problem regarding the multicast action. When I try to add another switch in the topology, I confront with loops. What is the meaning of the multicast in your controller and do you know if I can avoid the loops?

Regards

Adonis Chatzivasiliou

Example in-band-network-telemetry

I'm testing the example of in-band-network-telemetry but pingall does not work. Can you give me an example of execution?

Makefile Error.

After fixing the typo, running make command and then the error log shown below:

int-transit.p4(171): [--Wwarn=uninitialized_out_param] warning: out parameter normal_meta may be uninitialized when IngressDeparserImpl terminates
    out metadata normal_meta,
                 ^^^^^^^^^^^
int-transit.p4(167)
control IngressDeparserImpl(
        ^^^^^^^^^^^^^^^^^^^
int-transit.p4(767): error: package PSA_Switch: main package does not match the expected model
)main;
 ^^^^
error: Are you using an up-to-date v1model.p4?
int-transit.p4(767): error: package PSA_Switch: main package does not match the expected model
)main;
 ^^^^
error: Are you using an up-to-date v1model.p4?
Makefile:4: recipe for target 'int' failed
make: *** [int] Error 1

And checking out the p4c/psa.p4 (L681), still can't find why the error said can not match "main" package.

---

Another try: using p4c-bm2-psa to compile, still can't fix the problem, another error message:

p4c-bm2-psa --std p4-16 -o int.json \
        --p4runtime-file int.p4info \
        --p4runtime-format text int-transit.p4
int-transit.p4(171): [--Wwarn=uninitialized_out_param] warning: out parameter normal_meta may be uninitialized when IngressDeparserImpl terminates
    out metadata normal_meta,
                 ^^^^^^^^^^^
int-transit.p4(167)
control IngressDeparserImpl(
        ^^^^^^^^^^^^^^^^^^^
make: *** [int] Segmentation fault: 11