Rare project developers

[mc36 <>]

hi,

On 8/23/22 22:55, Edgard da Cunha Pontes wrote:
> Hi everyone!
>
> After some time, I came back to this thread.
> I started creating the VMs in the virtualbox (with the one-line installation) 
> to get closer to the RENaaS topology. But I stopped at router r2 and did the 
> following steps:
>
> I created a debian/sid vm and compiled the freeRtr github repository.
> I ran the tests: ./tw.sh p4lang-rout211 other p4lang9.ini

excellent! that's the easiest way to go!

> I accessed routers r1, r5, r6, r7 and r8
nicee!

> But I could not access routers r2, r3 and r4.
the point is, these are just dataplanes... they even dont have config in the 
tst file:

r1 controls them, that's the main point of the whole feature... :)
if you're looking at ps aux | grep java, you'll find r1, r5..r8,
and if you ps aux | grep bin you'll see the 3 dataplanes all pointing to r1...

in r1, you'll find similar outputs like, and all the other sho p4 things got 
that optional (that is, hidden:) parameter

wifi>show p4lang p4 port-names ?
  <cr>
  [num] - forwarder number
  |     - output modifier

wifi>show p4lang p4 port-names 0
2022-08-23 23:01:03
num | name
1   | veth3a
0   | veth6b
2   | veth8b

wifi>show p4lang p4 port-names 1
2022-08-23 23:01:04
num | name
2   | eth0.151
3   | eth0.152
1   | eth0.167
0   | gre4t-cpuport
4   | wlan0
5   | wlan0-1
6   | wlan1

wifi>show p4lang p4 port-names 2
2022-08-23 23:01:05
num | name
3   | eth0.150
2   | eth0.151
1   | eth0.168
0   | gre4t-cpuport
4   | wlan0
5   | wlan0-1
6   | wlan1

wifi>show p4lang p4 port-names 3
2022-08-23 23:01:06
num | name
3   | eth0.150
2   | eth0.152
1   | eth0.166
0   | gre4t-cpuport
4   | wlan0
5   | wlan0-1
6   | wlan1

wifi>




> The goal was to understand the "controller r1 v9 9080 feature bundle mpls 
> route" settings that Gabriel had commented on.
>
> Is there any way to access the compiled configuration of these routers?
you configure them from r1... they're just forwarders, instructed by r1...
much like the single box version, you have freerouter and a dataplane...
but here, freerouter got the capability to control more dataplanes at once...
do the spf over the backplane, and propagate the computed tables...

so as i left the lab before the polka experiments: a eu-sized router, made of 
4 stacked pizzaboxes...
https://www.cisco.com/c/en/us/products/collateral/routers/carrier-routing-system/data_sheet_c78-726136.html
was the last i knew about with a similar feature, but that was limited to 1 
hop, whereas,
rare, thanks to the mpls based backplane, can have arbitrary long chassis 
chain...

or, you can build an arbitrarily big data center made of tofino boxes,
and you need to configure the whole dc at a single controlling router..
(3+ would be safe enough and that feature is also there: 
http://sources.freertr.org/cfg/conn-redun.tst
and was configured in the 4 pizzabox as a single stack experiment)

or the same if one finally builds a chassis based tofino switch: you'll have 
1 or 2 route processors,
and let's say 8 line cards, and hopefully some forwarding engines: a good 
design would be horizontal
line cards in the front and vertical forwarding engines in the back, and no 
backplane but connections...
the line cards could be made of 64x port capable tofino, 32 to the faceplate 
and 32 toward the forwarding engines...
or even smaller ones based on the 32 port tofino...

br,
cs