In the text in section 3.3 of the manual it says: Let’s give it tag ID 100

Then in the example, has switched to tag id 10:

  {
    "type": "MATCH_TAGS_DIFFERENCE",
    "not": false,
    "or": false,
    "id": 10,
    "value": 0
  }, 

And following paragraph: difference between tags with tag ID 10 is zero

Looks like a typo and all should either be 10 or 100.

It would be very useful if we could include some code in the Java example to show how to use the sockets to send/receive data in streams. Thanks

We've done quite a bit refreshing our LACP/MC-LAG support. We should document it in docs/configuration.rst and write a tutorial.

• what is the name of the switch for mirroring (name defined in the faucet.yaml, not dns, for example)
• the port that Poseidon uses for mirroring needs to be controlled by Faucet, therefore it needs to be an openflow port
• the port that Poseidon uses needs to be configured in faucet.yaml to be output_only: true and no native vlan (a port for mirroring from Faucet's perspective)
• Requiremen

Setting flags on all our targets is preferable to global flags via .bazelrc, because the later applies to ALL code, including external. This limits the options we can actually use. Enabling all warnings for example results in an useless torrent of compiler output from code we have no influence over. External code also does not always support instrumentation and breaks if compiled with, e.g., ASA

Hi,
I want to try this project on mylab.
But i didn't build. (readme file not enough for me)
Also I tried build with docker but not worked.

Is there any step-by-step user guide, how can i build and use?

Thanks.

As requested bt @kedmison , we beed a README file to explain where diagrams should be kept and include some pointers to how to use .svg files etc.

Lighty bootup emits information messages about timimg based on conversion to milliseconds. This is not always appropriate, as some things are at seconds-scale.
Unify all time tracking around Guava's Stopwatch, which performs automatic conversion, such that the timings are human-readable down to microseconds.