Rare project developers

[Frédéric LOUI <>]

Hi,

self.<capability> safeguard has implemented and self populated by 
interrogating the p4 dataplane.
So bf_forwarder capability arguments have been removed.
https://bitbucket.software.geant.org/projects/RARE/repos/rare/commits/5a4235614ffcb49ce3bd9ec9d5d7e0f53db7fc7d

DAV0001#show p4lang p4                                                        
                                              
category    value                                                             
                                              
peer        127.0.0.1                                                         
                                              
closed      3                                                                 
                                              
capability  mpls mcast inacl outacl tun bier gre                              
                                              
platform    tna/bfforwarder                                                   
                                              
since       2022-02-08 15:12:46                                               
                                              
for         00:05:52                                                          
                                              

…
Output:
DAV0001#warning servP4lang.srvAccept:servP4lang.java:641 neighbor 127.0.0.1 
up                          
debug servP4langConn.doRound:servP4lang.java:1538 rx: platform 
tna/bfforwarder                          
debug servP4langConn.doRound:servP4lang.java:1538 rx: capabilities mpls mcast 
inacl outacl tun bier gre 
…

DAV0001#sh run | i nat                                     
ipv4 nat inet sequence 10 srclist ACL_NAT4 interface sdn15 

DAV0001#show access-list ACL_NAT4                                             
    
 sequence 10 permit 17 any all 4.4.4.4 255.255.255.255 all                    
    
  match=tx=0(0) rx=0(0) drp=0(0) accessed=never ago, 00:00:00 timeout         
    
 sequence 20 permit 6 any all 4.4.4.4 255.255.255.255 all                     
    
  match=tx=0(0) rx=0(0) drp=0(0) accessed=never ago, 00:00:00 timeout         
    
 sequence 30 deny all any all any all                                         
    
  match=tx=0(0) rx=894928(12980) drp=0(0) accessed=00:00:01 ago, 00:00:00 
timeout 

The important point here is that there is no more entry error related to NAT. 
In this example we are involving P4  NAT table. Why you might say ?

Answer is here:
https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/bfrt_python/rare/api/natcfg4.py#7

Basically when self.<capability> is false then it will result in a no-op. 
(bf_forwarder won’t even try to write entry via GRPC into an object that does 
not exist as the capability is not supported)

Let’s pass mc36’s  QC now :)

Thanks
fl