+1 -John
From: vpp-committ...@lists.fd.io On Behalf Of Dave
Barach via lists.fd.io
Sent: Friday, September 25, 2020 3:14 PM
To: vpp-committ...@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-committers] VPP committers: VPP PTL vote
Folks,
The self-nomination period closed yesterday. We
Make sense to me, as saving trace data is already impacting "normal"
performance. The extra function call is probably not much more overhead. -John
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
lists.fd.io
Sent: Monday, June 08, 2020 10:13 AM
To: vpp-dev@lists.fd.io
Subject:
Never mind. I have not caught up to newer messages in the thread when I
replied. -John
From: vpp-dev@lists.fd.io On Behalf Of John Lo (loj) via
lists.fd.io
Sent: Friday, June 05, 2020 4:40 PM
To: dmar...@me.com; m...@ciena.com
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] #vpp #vnet
May be it is this one? https://gerrit.fd.io/r/c/vpp/+/26961 -John
From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via
lists.fd.io
Sent: Friday, June 05, 2020 11:51 AM
To: m...@ciena.com
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] #vpp #vnet apparent buffer prefetch issue - seeing "l3
:55 PM
To: John Lo (loj) ; Nagaraju Vemuri
Cc: Andrew Yourtchenko ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP forwarding packets not destined to it #vpp
Hi John,
I assume the pass thru/drop applies to multicast frames too(assuming we have
IGMP enabled segment). Correct?
Thanks
We can use “show node counters” which should display counter for packets
dropped due to MAC mismatch. -John
From: Nagaraju Vemuri
Sent: Wednesday, June 03, 2020 3:10 PM
To: John Lo (loj)
Cc: Andrew Yourtchenko ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP forwarding packets not destined
, and build, the image should
have my patch included. Please let us know if it solve your problem or not.
Regards,
John
From: Nagaraju Vemuri
Sent: Wednesday, June 03, 2020 1:52 PM
To: Andrew Yourtchenko
Cc: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP forwarding packets
.
Regards,
John
From: Nagaraju Vemuri
Sent: Wednesday, June 03, 2020 1:06 PM
To: John Lo (loj)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP forwarding packets not destined to it #vpp
Hi John,
Sorry, I should have been more clear.
We are using Virtual machines(KVM based) on which VPP runs
Please clarify the following:
> When the bridge has no binding info about MAC-to-port, bridge is flooding
> packets to all interfaces.
1. Is this linux bridge that’s in the kernel so not a bridge domain inside
VPP?
2. So packets are flooded to all interfaces in the bridge. Are you saying
Hi Laurent,
VPP interface and sub-interface come up in L3 mode by default, unless it is put
into L2 mode for either bridging or cross connect:
DBGvpp# set interface l2 bridge ?
set interface l2 bridge set interface l2 bridge
[bvi|uu-fwd] [shg]
DBGvpp# set interface l2
The new vpp cli to show ip4-arp and ip6-neighbor entries is “show ip neighbors”:
DBGvpp# sho ip neighbor
Time IPFlags Ethernet
Interface
8.436410.0.3.3 D00:50:56:88:00:ac
Hi Andrew,
It would be good to include the following two patches:
https://gerrit.fd.io/r/c/vpp/+/27027
https://gerrit.fd.io/r/c/vpp/+/27029
Regards,
John
From: vpp-dev@lists.fd.io On Behalf Of Mrityunjay Kumar
Sent: Wednesday, May 13, 2020 11:11 AM
To: Andrew Yourtchenko
Cc: vpp-dev
Subject:
Hi Damjan,
I took a look at the console log. It seems to me the traceback after vxlan test
case was due to running out of space. So test run was aborted thereafter:
07:56:20
==
07:56:20 VXLAN Test Case
07:56:20
Try “make test TEST=acl_plugin”. -John
From: vpp-dev@lists.fd.io On Behalf Of Govindarajan
Mohandoss
Sent: Tuesday, April 28, 2020 11:22 PM
To: Paul Vinciguerra
Cc: Andrew Yourtchenko ; vpp-dev@lists.fd.io; nd
; Lijian Zhang ; Jieqiang Wang
; nd
Subject: Re: [vpp-dev] ACL question
Hi
+1
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
lists.fd.io
Sent: Tuesday, April 21, 2020 7:40 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp project committer nomination: Benoit Ganne
Vpp project committers: please vote +1, 0, -1 on the
Hi Nick,
I reviewed your patch and merged it. Really appreciate your effort to address
the VRF limitation and also refactor the common VTEP handling code.
Regards,
John
From: Nick Zavaritsky
Sent: Monday, March 02, 2020 7:35 AM
To: John Lo (loj)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev
+1 -John
From: vpp-dev@lists.fd.io On Behalf Of d...@barachs.net
Sent: Monday, March 02, 2020 9:16 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp project committers: formal vote to add Matt Smith as a
vpp committer
VPP committers, please vote +1, 0, -1 on adding Matt Smith
Hi Nick,
I agree the current bypass node for various tunnel types, including geneve,
gtpu, vxlan, and vxlan_gbp all have this issue in its hash lookup using only
incoming packet DIP without checking VRF. It is generally not an issue if
bypass feature is enabled on all interfaces which are on
Thanks Dave, that would be good. -John
From: Dave Barach (dbarach)
Sent: Wednesday, February 26, 2020 10:08 AM
To: John Lo (loj) ; vpp-dev
Subject: RE: Change interface default MTU to 1500
OK, how about this: I'll add a VLIB_CONFIG_FUNCTION, or [more likely] add a
system default MTU
Hi Dave,
My memory was that in data center or cloud environment it is desirable to set
MTU to jumbo frame size to avoid fragmentation by default. Thus the question
would be if it is reasonable to set default MTU size to 9000 for VPP and what
kind of problem is it causing that would be fixed
The MAC address ad:ef:ad:ef:de:ad is a multicast address. That’s why packet
with that destination MAC is flooded in the bridge. Try assign a unicast MAC
address to gtpu_tunnel1.
Regards,
John
From: vpp-dev@lists.fd.io On Behalf Of sunny cupertino
Sent: Friday, February 14, 2020 9:34 PM
To:
AM
To: John Lo (loj)
Cc: Raj ; vpp-dev
Subject: Re: [vpp-dev] QinQ and dot1ad any
On Tue, Dec 17, 2019 at 8:13 AM John Lo (loj) via
Lists.Fd.Io<http://Lists.Fd.Io>
mailto:cisco@lists.fd.io>> wrote:
Thus, sub-interface with "inner-dot1q any" is not an exa
ave missed.
Regards,
John
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Raj
Sent: Wednesday, December 18, 2019 8:32 AM
To: vpp-dev
Subject: Re: [vpp-dev] QinQ and dot1ad any
On Tue, Dec 17, 2019 at 7:43 PM John Lo (loj) wrote:
> Without exact match on a L3 sub-i
Hi Raj,
A sub-interface with "dot1q inner any" can only work with L2 forwarding via
cross-connect or bridging where packets are forwarded using MAC header without
any changes to MAC header nor VLAN IDs in VLAN tags.
For L3 IP forwarding, any VLAN tags on a packet must be exact match to a
With the newer VPP, since around 18.04, IP table must be created before an
interface can be set to it. The default global IP table 0 is an exception
because it is already present on startup.
The CLI is:
vpp# ip table ?
ip table ip table [add|del]
Regards,
Thank you very much, Dave! Appreciate your quick action. -John
From: vpp-dev@lists.fd.io On Behalf Of Dave Wallace
Sent: Tuesday, October 29, 2019 2:02 PM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: [vpp-dev] VPP 19.04.3 Maintenance Release is complete!
Folks,
The VPP 19.04.3
To create GRE tunnel in L2 mode, you can add “teb” keyword in the create CLI
which makes the GRE tunnel work in transparent ethernet bridging mode:
vpp# create gre ?
create gre tunnelcreate gre tunnel src dst
[instance ] [outer-fib-id ] [teb | erspan ] [del]
In
I have similar setup with 10GE Intel NIC on bare-metal box running Ubuntu
18.10. I don’t see such an issue in the past up to the current VPP being used
which is 19.04 (unless something changed with 19.08 or master). The 10GE port
is connected to an IXIA tester and when I set interface state
To clarify, what's implemented in VPP for IRB (Integrated Routing and Bridging)
is via creation of BVI (Bridge Virtual Interface) interfaces on bridge domains.
Then IP addresses can then be configured on these BVIs to enable IP packets be
routed (or L3 forwarded) among bridge domains or other
The VPP CLI to set interface to an IP table also work on sub-interfaces if the
name of the sub-interface is specified. For example:
vpp# ip table 10
vpp# create sub-interfaces GigabitEthernet4/0/0 10
GigabitEthernet4/0/0.10
vpp# set int ip table GigabitEthernet4/0/0.10 10
vpp# set int ip
Right now, the only condition for VPP to send GARP would be on bonded
interfaces in active-standby mode when the active link switches from one to the
other. GRAP is sent to help the upstream router/switch converge its routes
faster. There is no support for VPP to send GARP for other events.
Looks like your GTPU tunnel is setup to send decap packets into L2 forwarding
(either via "decap-next l2" CLI or default). Now, you need to setup how to L2
forward the decap packets. You can either put this tunnel interface into a
bridge domain or cross connect it to an output interface for
pp-dev@lists.fd.io On Behalf Of John Lo (loj) via
Lists.Fd.Io
Sent: Thursday, April 18, 2019 11:30 AM
To: Raj ; vpp-dev
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Using wildcard-ip4-arp-publisher-process
Hi Raj,
The registration for ARP events with specific IP is different to when
registration for
Hi Raj,
The registration for ARP events with specific IP is different to when
registration for a wild card IP.
If a client register for ARP events for a specific IP address, an event will be
sent by VPP to the client when ARP resolution occurred for the specified IP
address in L3 FIB.
If a
Of John Lo (loj) via
Lists.Fd.Io
Sent: Wednesday, April 17, 2019 12:06 PM
To: Abeeha Aqeel ; hongjun...@intel.com;
vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP PPPoE Plugin
Hi Abeeha,
Have you tried the suggestion I made previously in a similar thread to get rid
Hi Abeeha,
Have you tried the suggestion I made previously in a similar thread to get rid
of the dummy_interface_tx nodes for PPPoE sessions?
diff --git a/src/plugins/pppoe/pppoe.c b/src/plugins/pppoe/pppoe.c
index d73a718..f61926d 100644
--- a/src/plugins/pppoe/pppoe.c
+++
I think the way to not create TX nodes for PPPoE interfaces would be to just
remove the .tx_function specified in its device class init in
src/plugin/pppoe/pppoe.c:
/* *INDENT-OFF* */
VNET_DEVICE_CLASS (pppoe_device_class,static) = {
.name = "PPPoE",
.format_device_name = format_pppoe_name,
ror0 = ETHERNET_ERROR_L3_MAC_MISMATCH;
Regards,
John
From: Damjan Marion
Sent: Friday, March 22, 2019 3:41 AM
To: Ni, Hongjun
Cc: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Status of PPPoE Plugin
On 22 Mar 2019, at 07:34, Ni, Hongjun
mailto:hongjun...@intel.com>>
Thanks for citing the PPPoE RFC 2516, Damjan. The RFC goes on to describe how
to resolve the MAC address for PPPoE sessions in Section 5 in discovery stage.
As such, there is really no “L2 mode” for PPPoE sessions mentioned in my
previous reply in this thread. The root cause of the problem
Hi Hongjun,
I understand PPP is point to point so there is no MAC as such to check. If it
is PPPoE, are you sure we are supposed to accept packets with any MAC address?
Is PPPoE also a point to point interface only and not on a Ethernet LAN?
With Ethernet, MAC check is required if interface
Hi Milan,
The l2_len field in the buffer metadata area is valid only for L2 forwarding
path. It is overlaid with other L3 forwarding related fields. Thus, packets
coming into a bridge domain (BD) will have its l2_len setup correctly. Once
the packet leave the BD via its BVI interface into
Sent: Monday, March 18, 2019 7:25 AM
To: Eyle Brinkhuis ; vpp-dev@lists.fd.io; John Lo
(loj)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Support for non TCP traffic
If the idea is simply to flood and/or forward at L2 these ethertypes, there’s a
decent chance you won’t have to do anything beyond
Hi Joe,
Thank you very much for catching this bug. I took a look at your patch which
looks to be the right fix to this problem. Without this fix, I suppose the
work around is to always add BVI interface to a BD last, after all other
interfaces are added in the BD.
Can you push your patch to
Congratulations Paul. It is great to have you on board as one of the
committers to share the load, I mean “joy” , of VPP. -John
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
Lists.Fd.Io
Sent: Thursday, February 28, 2019 5:38 PM
To: vpp-dev@lists.fd.io; Paul Vinciguerra
Cc:
+1 from me. -John
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
Lists.Fd.Io
Sent: Wednesday, February 27, 2019 7:38 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra
In view of significant code contributions
From “show interface” output, the rx/tx counters of TenGE4/0/0 matches that of
tx/rx counters of 4/0/1. So L2XC is working between them. For the other L2XC
pair, the rx counter of TenGE7/0/1 matches that of the tx counter of 7/0/0 so
that also seem fine. The rx of TenGE7/0/0 and tx of 7/0/1
One can put the BD BVI interfaces into its own IP table and leave VXLAN encap
and underlay in default global IP table. We would put the loopN interface into
an IP table before assigning its IP address:
vpp# set int ip table ?
set interface ip table set interface ip table
-Original Message-
From: Neale Ranns (nranns)
Sent: Monday, November 05, 2018 11:00 AM
To: John Lo (loj) ; Xuekun ; Eyal Bari
(ebari) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Problem on VxLAN multicast mode
Hi Eyal, John,
I missed the fact that the tunnel classification is based
VPP does not support receiving of VXLAN packets from an unknown VTEP. Thus,
any packet received in a BD from a VXLAN multicast tunnel must have its source
IP match of the remote VTEP of an existing VXLAN unicast tunnel in the same BD.
If no such unicast tunnel is found, packets are dropped.
孙 via Lists.Fd.Io"
mailto:saint_sun=aliyun@lists.fd.io>>
Reply-To: "saint_...@aliyun.com<mailto:saint_...@aliyun.com>"
mailto:saint_...@aliyun.com>>
Date: Wednesday, October 24, 2018 at 8:07 PM
To: "John Lo (loj)" mailto:l...@cisco.com>>
Cc: "v
in this email (I did change the
email subject accordingly)? -John
From: saint_sun 孙
Sent: Wednesday, October 24, 2018 8:52 PM
To: John Lo (loj)
Subject: Re: RE: RE: [vpp-dev]vlan interface support?
I am very grateful for your help.
And when I test the VLAN, maybe I find a bug that if I switch the mode
I believe you can cross connect two gtpu tunnel interfaces on the VPP in your
GW to achieve what you need:
DBGvpp# set int l2 xconnect ?
set interface l2 xconnectset interface l2 xconnect
You need to set L2 xconnect on both gtpu tunnel interfaces to each other.
Regards,
further.
If your requirement is to have IP in IP tunnel, GRE tunnel may be a better
choice which is fully supported by VPP. Then everything will be handled in L3
only.
Regards,
John
From: Zhang, Yuwei1
Sent: Monday, October 22, 2018 10:44 PM
To: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: RE
wei1
Sent: Monday, October 22, 2018 4:50 AM
To: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] one question IP checksum
Hi John, thanks for your instructions, I tried to use your method with below
steps:
1) Create tunnel: vppctl create vxlan tunnel src 10.0.0.1 dst 10.0.0.2 vni
24 en
. If
underlay is IPv6, then UDP checksum would be required and VPP would set it on
VXLAN encap.
Regards,
John
From: Zhang, Yuwei1
Sent: Saturday, October 20, 2018 9:58 AM
To: John Lo (loj) ; vpp-dev@lists.fd.io
Cc: Yang, Zhiyong
Subject: RE: [vpp-dev] one question IP checksum
Thanks a lot for your
The IP path after receiving a VXLAN packet is processing the outer IP header
and not the inner one. The payload of VXLAN packet is expected to be an
ethernet packet. After VXLAN decap, the payload ethernet packet will be
processed in L2 forwarding path where no IP processing is involved.
If
I have no idea what you are trying to do with PPPoE. From an L2 forwarding
point of view, however, you need to put interfaces into the same bridge domain
(BD) so they can forward packets to each other. If you have only two
interfaces to send packets to each other, you can L2 cross connect
Hi Jeff,
It was not intentional. The commit you mentioned was addressing tunnel
implementations in VPP which uses similar encap/decap approach with
vnet/src/vxlan as the model or “template”. L2TP uses different encap/decap
approach so was not included.
With respect to the dummy tx function,
The interface is in L3 mode. Thus, VPP will only allow packets whose
destination MAC is the same as the interface MAC or bcast/mcast MAC. The
error “l3 mac mismatch” means the DMAC here “52:54:00:ea:ca:a5“ is not the same
as the MAC of the interface. -John
From:
” if the sub-interface has one VLAN tag.–John
From: saint_sun 孙
Sent: Monday, October 15, 2018 2:42 AM
To: John Lo (loj)
Cc: vpp-dev@lists.fd.io
Subject: Re: RE: [vpp-dev]vlan interface support?
I am very grateful to you for your advice!
I have tested it,But there is something wrong. when I
Hi Xue,
L2VPN/EVPN is a pretty generic area including many things. You need to be more
specific about what additional things you expect VPP to do for your usage of
L2VPN/EVPN. Note that if you are thing of protocol related handling for
L2VPN/EVPN, then it won’t be supported as VPP is really
The equivalent of VLAN on a switch in VPP is a bridge domain or BD for short.
One can put interfaces or VLAN sub-interfaces in a BD to form a L2 network
among all interfaces in it. One can also create a loopback interface, put it
in a BD as its BVI (Bridge Virtual Interface) and assign IP
Sent: Thursday, October 11, 2018 11:29 AM
To: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Verification always fail with stable/1801
Yes, there's troubles with 2 things:
1) package naming
2) packagecloud bionic "repo"
Both things are getting addressed.
HTH,
Marco
On Thu,
It seems verifications are always failing for patches on stable/1801 branch.
Does anyone know why?
The following patch with a simple one line change is an example which fails all
3 verification attempts:
https://gerrit.fd.io/r/#/c/15222/
Regards,
John
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive
When a sub-interface is created, matching of tags on the packet to the
sub-interface can be specified as “exact-match”. With exact-match, packet must
have the same number of tags with values matching that specified for the
sub-interface. Otherwise, packets will belong to the best matched
Hi Xue,
VPP does support L2VPN with SR-MPLS in latest master, possibly the just
released 18.07.1 point release. I only verified it on master and not 18.07.1
myself.
Assume we created an SR-MPLS policy:
sr mpls policy add bsid 993 next 104 next 105 next 106
We can then create a MPLS tunnel
VPP has supported IPv6 NA/NS for a while. I believe this process was added for
VPP to support RS/RA.
Ole, Can you confirm if my understanding is correct?
Regards,
John
From: vpp-dev@lists.fd.io On Behalf Of sheckman
Sent: Tuesday, September 18, 2018 6:29 PM
To: John Lo (loj) ; Dave Barach
In 1804 the rd-cp-process would run frequently in the main thread to cause your
observation of CPU usage. It can be observed in your "show run" output under
main thread that this process went through suspend/run cycle many times
(highlighted in bold red below).
This was fixed under Jira
Since qsort.c from vppinfra has the buffer overflow issue, shall we delete this
file to avoid causing more confusion in the future? -John
From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via
Lists.Fd.Io
Sent: Friday, September 07, 2018 4:30 AM
To: Damjan Marion
Cc: vpp-dev@lists.fd.io
Disabling a feature on an interface will not change the graph arcs, as stated
by Dave. The more relevant CLI is to use “show interface features
” to check whether a particular feature is enabled on an
interface or not.–John
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
VPP interface by default is in L3 mode and has to be set into L2 mode for
either bridging or cross connect. The reason, setting up an interface cross
connected to the 2nd interface only does not work, is that the second interface
is not in L2 mode. Thus, L2 forwarding cannot output packets on
When you have a full mesh of tunnels among PE routers, the split horizon group
(SHG) of these tunnels should be set to a non-zero value, e.g. 1, to prevent
loops. Thus, packets received from an interface with a non-zero SHG will not be
replicated or broadcasted to another interface in the
Packet drop with unresolved IP neighbor adjacency is the expected behavior. As
the packet will trigger an ARP request to resolve the adjacency, subsequent
packets with the same destination address will start to flow if the adjacency
is resolved on receiving a reply. -John
From:
: Thursday, June 14, 2018 4:40 PM
To: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: Re: [**EXTERNAL**] Re: [vpp-dev] GET/SET support for each feature
entity from VPP client
Thanks John. Are these “dump” and “details” defined for all the different
entities that a VPP client configure? Like Interfaces
You can find L2 bridging related APIs from the file src/vnet/l2/l2.api. The
API to get bridge domain state is bridge_domain_dump and the response info
provided is bridge_domain_details. The API to change bridge domain attributes
is bridge_flags. The API to set bridge domain aging interval is
On VPP, packets with VLANs does not imply it go into a separate bridge domains
(BDs). For your case, your sub-interfaces for VLAN 100 and 200 on your host
interface should be put into separate bridge domains, e.g. you can use BD IDs
100 and 200, and have the correct behavior. As I described
to work,
John
From: Mehran Memarnejad <memarnejad...@gmail.com>
Sent: Sunday, May 27, 2018 9:04 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev@lists.fd.io
Subject: Re: dot1ad tag
Does the efp-filter work base on the second tag??
As far as I experiment, I realized that each subinterf
the efp-filter would also check
the packet after VTR operation contain VLAN tag matching that of the output
sub-interface.
Regards,
John
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of John Lo (loj)
Sent: Sunday, May 27, 2018 8:30 PM
To: Mehran Memarnejad <memarnejad...@
. It just make L2
forwarding slower because of the VLAN tag push/pop overhead on each packet and
does not serve any purpose, AFAIK. -John
From: Mehran Memarnejad <memarnejad...@gmail.com>
Sent: Sunday, May 27, 2018 8:56 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re
I just submitted a patch. Can you give it a try if this resolve the problem?
-John
https://gerrit.fd.io/r/#/c/12750/
From: Mehran Memarnejad <memarnejad...@gmail.com>
Sent: Friday, May 25, 2018 1:24 PM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re: dot1ad tag
5, 2018 4:40 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re: dot1ad tag
Sw_if_index 6 is the mpls tunnel0 and sw_if_index 3 is the GigabitEthernet5/0/0
on which I have set interface tag-rewrite push dot1ad 12 (both of them are
attached to bridge1)
Gigabitethe
Hi Mehran,
The packet trace shows drop is cause by l2-output node when the packet is sent
on the interface with sw_if_index 3 where the output tag-rewrite operation is
not expecting packet with a dot1ad tag of 12. What is the interface with
sw_if_index of 3 on that PE? Is this the same
The MAC for a loopback is added to the L2FIB only when the loopback interface
is added to a BD as BVI. If loopback MAC of a BVI is changed subsequently,
there is no mechanism to automatically update its MAC in the L2FIB. -John
From: vpp-dev@lists.fd.io On Behalf Of
;xy...@fiberhome.com>
Sent: Wednesday, May 16, 2018 8:07 AM
To: John Lo (loj) <l...@cisco.com>; Neale Ranns (nranns) <nra...@cisco.com>;
vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: Re: [vpp-dev] problem in xcrw testing
Hi John,
I changed my configuration to that shown below:
cr
the other interface
as source/input so it will also be in L2 mode.
Hope this help, with regards,
John
From: 薛欣颖 <xy...@fiberhome.com>
Sent: Wednesday, May 16, 2018 3:46 AM
To: John Lo (loj) <l...@cisco.com>; Neale Ranns (nranns) <nra...@cisco.com>;
vpp-dev <vpp-dev@lists.f
ohn Lo (loj) <l...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Static ARP Flag Question
On Thu, May 10, 2018 at 7:28 PM, John Lo (loj)
<l...@cisco.com<mailto:l...@cisco.com>> wrote:
Hi Jon,
Hi John,
This is not the right behavior.
I had th
The GRE tunnel needs to be put in L2 mode so it can be a valid l2-output
interface. You can do that by putting the GRE tunnel into a bridge domain, or
xconnect it to peer interface:
vpp# set int l2 bri ?
set interface l2 bridge set interface l2 bridge
[bvi] [shg]
vpp# set
Hi Jon,
This is not the right behavior. I think it is caused by reuse of a static ARP
entry in the IP4 neighbor pool with static bit still set. The code merely set
the dynamic bit in the flags but left the static bit untouched (similarly for
the static path) in arp.c function
Hi Matt,
SPAN without L2 is putting the packet mirror on an interface (only main
interface) input and/or output irrespectively of it in L2 or L3 mode.
SPAN with L2 means to perform packet mirror on L2 input and/or output on an
interface or sub-interface which is in a bridge domain or cross
. -John
-Original Message-
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of John Lo (loj)
Sent: Thursday, April 19, 2018 4:48 PM
To: carlito nueno <carlitonu...@gmail.com>; Andrew Yourtchenko
<ayour...@gmail.com>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp
The config looks correct and should work, assuming the following:
1. The devices connected to GigabitEthernet0/14/0.2 have IP addresses in the
192.168.2.1/24 subnet with default gateway set to that of the BVI IP address of
192.168.2.1.
2. The devices connected to GigabitEthernet0/14/0.3 have IP
As noted by Billy, vec_validate would call vec_resize and then call memset() to
clear unused area to 0. This call is required to make sure, if vector is
expanded by vec_resize without having to allocate new memory, any unused memory
with stale content is cleared.
For new vectors, calling
Hi Tom,
On your gerrit page for these patches, you can just click the "Cherry Pick"
bottom and choose stable/1804 branch.
Regards,
John
From: vpp-dev@lists.fd.io On Behalf Of Thomas F Herbert
Sent: Friday, April 06, 2018 2:38 PM
To: vpp-dev@lists.fd.io
Cc: vpp-dev
Thanks for your help, Marek. That worked. -John
From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
Sent: Friday, April 06, 2018 1:58 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: RE: My patch kept failing Ubuntu 16.04 verification
Hi,
You need to
Hi all,
I submitted a patch https://gerrit.fd.io/r/#/c/11553/ which failed the verify
job on Ubuntu 16.04 in 5 consecutive tries. 4 of the 5 failures all started
similarly - not able to run "JVPP Core Test Case" where console output showed
failure with temp dir in use and tracebacks. These
It is described here:
https://wiki.fd.io/view/VPP/Using_VPP_as_a_VXLAN_Tunnel_Terminator#BVI_Interface_Creation_and_Setup
Regards,
John
From: vpp-dev@lists.fd.io On Behalf Of xulang
Sent: Monday, April 02, 2018 6:17 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] vpp bridge
, Leela Sankar <lgudi...@ciena.com>
Sent: Thursday, March 22, 2018 4:46 PM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: Re: [**EXTERNAL**] RE: [vpp-dev] Is IRB feature fully functional?
Thanks John for quick response.
Yes. I placed sub-interface in the BD
In order to use a sub-interface on a loopback interface as BVI of a BD, the
sub-interface should be placed in a BD and the IP address configured on the
sub-interface (in your case, sub-interface with VLAN tag 50 and not the main
interface). The sub-interface must be configured as an exact
Hi Sara,
To address your question on “show err”, your output is displaying running
counts for the l2-output, l2-learn and l2-input node wrt how many packets each
node processed. These are not error counts, unless the “Reason” column
indicate some kind of error. The CLI name “show err” is
The functions in the area you are interested may be the unformat functions
unformat_vnet_sw_interface(), unformat_vnet_hw_interface() in
src/vnet/interface_format.c used by VPP CLI to get sw_if_index or hw_if_index
from user specified interface name.-John
-Original Message-
From:
1 - 100 of 180 matches
Mail list logo