some success to link an emulated dataplane please?!

[mc36]

hihi,

its an other geant project leader speaking who is about to link a real 12tbps tofino based

or intel dodk based forwarder and its emulation... we had a mailings this summer but since

then seemingly you stopped responding me... the question is, did you succeeded populate

the dataplanes in freerouter through flowspec with a sample divert to vrf/interface rule,

and whats the exact reason why the police to 10mbps on a 100gbps is not enough

once you have the port ip level granurality to demo this on a "desk"?!

thanks in advance...

[mc36]

https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles/9.12.0/tofino2

we even support ipv4/ipv6 tcp tls.sni inspection for a long ago on the above mentioned devices equally on a dpdk.org based physical servers nicely fit to 1 or 2 rack unit servers' as smartnics... that was out of the scope of the geant compiler farms, the dataplanes (all) could be found here;

https://github.com/rare-freertr/freeRtr/tree/master/misc/p4bf <-- take a look and blame the flowspec profile, it arrived almost 1.5 years ago...... :)

https://github.com/rare-freertr/freeRtr/tree/master/misc/p4lang <--- is an on-desk asic emulator available for downloading from https://github.com/p4lang/behavioral-model and the p4c to compile the .p4 files...

the same api can be fed to a regular server as mentioned above, that means that once you're done with our code you can freely assume that it will run against the 12tbps intel asic based whiteboxes;

https://github.com/rare-freertr/freeRtr/tree/master/misc/native

the benchmarking code is pretty performant , on a single i7 mobile laptop core it can pass 120gbps!!!
and the same things are linked against the p4udp forwarder, this way you can freely build up a complete topology.... if you dont want to compile/link by hand, there is a fedore build farm doing this since years now; https://copr.fedorainfracloud.org/coprs/nucleo/freerouter/

i personally provide the debian builds plus the autoupgrade servers so these two seems an acceptable coverage...

regarding the bgp, hbone.hu feeds the project with full bgp since 2011 0-24; you can check yourself at www.nop.hu as a demo whatsmyip whatsmyaspath project, its a recent fun bgp monitoring development for the commons goods...

a quick reminde, the divert* will arrived to the todo.txt just im waiting for the good 2nd reason to plan the feature properly... the #1 feature is to fully support the bgp-ct (fingers crossed rfc soon)... here is a brief config guide from juniper on the topic;

https://community.juniper.net/blogs/kaliraj-vairavakkalai/2023/05/22/bgp-ct-interop-demo-eantc2023

http://eantc.de/fileadmin/eantc/downloads/events/2023/EANTC-InteropTest2023-TestReport.pdf find the eantc.de 2023 report about the interoperability of the idr-draft...

rare/freertr equally have support for the concurrent idr draft bgp-car since this spring so fingers crossed that will also have traces/proper support once your requirements also gets communicated as per on-list agreements in between us....