Subject: RARE user and assistance email list
List archive
- From: mc36 <>
- To: ,
- Subject: Re: [gn4-3-wp6-t1-wb-RARE] bits from bfswd development...
- Date: Tue, 1 Sep 2020 05:33:32 +0200
hi,
please find attached the latest test results!
news that i added pppoe and l2tp to the tofino code base,
so finally we have feature parity between all the dataplanes.
a small addition to the tester itself that it got paralellism
for the image testing so for now it won't take 3 hours to have
tofino results... :)
unfortunate that i had to introduce additional flavors because
gre, l2tp or pppoe not fit together, and the latter two finally
have no mpls control because of the 'stage limit' issue.
regarding the 'tunnel-recirc' thing, i was thinking a lot about it,
did some quick tests and found that it have more drawbacks so finally
dropped the idea. tunnel decapsulation continues to cause recirculation.
currently, it called (*) after the decision is made to pass the packet
to the cpu, and this decision could be overridden. it happens after
every possible processing in question. if we would change this, we
have to move tunnel decap before acl processing in order to have acls
on tunnels. but at that point, the target vrf is not reliably known since
mpls or tunneling can change it... but we have to keep tunnel control
before the mpls control to have mpls over tunnels. regarding acls,
for decapped packets to have acl, we have to move tunneling before the acl
but doing so will simply take off encapped (gre) packets from the acl control
which is undesirable for example in a case of a bras who would like to
restrict
it's users to some networks... moreover, if we would do decap without recir,
we have to replicate all the current parser (and header) code after the last
tunnel
header to have it readily parsed up, because we need to copy these duplicated
headers
on decap to the original ones, because decision is made on those original ones
and the tunnel header need to be simply removed. it would end up additional
complexity of keeping two exact copies of the parser and surely increases
generated npu code which may cause less features enabled together or even
full loss of a some features...
regrards,
cs
*:
ig_ctl_vlan_in.apply(hdr,ig_md,ig_intr_md);
ig_ctl_pppoe.apply(hdr,ig_md,ig_intr_md);
ig_ctl_acl_in.apply(hdr,ig_md,ig_intr_md);
if (ig_md.dropping == 1) { return; }
ig_ctl_vrf.apply(hdr,ig_md,ig_intr_md);
ig_ctl_mpls.apply(hdr,ig_md,ig_intr_md);
ig_ctl_nat.apply(hdr,ig_md,ig_intr_md);
if ( ig_md.dropping == 1) { return; }
ig_ctl_ipv4.apply(hdr,ig_md,ig_intr_md);
ig_ctl_ipv6.apply(hdr,ig_md,ig_intr_md);
ig_ctl_bridge.apply(hdr,ig_md,ig_intr_md);
ig_ctl_ipv4b.apply(hdr,ig_md,ig_intr_md);
ig_ctl_ipv6b.apply(hdr,ig_md,ig_intr_md);
if ( ig_md.nexthop_id == CPU_PORT) {
ig_ctl_tunnel.apply(hdr,ig_md,ig_intr_md);
//////
On 8/31/20 10:51 AM, Frédéric LOUI wrote:
Hi Csaba,
Great additions â¦
Just let me know when youâll have finished this code alignment.
Iâll then proceed code cleaning in order to create a 1st a public releaseâ¦
For now Iâm busy with hardware/platform staging ...
à bientôt,
-- Frederic
Le 31 août 2020 à 10:42, mc36 <> a écrit :
hi,
attaching you the fresh results for the test runs with bfswd, bmv2 and p4emu
(dpdk, pcap)...
news that bfswd got the gre and tap features. it was a 2 step addition, first
got gre, then
the tap (routed mac) feature that will be the foundation of other tap-like
tunneling, vxlan
to name one. also had to change the sdm profiles, now we have bridge, mpls,
srv6 and tunnel.
this process can be tracked at http://sources.nop.hu/misc/p4bf/ , the c-*
files are those.
the resulting binaries have different capabilites, can be tracked at
http://sources.nop.hu/cfg/ ,
the p4lang3*.ini files are those. for now, i summarize you the features and
capabilies here:
brdg: -DHAVE_BRIDGE -DHAVE_TUN -DHAVE_GRE -DHAVE_TAP --> copp acl vlan bundle
bridge route hairpin gre gretap
mpls: -DHAVE_MPLS -DHAVE_BRIDGE --> copp acl vlan bundle bridge route mpls
vpls evpn eompls hairpin
srv6: -DHAVE_SRV6 -DHAVE_BRIDGE -DHAVE_NAT --> copp acl vlan bundle bridge
route srv6 hairpin nat
tun: -DHAVE_MPLS -DHAVE_TUN -DHAVE_GRE --> copp acl vlan bundle route hairpin
gre mpls
mpls and srv6 is the same as it was and they're basically full, i was not
able to enable any new features into them...
the bridging image have the layer2 over tunnels capability!!! it'll be the
basic for vxlan and others....
the tunneling image have mpls and gre but no layer2... it could become the
mpls enabled bras image!!!!
regarding the future, i'm continuing backporting features from bmv2 to
bfswd... pppoe control is
the only one missing and it would be easy-peasy... l2tp is a kind of
tunneling -that just arrived-
so also would not be a big deal... if all these are over, i'll skip
backporting bridging over
pppoe and l2tp to tofino because these are completely useless today and
they're quite different
tap encapsulation that would not worth the effort, instead i'll start
thinking about(*)/experimenting
with the vxlan encapsuation on p4emu and if it seems straightforward then
it'll appear on bmv2 and
them ported to tofino... probably these all won't fit once to the
corresponding bridge and tunnel
images so they may multiply by the underlying techniques.... we'll see how
far we can get....
(*) currently tunnel decap happens after it's decided that the packet for the
cpu, but before copp,
and after decap, a recirculation happens... for not-static tunnels it won't
work since we have no
inetrface ids for these virtual interfaces so on a mac-miss-punt the cpu
won't understand with the
tunneling header removed that the packet where belongs to... so i'm thinking
heavily on tunneling
should happen after mpls and nat, and before any ip processing, and get rid
of the recirculation
for tunnel decapsulation, similarly to pppoe which also not cause
recirculation....
if you spotted the failing tests with tofino it's because of the double
recirculation caused
first because of the hairpin and the second because of the tunnel itself...
regards,
cs
<rtrp4lang-bmv2-.csv><rtrp4lang-bmv2-.html><rtrp4lang-dpdk-.csv><rtrp4lang-dpdk-.html><rtrp4lang-tofino-.csv><rtrp4lang-tofino-.html>
file;result;test -;-;freeRouter v20.8.31-rel, done by cs@nop. -;-;2020-08-31 19:13:25, took 01:50:12, with 1 workers, on 122 cases, 0 failed, 0 traces, 0 retries -;-;java -Xmx256m -jar rtr.jar p4lang-acl01.tst;success;p4lang: copp p4lang-acl02.tst;success;p4lang: ingress access list p4lang-acl03.tst;success;p4lang: egress access list p4lang-acl04.tst;success;p4lang: nat p4lang-acl05.tst;success;p4lang: vlan ingress access list p4lang-acl06.tst;success;p4lang: vlan egress access list p4lang-acl07.tst;success;p4lang: bundle ingress access list p4lang-acl08.tst;success;p4lang: bundle egress access list p4lang-acl09.tst;success;p4lang: bundle vlan ingress access list p4lang-acl10.tst;success;p4lang: bundle vlan egress access list p4lang-acl11.tst;success;p4lang: bridge ingress access list p4lang-acl12.tst;success;p4lang: bridge egress access list p4lang-acl13.tst;success;p4lang: vlan bridge ingress access list p4lang-acl14.tst;success;p4lang: vlan bridge egress access list p4lang-acl15.tst;success;p4lang: ingress pppoe access list p4lang-acl16.tst;success;p4lang: egress pppoe access list p4lang-acl17.tst;success;p4lang: ingress vlan pppoe access list p4lang-acl18.tst;success;p4lang: egress vlan pppoe access list p4lang-acl19.tst;success;p4lang: hairpin ingress access list p4lang-acl20.tst;success;p4lang: hairpin egress access list p4lang-acl21.tst;success;p4lang: hairpin vlan ingress access list p4lang-acl22.tst;success;p4lang: hairpin vlan egress access list p4lang-acl23.tst;success;p4lang: hairpin pppoe ingress access list p4lang-acl24.tst;success;p4lang: hairpin pppoe egress access list p4lang-acl25.tst;success;p4lang: hairpin vlan pppoe ingress access list p4lang-acl26.tst;success;p4lang: hairpin vlan pppoe egress access list p4lang-acl27.tst;success;p4lang: ingress gre access list p4lang-acl28.tst;success;p4lang: egress gre access list p4lang-acl29.tst;success;p4lang: ingress vlan gre access list p4lang-acl30.tst;success;p4lang: egress vlan gre access list p4lang-acl31.tst;success;p4lang: ingress l2tp access list p4lang-acl32.tst;success;p4lang: egress l2tp access list p4lang-acl33.tst;success;p4lang: ingress vlan l2tp access list p4lang-acl34.tst;success;p4lang: egress vlan l2tp access list p4lang-rout01.tst;success;p4lang: routing p4lang-rout02.tst;success;p4lang: bridging p4lang-rout03.tst;success;p4lang: mpls core p4lang-rout04.tst;success;p4lang: mpls edge p4lang-rout05.tst;success;p4lang: vlan routing p4lang-rout06.tst;success;p4lang: vlan bridging p4lang-rout07.tst;success;p4lang: vlan mpls p4lang-rout08.tst;success;p4lang: vpn with bgp p4lang-rout09.tst;success;p4lang: vpls/ldp with bgp p4lang-rout10.tst;success;p4lang: evpn/cmac with bgp p4lang-rout11.tst;success;p4lang: eompls p4lang-rout12.tst;success;p4lang: vpn with bgp over srv6 p4lang-rout13.tst;success;p4lang: evpn/cmac with bgp over srv6 p4lang-rout14.tst;success;p4lang: bundle routing p4lang-rout15.tst;success;p4lang: bundle mpls p4lang-rout16.tst;success;p4lang: bundle vlan routing p4lang-rout17.tst;success;p4lang: bundle vlan mpls p4lang-rout18.tst;success;p4lang: bundle vlan bridging p4lang-rout19.tst;success;p4lang: bridge routing p4lang-rout20.tst;success;p4lang: bridge mpls p4lang-rout21.tst;success;p4lang: vlan bridge routing p4lang-rout22.tst;success;p4lang: vlan bridge mpls p4lang-rout23.tst;success;p4lang: vlan vpls/ldp with bgp p4lang-rout24.tst;success;p4lang: vlan eompls p4lang-rout25.tst;success;p4lang: bundle vlan vpls/ldp with bgp p4lang-rout26.tst;success;p4lang: bundle vlan eompls p4lang-rout27.tst;success;p4lang: pppoe routing p4lang-rout28.tst;success;p4lang: vlan pppoe routing p4lang-rout29.tst;success;p4lang: pppoe mpls p4lang-rout30.tst;success;p4lang: vlan pppoe mpls p4lang-rout31.tst;success;p4lang: hairpin routing p4lang-rout32.tst;success;p4lang: hairpin bridging p4lang-rout33.tst;success;p4lang: hairpin mpls p4lang-rout34.tst;success;p4lang: hairpin vlan routing p4lang-rout35.tst;success;p4lang: hairpin vlan bridging p4lang-rout36.tst;success;p4lang: hairpin vlan mpls p4lang-rout37.tst;success;p4lang: hairpin pppoe routing p4lang-rout38.tst;success;p4lang: hairpin vlan pppoe routing p4lang-rout39.tst;success;p4lang: hairpin pppoe mpls p4lang-rout40.tst;success;p4lang: hairpin vlan pppoe mpls p4lang-rout41.tst;success;p4lang: hairpin vpls/ldp with bgp p4lang-rout42.tst;success;p4lang: hairpin vlan vpls/ldp with bgp p4lang-rout43.tst;success;p4lang: hairpin eompls p4lang-rout44.tst;success;p4lang: hairpin vlan eompls p4lang-rout45.tst;success;p4lang: vlan evpn/cmac with bgp p4lang-rout46.tst;success;p4lang: bundle vlan evpn/cmac with bgp p4lang-rout47.tst;success;p4lang: hairpin evpn/cmac with bgp p4lang-rout48.tst;success;p4lang: hairpin vlan evpn/cmac with bgp p4lang-rout49.tst;success;p4lang: gre routing over ipv4 p4lang-rout50.tst;success;p4lang: gre routing over ipv6 p4lang-rout51.tst;success;p4lang: gre routing over ipv4 loopback p4lang-rout52.tst;success;p4lang: gre routing over ipv6 loopback p4lang-rout53.tst;success;p4lang: gre routing over vlan p4lang-rout54.tst;success;p4lang: gre routing over bundle p4lang-rout55.tst;success;p4lang: gre routing over bundle vlan p4lang-rout56.tst;success;p4lang: gre routing over hairpin p4lang-rout57.tst;success;p4lang: gre routing over hairpin vlan p4lang-rout58.tst;success;p4lang: gre routing over bridge p4lang-rout59.tst;success;p4lang: gre routing over vlan bridge p4lang-rout60.tst;success;p4lang: gre mpls over ipv4 p4lang-rout61.tst;success;p4lang: gre mpls over ipv6 p4lang-rout62.tst;success;p4lang: gre mpls over ipv4 loopback p4lang-rout63.tst;success;p4lang: gre mpls over ipv6 loopback p4lang-rout64.tst;success;p4lang: gre mpls over vlan p4lang-rout65.tst;success;p4lang: gre mpls over bundle p4lang-rout66.tst;success;p4lang: gre mpls over bundle vlan p4lang-rout67.tst;success;p4lang: gre mpls over hairpin p4lang-rout68.tst;success;p4lang: gre mpls over hairpin vlan p4lang-rout69.tst;success;p4lang: gre mpls over bridge p4lang-rout70.tst;success;p4lang: gre mpls over vlan bridge p4lang-rout71.tst;success;p4lang: l2tp routing over ipv4 p4lang-rout72.tst;success;p4lang: l2tp routing over ipv6 p4lang-rout73.tst;success;p4lang: l2tp routing over ipv4 loopback p4lang-rout74.tst;success;p4lang: l2tp routing over ipv6 loopback p4lang-rout75.tst;success;p4lang: l2tp routing over vlan p4lang-rout76.tst;success;p4lang: l2tp routing over bundle p4lang-rout77.tst;success;p4lang: l2tp mpls over ipv4 p4lang-rout78.tst;success;p4lang: l2tp mpls over ipv6 p4lang-rout79.tst;success;p4lang: l2tp mpls over ipv4 loopback p4lang-rout80.tst;success;p4lang: l2tp mpls over ipv6 loopback p4lang-rout81.tst;success;p4lang: l2tp mpls over vlan p4lang-rout82.tst;success;p4lang: l2tp mpls over bundle p4lang-rout83.tst;success;p4lang: bridging over gre p4lang-rout84.tst;success;p4lang: bridging over gre vlan p4lang-rout85.tst;success;p4lang: bridging over pppoe p4lang-rout86.tst;success;p4lang: bridging over pppoe vlan p4lang-rout87.tst;success;p4lang: bridging over l2tp p4lang-rout88.tst;success;p4lang: bridging over l2tp vlanTitle: tester
|
release: freeRouter v20.8.31-rel, done by cs@nop. tested: 2020-08-31 19:13:25, took 01:50:12, with 1 workers, on 122 cases, 0 failed, 0 traces, 0 retries jvm: java -Xmx256m -jar rtr.jar
|
file;result;test -;-;freeRouter v20.8.31-rel, done by cs@nop. -;-;2020-08-31 19:29:54, took 02:06:39, with 1 workers, on 122 cases, 0 failed, 0 traces, 1 retries -;-;java -Xmx256m -jar rtr.jar p4lang-acl01.tst;success;p4lang: copp p4lang-acl02.tst;success;p4lang: ingress access list p4lang-acl03.tst;success;p4lang: egress access list p4lang-acl04.tst;success;p4lang: nat p4lang-acl05.tst;success;p4lang: vlan ingress access list p4lang-acl06.tst;success;p4lang: vlan egress access list p4lang-acl07.tst;success;p4lang: bundle ingress access list p4lang-acl08.tst;success;p4lang: bundle egress access list p4lang-acl09.tst;success;p4lang: bundle vlan ingress access list p4lang-acl10.tst;success;p4lang: bundle vlan egress access list p4lang-acl11.tst;success;p4lang: bridge ingress access list p4lang-acl12.tst;success;p4lang: bridge egress access list p4lang-acl13.tst;success;p4lang: vlan bridge ingress access list p4lang-acl14.tst;success;p4lang: vlan bridge egress access list p4lang-acl15.tst;success;p4lang: ingress pppoe access list p4lang-acl16.tst;success;p4lang: egress pppoe access list p4lang-acl17.tst;success;p4lang: ingress vlan pppoe access list p4lang-acl18.tst;success;p4lang: egress vlan pppoe access list p4lang-acl19.tst;success;p4lang: hairpin ingress access list p4lang-acl20.tst;success;p4lang: hairpin egress access list p4lang-acl21.tst;success;p4lang: hairpin vlan ingress access list p4lang-acl22.tst;success;p4lang: hairpin vlan egress access list p4lang-acl23.tst;success;p4lang: hairpin pppoe ingress access list p4lang-acl24.tst;success;p4lang: hairpin pppoe egress access list p4lang-acl25.tst;success;p4lang: hairpin vlan pppoe ingress access list p4lang-acl26.tst;success;p4lang: hairpin vlan pppoe egress access list p4lang-acl27.tst;success;p4lang: ingress gre access list p4lang-acl28.tst;success;p4lang: egress gre access list p4lang-acl29.tst;success;p4lang: ingress vlan gre access list p4lang-acl30.tst;success;p4lang: egress vlan gre access list p4lang-acl31.tst;success;p4lang: ingress l2tp access list p4lang-acl32.tst;success;p4lang: egress l2tp access list p4lang-acl33.tst;success;p4lang: ingress vlan l2tp access list p4lang-acl34.tst;success;p4lang: egress vlan l2tp access list p4lang-rout01.tst;success;p4lang: routing p4lang-rout02.tst;success;p4lang: bridging p4lang-rout03.tst;success;p4lang: mpls core p4lang-rout04.tst;success;p4lang: mpls edge p4lang-rout05.tst;success;p4lang: vlan routing p4lang-rout06.tst;success;p4lang: vlan bridging p4lang-rout07.tst;success;p4lang: vlan mpls p4lang-rout08.tst;success;p4lang: vpn with bgp p4lang-rout09.tst;success;p4lang: vpls/ldp with bgp p4lang-rout10.tst;success;p4lang: evpn/cmac with bgp p4lang-rout11.tst;success;p4lang: eompls p4lang-rout12.tst;not applicable;p4lang: vpn with bgp over srv6 p4lang-rout13.tst;not applicable;p4lang: evpn/cmac with bgp over srv6 p4lang-rout14.tst;success;p4lang: bundle routing p4lang-rout15.tst;success;p4lang: bundle mpls p4lang-rout16.tst;success;p4lang: bundle vlan routing p4lang-rout17.tst;success;p4lang: bundle vlan mpls p4lang-rout18.tst;success;p4lang: bundle vlan bridging p4lang-rout19.tst;success;p4lang: bridge routing p4lang-rout20.tst;success;p4lang: bridge mpls p4lang-rout21.tst;success;p4lang: vlan bridge routing p4lang-rout22.tst;success;p4lang: vlan bridge mpls p4lang-rout23.tst;success;p4lang: vlan vpls/ldp with bgp p4lang-rout24.tst;success;p4lang: vlan eompls p4lang-rout25.tst;success;p4lang: bundle vlan vpls/ldp with bgp p4lang-rout26.tst;success;p4lang: bundle vlan eompls p4lang-rout27.tst;success;p4lang: pppoe routing p4lang-rout28.tst;success;p4lang: vlan pppoe routing p4lang-rout29.tst;success;p4lang: pppoe mpls p4lang-rout30.tst;success;p4lang: vlan pppoe mpls p4lang-rout31.tst;success;p4lang: hairpin routing p4lang-rout32.tst;success;p4lang: hairpin bridging p4lang-rout33.tst;success;p4lang: hairpin mpls p4lang-rout34.tst;success;p4lang: hairpin vlan routing p4lang-rout35.tst;success;p4lang: hairpin vlan bridging p4lang-rout36.tst;success;p4lang: hairpin vlan mpls p4lang-rout37.tst;success;p4lang: hairpin pppoe routing p4lang-rout38.tst;success;p4lang: hairpin vlan pppoe routing p4lang-rout39.tst;success;p4lang: hairpin pppoe mpls p4lang-rout40.tst;success;p4lang: hairpin vlan pppoe mpls p4lang-rout41.tst;success;p4lang: hairpin vpls/ldp with bgp p4lang-rout42.tst;success;p4lang: hairpin vlan vpls/ldp with bgp p4lang-rout43.tst;success;p4lang: hairpin eompls p4lang-rout44.tst;success;p4lang: hairpin vlan eompls p4lang-rout45.tst;success;p4lang: vlan evpn/cmac with bgp p4lang-rout46.tst;success;p4lang: bundle vlan evpn/cmac with bgp p4lang-rout47.tst;success;p4lang: hairpin evpn/cmac with bgp p4lang-rout48.tst;success;p4lang: hairpin vlan evpn/cmac with bgp p4lang-rout49.tst;success;p4lang: gre routing over ipv4 p4lang-rout50.tst;success;p4lang: gre routing over ipv6 p4lang-rout51.tst;success;p4lang: gre routing over ipv4 loopback p4lang-rout52.tst;success;p4lang: gre routing over ipv6 loopback p4lang-rout53.tst;success;p4lang: gre routing over vlan p4lang-rout54.tst;success;p4lang: gre routing over bundle p4lang-rout55.tst;success;p4lang: gre routing over bundle vlan p4lang-rout56.tst;success;p4lang: gre routing over hairpin p4lang-rout57.tst;success;p4lang: gre routing over hairpin vlan p4lang-rout58.tst;success;p4lang: gre routing over bridge p4lang-rout59.tst;success;p4lang: gre routing over vlan bridge p4lang-rout60.tst;success;p4lang: gre mpls over ipv4 p4lang-rout61.tst;success;p4lang: gre mpls over ipv6 p4lang-rout62.tst;success;p4lang: gre mpls over ipv4 loopback p4lang-rout63.tst;success;p4lang: gre mpls over ipv6 loopback p4lang-rout64.tst;success;p4lang: gre mpls over vlan p4lang-rout65.tst;success;p4lang: gre mpls over bundle p4lang-rout66.tst;success;p4lang: gre mpls over bundle vlan p4lang-rout67.tst;success;p4lang: gre mpls over hairpin p4lang-rout68.tst;success;p4lang: gre mpls over hairpin vlan p4lang-rout69.tst;success;p4lang: gre mpls over bridge p4lang-rout70.tst;success;p4lang: gre mpls over vlan bridge p4lang-rout71.tst;success;p4lang: l2tp routing over ipv4 p4lang-rout72.tst;success;p4lang: l2tp routing over ipv6 p4lang-rout73.tst;success;p4lang: l2tp routing over ipv4 loopback p4lang-rout74.tst;success;p4lang: l2tp routing over ipv6 loopback p4lang-rout75.tst;success;p4lang: l2tp routing over vlan p4lang-rout76.tst;success;p4lang: l2tp routing over bundle p4lang-rout77.tst;success;p4lang: l2tp mpls over ipv4 p4lang-rout78.tst;success;p4lang: l2tp mpls over ipv6 p4lang-rout79.tst;success;p4lang: l2tp mpls over ipv4 loopback p4lang-rout80.tst;success;p4lang: l2tp mpls over ipv6 loopback p4lang-rout81.tst;success;p4lang: l2tp mpls over vlan p4lang-rout82.tst;success;p4lang: l2tp mpls over bundle p4lang-rout83.tst;success;p4lang: bridging over gre p4lang-rout84.tst;success;p4lang: bridging over gre vlan p4lang-rout85.tst;success;p4lang: bridging over pppoe p4lang-rout86.tst;success;p4lang: bridging over pppoe vlan p4lang-rout87.tst;success;p4lang: bridging over l2tp p4lang-rout88.tst;success;p4lang: bridging over l2tp vlanTitle: tester
|
release: freeRouter v20.8.31-rel, done by cs@nop. tested: 2020-08-31 19:29:54, took 02:06:39, with 1 workers, on 122 cases, 0 failed, 0 traces, 1 retries jvm: java -Xmx256m -jar rtr.jar
|
file;result;test -;-;freeRouter v20.8.31-rel, done by cs@nop. -;-;2020-08-31 20:25:52, took 03:01:50, with 1 workers, on 122 cases, 0 failed, 0 traces, 3 retries -;-;java -Xmx256m -jar rtr.jar p4lang-acl01.tst;success;p4lang: copp p4lang-acl02.tst;success;p4lang: ingress access list p4lang-acl03.tst;success;p4lang: egress access list p4lang-acl04.tst;success;p4lang: nat p4lang-acl05.tst;success;p4lang: vlan ingress access list p4lang-acl06.tst;success;p4lang: vlan egress access list p4lang-acl07.tst;success;p4lang: bundle ingress access list p4lang-acl08.tst;success;p4lang: bundle egress access list p4lang-acl09.tst;success;p4lang: bundle vlan ingress access list p4lang-acl10.tst;success;p4lang: bundle vlan egress access list p4lang-acl11.tst;success;p4lang: bridge ingress access list p4lang-acl12.tst;success;p4lang: bridge egress access list p4lang-acl13.tst;success;p4lang: vlan bridge ingress access list p4lang-acl14.tst;success;p4lang: vlan bridge egress access list p4lang-acl15.tst;success;p4lang: ingress pppoe access list p4lang-acl16.tst;success;p4lang: egress pppoe access list p4lang-acl17.tst;success;p4lang: ingress vlan pppoe access list p4lang-acl18.tst;success;p4lang: egress vlan pppoe access list p4lang-acl19.tst;success;p4lang: hairpin ingress access list p4lang-acl20.tst;success;p4lang: hairpin egress access list p4lang-acl21.tst;success;p4lang: hairpin vlan ingress access list p4lang-acl22.tst;success;p4lang: hairpin vlan egress access list p4lang-acl23.tst;success;p4lang: hairpin pppoe ingress access list p4lang-acl24.tst;success;p4lang: hairpin pppoe egress access list p4lang-acl25.tst;success;p4lang: hairpin vlan pppoe ingress access list p4lang-acl26.tst;success;p4lang: hairpin vlan pppoe egress access list p4lang-acl27.tst;success;p4lang: ingress gre access list p4lang-acl28.tst;success;p4lang: egress gre access list p4lang-acl29.tst;success;p4lang: ingress vlan gre access list p4lang-acl30.tst;success;p4lang: egress vlan gre access list p4lang-acl31.tst;success;p4lang: ingress l2tp access list p4lang-acl32.tst;success;p4lang: egress l2tp access list p4lang-acl33.tst;success;p4lang: ingress vlan l2tp access list p4lang-acl34.tst;success;p4lang: egress vlan l2tp access list p4lang-rout01.tst;success;p4lang: routing p4lang-rout02.tst;success;p4lang: bridging p4lang-rout03.tst;success;p4lang: mpls core p4lang-rout04.tst;success;p4lang: mpls edge p4lang-rout05.tst;success;p4lang: vlan routing p4lang-rout06.tst;success;p4lang: vlan bridging p4lang-rout07.tst;success;p4lang: vlan mpls p4lang-rout08.tst;success;p4lang: vpn with bgp p4lang-rout09.tst;success;p4lang: vpls/ldp with bgp p4lang-rout10.tst;success;p4lang: evpn/cmac with bgp p4lang-rout11.tst;success;p4lang: eompls p4lang-rout12.tst;success;p4lang: vpn with bgp over srv6 p4lang-rout13.tst;success;p4lang: evpn/cmac with bgp over srv6 p4lang-rout14.tst;success;p4lang: bundle routing p4lang-rout15.tst;success;p4lang: bundle mpls p4lang-rout16.tst;success;p4lang: bundle vlan routing p4lang-rout17.tst;success;p4lang: bundle vlan mpls p4lang-rout18.tst;success;p4lang: bundle vlan bridging p4lang-rout19.tst;success;p4lang: bridge routing p4lang-rout20.tst;success;p4lang: bridge mpls p4lang-rout21.tst;success;p4lang: vlan bridge routing p4lang-rout22.tst;success;p4lang: vlan bridge mpls p4lang-rout23.tst;success;p4lang: vlan vpls/ldp with bgp p4lang-rout24.tst;success;p4lang: vlan eompls p4lang-rout25.tst;success;p4lang: bundle vlan vpls/ldp with bgp p4lang-rout26.tst;success;p4lang: bundle vlan eompls p4lang-rout27.tst;success;p4lang: pppoe routing p4lang-rout28.tst;success;p4lang: vlan pppoe routing p4lang-rout29.tst;not applicable;p4lang: pppoe mpls p4lang-rout30.tst;not applicable;p4lang: vlan pppoe mpls p4lang-rout31.tst;success;p4lang: hairpin routing p4lang-rout32.tst;success;p4lang: hairpin bridging p4lang-rout33.tst;success;p4lang: hairpin mpls p4lang-rout34.tst;success;p4lang: hairpin vlan routing p4lang-rout35.tst;success;p4lang: hairpin vlan bridging p4lang-rout36.tst;success;p4lang: hairpin vlan mpls p4lang-rout37.tst;success;p4lang: hairpin pppoe routing p4lang-rout38.tst;success;p4lang: hairpin vlan pppoe routing p4lang-rout39.tst;not applicable;p4lang: hairpin pppoe mpls p4lang-rout40.tst;not applicable;p4lang: hairpin vlan pppoe mpls p4lang-rout41.tst;success;p4lang: hairpin vpls/ldp with bgp p4lang-rout42.tst;success;p4lang: hairpin vlan vpls/ldp with bgp p4lang-rout43.tst;success;p4lang: hairpin eompls p4lang-rout44.tst;success;p4lang: hairpin vlan eompls p4lang-rout45.tst;success;p4lang: vlan evpn/cmac with bgp p4lang-rout46.tst;success;p4lang: bundle vlan evpn/cmac with bgp p4lang-rout47.tst;success;p4lang: hairpin evpn/cmac with bgp p4lang-rout48.tst;success;p4lang: hairpin vlan evpn/cmac with bgp p4lang-rout49.tst;success;p4lang: gre routing over ipv4 p4lang-rout50.tst;success;p4lang: gre routing over ipv6 p4lang-rout51.tst;success;p4lang: gre routing over ipv4 loopback p4lang-rout52.tst;success;p4lang: gre routing over ipv6 loopback p4lang-rout53.tst;success;p4lang: gre routing over vlan p4lang-rout54.tst;success;p4lang: gre routing over bundle p4lang-rout55.tst;success;p4lang: gre routing over bundle vlan p4lang-rout56.tst;success;p4lang: gre routing over hairpin p4lang-rout57.tst;success;p4lang: gre routing over hairpin vlan p4lang-rout58.tst;success;p4lang: gre routing over bridge p4lang-rout59.tst;success;p4lang: gre routing over vlan bridge p4lang-rout60.tst;success;p4lang: gre mpls over ipv4 p4lang-rout61.tst;success;p4lang: gre mpls over ipv6 p4lang-rout62.tst;success;p4lang: gre mpls over ipv4 loopback p4lang-rout63.tst;success;p4lang: gre mpls over ipv6 loopback p4lang-rout64.tst;success;p4lang: gre mpls over vlan p4lang-rout65.tst;success;p4lang: gre mpls over bundle p4lang-rout66.tst;success;p4lang: gre mpls over bundle vlan p4lang-rout67.tst;success;p4lang: gre mpls over hairpin p4lang-rout68.tst;success;p4lang: gre mpls over hairpin vlan p4lang-rout69.tst;success;p4lang: gre mpls over bridge p4lang-rout70.tst;success;p4lang: gre mpls over vlan bridge p4lang-rout71.tst;success;p4lang: l2tp routing over ipv4 p4lang-rout72.tst;success;p4lang: l2tp routing over ipv6 p4lang-rout73.tst;success;p4lang: l2tp routing over ipv4 loopback p4lang-rout74.tst;success;p4lang: l2tp routing over ipv6 loopback p4lang-rout75.tst;success;p4lang: l2tp routing over vlan p4lang-rout76.tst;success;p4lang: l2tp routing over bundle p4lang-rout77.tst;not applicable;p4lang: l2tp mpls over ipv4 p4lang-rout78.tst;not applicable;p4lang: l2tp mpls over ipv6 p4lang-rout79.tst;not applicable;p4lang: l2tp mpls over ipv4 loopback p4lang-rout80.tst;not applicable;p4lang: l2tp mpls over ipv6 loopback p4lang-rout81.tst;not applicable;p4lang: l2tp mpls over vlan p4lang-rout82.tst;not applicable;p4lang: l2tp mpls over bundle p4lang-rout83.tst;success;p4lang: bridging over gre p4lang-rout84.tst;success;p4lang: bridging over gre vlan p4lang-rout85.tst;not applicable;p4lang: bridging over pppoe p4lang-rout86.tst;not applicable;p4lang: bridging over pppoe vlan p4lang-rout87.tst;not applicable;p4lang: bridging over l2tp p4lang-rout88.tst;not applicable;p4lang: bridging over l2tp vlanTitle: tester
|
release: freeRouter v20.8.31-rel, done by cs@nop. tested: 2020-08-31 20:25:52, took 03:01:50, with 1 workers, on 122 cases, 0 failed, 0 traces, 3 retries jvm: java -Xmx256m -jar rtr.jar
|
- Re: [gn4-3-wp6-t1-wb-RARE] bits from bfswd development..., mc36, 09/01/2020
Archive powered by MHonArc 2.6.19.