Skip to Content.
Sympa Menu

rare-dev - Re: [rare-dev] further negotiations in between the dataplane and freerouter...

Subject: Rare project developers

List archive

Re: [rare-dev] further negotiations in between the dataplane and freerouter...


Chronological Thread 
  • From: mc36 <>
  • To: , Alexander Gall <>
  • Cc: Frédéric LOUI <>, David Richardson <>
  • Subject: Re: [rare-dev] further negotiations in between the dataplane and freerouter...
  • Date: Fri, 15 Jul 2022 10:16:23 +0200



On 7/14/22 19:02, mc36 wrote:

well, now think about the above.. surely it's not too hard to export
everything belonging to a given set of ports but the other side will
be the loss in possibilities...

yup, yet another one... rare/freertr also can do route processor redundancy...
(it have config syncing, single master election, etc, etc, much like you
expect in brand boxes...)
https://files.fm/f/y6hcpz4js from http://www.freertr.org/present.html showing
it off...
in practice, you can create an instance with exactly the same interfaces, but
at different hosts...
it's easy nowadays as in -hw you can describe anything, and the p4emu process
also hides the names:

wifi>show redundancy
2022-07-15 10:07:24
iface | reach | state | prio | uptime | magic | heard
self | - | 3 | 10 | 23:54:18 | 1012481247 | -
ethernet96 | 3 | 2 | 1 | 23:52:47 | 334780719 | 00:00:00
ethernet97 | 3 | 2 | 5 | 23:54:02 | 740240790 | 00:00:00

wifi>show cdp neighbor
2022-07-15 10:07:27
interface | hostname | iface | ipv4 | ipv6
sdn0/0 | mchome | sdn905 | 10.1.1.49 | 2001:db8:1d::1

wifi>show p4lang p4 port-names 0
num | name
1 | veth3a
0 | veth6b
2 | veth8b

wifi>

a moment later, after stopping the vdc at the original node, i see the
following:

wifi>show redundancy
2022-07-15 10:13:26
iface | reach | state | prio | uptime | magic | heard
self | - | 3 | 5 | 00:03:56 | 740240790 | -
ethernet96 | 3 | 2 | 1 | 23:58:49 | 334780719 | 00:00:00
ethernet97 | 0 | 3 | 10 | 23:56:21 | 1012481247 | 00:03:59

wifi>show cdp neighbor
2022-07-15 10:13:30
interface | hostname | iface | ipv4 | ipv6
sdn0/0 | nas | sdn902 | 10.1.1.49 | 2001:db8:1d::1

wifi>show p4lang p4 port-names 0
2022-07-15 10:13:40
num | name
0 | veth3b
1 | veth4a
2 | veth7b

wifi>

that is, the rp now lives on a different node, and the associated forwarder 0
have different interface names...

such a setup also would be impossible with names in the p4lang server....

br,
cs



Archive powered by MHonArc 2.6.19.

Top of Page