Rare project developers

[mc36 <>]

hi,

On 8/11/22 12:09, mc36 wrote:
> so that particular knob is just a bonus port to open during the testing 
> process for the server p4lang:
> https://github.com/rare-freertr/freeRtr/blob/master/src/net/freertr/user/userTester.java#L1964
> https://github.com/rare-freertr/freeRtr/blob/master/src/net/freertr/user/userTester.java#L2026
> you can safely ignore it especially as this stuff finally abadoned because 
> the p4lang server
> now requires an unique ip to identify the connecting dataplane...

so after i've written these lines then started thinking about the missing 
pieces for this to work,
and i came up with the following changes: 
https://github.com/rare-freertr/freeRtr/commit/8e377850bebcff6975456a4a947a63784d3e195f
it's mostly about me sedding through the config files to put the new faked-ip 
parameter to the tests...
and some lines to implement this new parameter in the tcp2vrf -hw knob... if 
set, it'll mimic the source
ip of the new connections, and exactly this is what needed for one to be able 
to run the backplane stuff
within a single machine with the p4udp dataplane emulation:

cd src
./c.sh
cd ../misc/native
./c.sh
cd ../../src
./tw.sh p4lang-rout211 other p4lang9.ini

will spin up the test case for you: r1 will be the controlling freerouter 
who'll have 3 dataplanes connected...
r2, r3, r4 could be the previously described dataplane vm (there are several: 
bmv2 1.ini , dpdk 2.ini, ebpf/xdp 4.ini,
tofino asic emulator 3.ini) r5..t8 regular surrounding routers to perform the 
given test... here the difference from the
previous version is the 9.ini, it'll simply start the same forwarder logic 
found in the dpdk or pcap dataplanes, but
here it's coupled with a pure udp based packet io... this way it's quite 
resource efficient to run these kind of tests too..

br,
cs