RARE user and assistance email list

[Alexander Gall <>]

Hi

On Sat, 16 Jul 2022 15:45:10 +0200, mc36 <> said:

> according to the below, starting from tomorrow, you won't have to pick a 
> vrf id when you export a vrf...
> the conversion should happen automatically, that is, for a while, the 2nd 
> parameter to export-vrf is
> ignored during parsing and not emitted during config creation... all you 
> have to do is login to your
> box an save the current configuration... optionally check beforehand if 
> everything went fine:

Excellent. Thank's a lot. I think that's a nice improvement of
usabilty :)

-- 
Alex

> show config-differences
> show rollback-config
> write

> br,
> cs


> -------- Forwarded Message --------
> Subject: Re: [rare-dev] further negotiations in between the dataplane and 
> freerouter...
> Date: Sat, 16 Jul 2022 09:41:13 +0200
> From: mc36 <>
> Reply-To: 
> To: , Alexander Gall <>
> CC: Fr  d  ric LOUI <>, David Richardson 
> <>

> hi,

> On 7/12/22 10:45, Alexander Gall wrote:
>> While you're at it, why not extend the mechanism to the other export
>> properties like VRFs?  It should not be up to the user to pick the
>> number that represents a VRF in a P4 table.
> here we go:

> server p4lang p4
>   export-vrf v2
>   export-port sdn1 1 10 0 0 0
>   export-port sdn2 2 10 0 0 0
>   export-port sdn3 3 10 0 0 0
>   export-port sdn4 4 10 0 0 0
>   interconnect pwether0
>   vrf v1
>   exit
> !

> sid#

> it had the drawback that if you're interested about the exact exports
> in p4 or in freerouter, first you have to find out the vrf number:

> sid#show p4lang p4 done-vrf
> sent  name
> 9007  ifc v2

> sid#show p4lang p4 done-route4 9007
> typ  prefix      metric  iface  hop   time
> C    1.1.1.0/30  0/0     sdn1   null  00:02:11
> LOC  1.1.1.1/32  0/1     sdn1   null  00:02:11
> C    1.1.1.4/30  0/0     sdn2   null  00:02:11
> LOC  1.1.1.5/32  0/1     sdn2   null  00:02:11
> C    1.1.1.8/30  0/0     sdn3   null  00:02:11
> LOC  1.1.1.9/32  0/1     sdn3   null  00:02:11

> sid#


> br,
> cs