Hi Jon,
That is a good idea. Please submit a patch.
Regards,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, March 12, 2018 10:54 AM
To: vpp-dev <vpp-dev@lists.fd.io>; John Lo (loj) <l...@cisco.com>
Subject: A Question about SPAN Dump Details
John, et al,
-dev@lists.fd.io] On Behalf Of John Lo
(loj)
Sent: Friday, February 23, 2018 5:44 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VXLAN Instances Not Freed Properly?
Hi Jon,
I see the problem in the delete path where the hash_unset() call is using the
tunnel instance instead of the user_instance
Do you mind submit a patch to fix it, please?
Regards,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Friday, February 23, 2018 4:57 PM
To: vpp-dev <vpp-dev@lists.fd.io>; John Lo (loj) <l...@cisco.com>
Subject: VXLAN Instances Not Freed Properly?
John, et al,
Hi Avi,
I do not have direct experience myself but someone told me Mellanox DPDK driver
is broken with DPDK 17.11. You may need to rebuild VPP 18.01 with DPDK 17.08 to
get Melllanox NICs to work. Hopefully someone with direct Mellanox experience
can add more details.
Regards,
John
where a requested
instance is not available, I wonder how control plane should handle the error
condition if it does not check the result of the VXLAN create request… -John
From: Neale Ranns (nranns)
Sent: Wednesday, February 07, 2018 5:55 AM
To: Jon Loeliger <j...@netgate.com>; John Lo (l
..@cisco.com>>; Florin Coras
(fcoras) <fco...@cisco.com<mailto:fco...@cisco.com>>; John Lo (loj)
<l...@cisco.com<mailto:l...@cisco.com>>; Luke, Chris
<chris_l...@comcast.com<mailto:chris_l...@comcast.com>>; Damjan Marion
(damarion) <damar...@cisco.co
will submit my GRE patch for review sometime later and add you as one of the
reviewers.
Thanks,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, February 05, 2018 2:26 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] VXLAN Tun
One more thang, I would prefer to have a u32 instance number instead of the 64
bytes if_name in the vxlan_tunnel_details API. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of John Lo (loj)
Sent: Monday, February 05, 2018 12:43 PM
To: Jon Loeliger &l
Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, February 05, 2018 11:49 AM
To: John Lo (loj) <l...@cisco.com>
Cc: Dave Barach (dbarach) <dbar...@cisco.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] VXLAN Tunnel IF Names
On Mon, Feb 5, 2018 at 9:55 AM, Jon Loelig
uffice as ~0
can be used to state “not specified” rather than having an additional parameter
“renumber”, although I can accept either way.
Regards,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Sunday, February 04, 2018 3:38 PM
To: John Lo (loj) <l...@cisco.com>; Dave Barach (db
, 2018 4:18 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] VXLAN Tunnel IF Names
On Fri, Feb 2, 2018 at 3:08 PM, Jon Loeliger
<j...@netgate.com<mailto:j...@netgate.com>> wrote:
I have submitted a patch to Gerrit. When this p
Hi Jon,
All VPP tunnel creation uses the mechanism of returning a sw_if_index of the
created tunnel. The name of the tunnel is then followed by a number being the
instance or index to the tunnel struct vector. Thus, the first VXLAN tunnel
created is called vxlan_tunnel0 followed by
Hi Andrea,
Typically a tunnel used for tx/rx of L3/IP payload would have IP address and
optionally table-id set on the interface. It will then allow packets to be
routed into the tunnel for tx and, for rx packets, forward the payload IP
packets using the correct fib-index.
I see that you are
To: Lollita Liu <lollita@ericsson.com>; John Lo (loj) <l...@cisco.com>;
vpp-dev@lists.fd.io
Cc: Kingwel Xie <kingwel@ericsson.com>; David Yu Z
<david.z...@ericsson.com>; Terry Zhang Z <terry.z.zh...@ericsson.com>; Jordy
You <jordy@ericsson.com>
Subjec
Hi Lolita,
Thank you for providing information from your performance test with observed
behavior and problems.
On interface creation, including tunnels, VPP always creates dedicated output
and tx nodes for each interface. As you correctly observed, these dedicated tx
and output nodes are not
to check how it is set up and
tested. The test cases include L2 ones with mirrored packet output to VLAN
sub-interfaces and VXLAN tunnels.
Regards,
John
From: Juraj Linkeš [mailto:juraj.lin...@pantheon.tech]
Sent: Thursday, January 18, 2018 11:14 AM
To: John Lo (loj) <l...@cisco.com>; Damjan
For VPP 18.01 and master, SPAN has been enhanced to allow port mirroring for
interface in L2 mode such as ones in bridge domains. There is a “L2” argument
added to the SPAN CLI/API which allow any interface, including vHost, to have
packet replicated on its L2 input and/or output paths and be
The API is sw_interface_set_mac_address defined in src/vnet/interface.api.
-John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Omer Majeed
Sent: Wednesday, December 13, 2017 9:59 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] :: Modify Mac address of
In L2 mode, the ethernet interface will be put in promiscuous mode to receive
all packets on the wire. In L3 mode, it will only receive packets whose
destination MAC is that of the interface. What you observe is the expected
behavior. -John
From: vpp-dev-boun...@lists.fd.io
0, 2017 11:58 AM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev@lists.fd.io
Subject: Anyone using the l2 classify path these days?
Dear John,
I'm wondering about copying e0->metadata into vlib_buffer (b)->l2_classify.xxx
in l2_input_classify. On the face of it, that seems reason
Yes, I can confirm using LF password does work while https password failed.
-John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Andrew Yourtchenko
Sent: Thursday, October 19, 2017 1:29 PM
To: Luke, Chris
Cc: vpp-dev@lists.fd.io
Hi Dave,
I found quite a few places using this mechanism:
*In the input ACL support for PBR, there is an action to switch FIB
table and the code uses this mechanism to specify which ones to use:
*** src/vnet/ip/ip_input_acl.c:
ip_inacl_inline[290] vnet_buffer
The "proper" CLI is "show node counters" which displays stats kept by various
graph nodes including normal operation counts and possibly error counts. The
CLI "sho err" is historical and was kept for backward compatibilities. The old
CLI is somewhat misleading but is quicker to type then the
I am able to use memfd with 14.04 by updating its kernel to 3.19 (my 14.04
kernel was 3.13 before the update).
I also had to add the following to /usr/include/x86_64-linux-gnu/asm/unistd_64.h
#define __NR_memfd_create 319
Hope this works for you,
John
From: vpp-dev-boun...@lists.fd.io
There was a patch recently merged in mater/17.10:
https://gerrit.fd.io/r/#/c/8464/
Can you try the latest image from master/17.10 or apply the patch it into your
17.07 tree and rebuild?
Regards,
John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Balaji Kn
Hi Marco,
I am not sure this can work. After VXLAN encap, there is no IP lookup (as it is
expensive) so it won't naturally follow the IP for-us path to ip4-local and
ip4-udp-lookup and vxlan-input nodes. Instead, packet forwarding will follow
the DPO forwarding chain setup by L3 FIB for the
Looking at the new result, it appears that PNIC to PNIC performance mostly
degrade slightly while PNIC to VM to PNIC performance mostly improved slightly
or same from 17.04 to master. Does that seem right to you, Maciek?
The L2FIB scale fix has been merged to both master and 17.07 already.
ode, how many packets were processed for each call, average clocks used
by each node to process a packet. We can then compare the difference between
1704 and 1707 to get more clues.
Regards,
John
From: Billy McFall [mailto:bmcf...@redhat.com]
Sent: Thursday, August 17, 2017 2:14 PM
To: John Lo (
Hi Abhilash,
For L3 forwarding, incoming L2 header, including any VLAN tags, will be removed
and be replaced by an outgoing L2 header as appropriate for the output
interface. Why would you need to strip any VLAN tags on input?
Regards,
John
From: vpp-dev-boun...@lists.fd.io
Hi Billy,
The output of “show l2fib” is showing how many MAC entries exist in the L2FIB
and is not relevant to the size of L2FIB table. The L2FIB table size is not
configurable. It is a bi-hash table with size set by the following #def’s in
l2_fib.h and has not changed for quite a while,
If an interface does not have IP4 address configured, you will see the
ip4-unitcast feature listed as ip4-drop:
ip4-unicast:
ip4-drop
Regards,
John
From: Balaji Kn [mailto:balaji.s...@gmail.com]
Sent: Friday, August 04, 2017 7:28 AM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev@lists
+1 -John
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Neale Ranns (nranns)
Sent: Thursday, August 03, 2017 3:57 AM
To: vpp-dev@lists.fd.io; csit-...@lists.fd.io; honeycomb-...@lists.fd.io
Subject: [vpp-dev] API Change
Hi Balaji,
In order to make input ACL work on the IPv4 forwarding path, you need to set it
as ip4-table on the interface or sub-interface. For your case for packets with
VLAN tags, it needs to be set on sub-interface:
set int input acl intfc TenGigabitEthernet1/0/0.100 ip4-table 0
The names in
Hi Alessio,
The mechanism you are using to handle ethertype works only when the interface
is in L3 mode which is the default, unless an interface is set to L2 bridging
(or xconnect) mode. When an interface is in L2 mode, VPP will always get into
l2-input mode to forward ethernet packet based
I enjoyed the presentation of using VPP with ClearContainers last week, during
one of our weekly fd.io VPP meetings, on July 18.
I believe the session was recorded. Does anyone have the webex recording URL of
the session, please?
Regards,
John
___
I wonder whether VirtualEthernet0/0/1 has been deleted and created again while
sub-interface BonEthernet0.1514 was created in between. Looking at the
sw_if_index for these interfaces:
·VirtualEthernet0/0/0 => 5
·BonEthernet0.1514 => 6
·VirtualEthernet0/0/1 => 7
I
These flush tests should be disabled for now, until Eyal put in a fix. It has
to do with timing, that after flush, there is a slight delay before ager run to
scan the FIB to delete the stale MACs. We are adding extra code in the L2
forwarding path to fix this issue. There is an ongoing patch
Hi Jon,
The difference between the two sub-interface create APIs is that
create_vlan_subif is typically used for creating a sub-interface for L3 IP
forwarding where you just specify two parameters: sw_if_index of the main
interface and the VLAN ID. It create a sub-interface using the same
The output of clib_warning() call should be in the syslog. If running vpp in
Ubuntu, take a look in /var/log/syslog. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Alessio Silvestro
Sent: Thursday, June 01, 2017 12:11 PM
To: Luke, Chris
)
Sent: Tuesday, May 30, 2017 2:33 PM
To: John Lo (loj) <l...@cisco.com>; Juraj Linkes -X (jlinkes - PANTHEON
TECHNOLOGIES at Cisco) <jlin...@cisco.com>; otr...@employees.org
Cc: Wojciech Dec (wdec) <w...@cisco.com>; fds-...@lists.opnfv.org;
vpp-dev@lists.fd.io
Subject: Re: [vpp-d
DPDK is moved to the plugin package vpp-plugins_17.04-release_amd64.deb since
17.04 or later. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Dharmaray Kundargi
Sent: Thursday, May 25, 2017 6:21 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] : VPP
Hi Juraj,
For an interface in L3 mode, any packet received with a VLAN tag must match a
sub-interface setup to expect that VLAN tag value. A way to handle this may be
to create a sub-interface matching VLAN 0, such as:
DBGvpp# create sub tuntap-0 0
tuntap-0.0
DBGvpp# sho int
Name
Hi Jon,
Appreciate your nicely written lament of the missing API. I fully accept your
point about API changes, especially removal of existing ones, should be given
heads up in the vpp-dev alias before it merges in the code base.
I merged this change for VPP L2 API as it is a nice cleanup for
Hi Mina,
The packet is forwarded in IP4 forwarding path so the ACL should definitely be
placed with the ip4-table option and not l2-table option.
According to the packet trace, ip4-inacl node is invoked on packet received on
sw_if_index 9 and used classify table index 1 to process it. You can
The patch for dpdk-input node to use etype is:
https://gerrit.fd.io/r/#/c/5563/
It is in 1704 or newer VPP and would match with your observation.
Regards,
John
From: Nagaprabhanjan Bellaru [mailto:nagp.li...@gmail.com]
Sent: Thursday, May 11, 2017 7:39 AM
To: John Lo (loj) <l...@cisco.com&
of
an Ethernet header with no VLAN tag and thus not quite usable.
Regards,
John
From: 薛欣颖 [mailto:xy...@fiberhome.com]
Sent: Wednesday, May 03, 2017 10:11 PM
To: John Lo (loj) <l...@cisco.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: 回复: 回复: [vpp-dev] ACL match tunnel interface
A detailed
If you are using classification CLI’s high level parameters to match l2/l3 etc,
it is generating bit mask for tables and match hex values for sessions assuming
matching from start of the received packet, thus always matching the outer L2
and L3 headers. These high level CLI parameter will not
That’s great, Jon. Please add me as a reviewer for this new patch.
Thanks for your help,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, May 01, 2017 7:47 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Bridge Dom
Hi Jon,
I agree we should fix CLI/API to not allow BD 0 modifications. Would you be
interested to submit a patch for it? ☺ Otherwise, I will try to fix it when I
get a chance.
Regards,
John
From: Jon Loeliger [mailto:j...@netgate.com]
Sent: Monday, May 01, 2017 7:10 PM
To: John Lo (loj) &l
Hi Jon,
The bridge domain (BD) 0 is created by VPP on startup to be a dummy BD and not
intended to be used by user. BD 0 is created with everything turned off to drop
packets in it. It is used by VPP to handle the transition of changing interface
between L2 bridging and L3 mode so that if a
Hi Hongjun,
How is the packet forwarded between Ethernet-input -> ... -> Tx to phy
interface? Is it via L2 or L3 forwarding? I am guessing it is L3 forwarding
thus this check for ethernet-input.
If it is L2 forwarded and the tunnel interface can be changed to L2 mode, this
MAC address
Please take the latest 1704 version with v17.04-rc1…. and see if it works
better. -John
From: John Pearson [mailto:johnpearson...@gmail.com]
Sent: Thursday, March 30, 2017 8:32 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] vdev bonding -- carrier do
Which version of VPP are you using? Is it latest from either 1704 or master?
After VPP moved to DPDK 17.02, there were some breakages with bonded interface
PMD that was fixes via these patches:
https://gerrit.fd.io/r/#/c/5786/
https://gerrit.fd.io/r/#/c/5788/
Regards,
John
From:
I may not have fully answered all the original questions. Added extra edit to
my original reply in bold. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of John Lo (loj)
Sent: Tuesday, March 14, 2017 4:41 PM
To: Dumitrescu, Cristian <cristian.dumi
Hi Cristian,
If the interface is in L3 routing mode, packets with VLAN tags, either one or
two, will need to match a sub-interface or will be dropped. It is not just QinQ
packets that are dropped.
Once the packet is received, however, the VLAN tags are not removed in the L3
input processing
,
John
From: Matej Klotton -X (mklotton - PANTHEON TECHNOLOGIES at Cisco)
Sent: Thursday, March 09, 2017 3:39 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Cc: csit-...@lists.fd.io
Subject: RE: [vpp-dev] [csit-dev] VPP receive no tagged packet on Virtio
interface
Hi John,
Hi Matej,
Do you know which NIC/DPDK-driver it is? I do know that ENIC driver by default
is initialized with VLAN tag striped, because it is more efficient with the
VNIC setup on the VIC NIC. Thus it needs to be explicitly disabled in startup
config.
For other NIC/driver's, they are left as
] On
Behalf Of John Lo (loj)
Sent: Wednesday, March 08, 2017 9:45 PM
To: Matej Klotton -X (mklotton - PANTHEON TECHNOLOGIES at Cisco)
<mklot...@cisco.com>; vpp-dev@lists.fd.io
Cc: csit-...@lists.fd.io
Subject: Re: [vpp-dev] [csit-dev] VPP receive no tagged packet on Virtio
interface
Hi
Hi Matej,
The difference between having an interface in L2 bridge/xconnect mode is that
the interface is put into promiscuous mode. Thus the interface will receive all
packets irrespective of its destination MAC address. When an interface is in L3
mode, it will receive packets with DMAC
Thanks Dave, I will clean up the one in api.c which is obsolete.
Thanks for letting me know,
John
From: Dave Barach (dbarach)
Sent: Thursday, March 02, 2017 12:38 PM
To: John Lo (loj) <l...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: sw_interface_set_vxlan_bypass API
Hi Jon,
The CLI is intended for human user. One can thus create an interface, use “show
int” to see the name of the created interface and use it for subsequent CLIs on
that interface.
The API calls expect the caller to specify sw_if_index of an interface to be
configured. The interface
For VPP, the number of queues on a device can be specified in the DPDK portion
of the startup config, which default to 1. This is usually documented in as
comments in the startup.conf template file when installing VPP rpm/deb on the
target Linux OS. Following is the dpdk portion from the
, 2017 7:10 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: RE: [vpp-dev] How to setup BVI with a ip address?
Hi John,
I want to add access bvi like the example you given, but it doesn't work, the
config looks like following:
set interfa
We do have products that still need to support running vpp 17.04 on Ubuntu
14.04 VMs. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Dave Barach (dbarach)
Sent: Tuesday, January 24, 2017 2:04 PM
To: Ed Warnicke ; vpp-dev
Bellaru [mailto:nagp.li...@gmail.com]
Sent: Friday, January 13, 2017 2:21 PM
To: John Lo (loj) <l...@cisco.com>
Cc: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco)
<jgel...@cisco.com>; vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] L2 Xconnect does not re-write vlan
interface and then have output interface tag pushed on output. That’s why two
vtr operations are performed per packet.
Regards,
John
From: Nagaprabhanjan Bellaru [mailto:nagp.li...@gmail.com]
Sent: Friday, January 13, 2017 1:50 PM
To: John Lo (loj) <l...@cisco.com>
Cc: Jan Gelety -X (jgelety - PA
If doing tag1 to tag2 translation as suggested, only need to do it on one
interface. Whatever is specified on an interface will be performed on input
while the opposite will be performed on output. Using pop on both interfaces,
as suggested in my other reply, is more straightforward but is
nd
preferably built with debug enabled (with TAG-vpp_debug) so it is easier to
find any issues.
Regards,
John
From: Dave Barach (dbarach)
Sent: Wednesday, January 11, 2017 9:01 AM
To: Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)
<jlin...@cisco.com>; vpp-dev@lists.fd.io; Joh
: Tuesday, January 10, 2017 10:00 AM
To: John Lo (loj) <l...@cisco.com>; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] Deleting VXLAN interface doesn't delete it from
interface dump
Reusing removed VXLAN interfaces sounds good.
However I put deleted vxlan_tunnel interface UP, then assign it to a
https://wiki.fd.io/view/VPP/Command-line_Arguments#.22dpdk.22_parameters
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of yug...@telincn.com
Sent: Wednesday, December 14, 2016 10:53 PM
To: vpp-dev
Subject: [vpp-dev] startup.conf
Hi, all
The tuntap-tx node in VPP does not save any data to support packet trace.
That’s why you do see any packet trace after error-punt. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Dave Barach (dbarach)
Sent: Friday, November 18, 2016 8:23 AM
To: Prerit
For VPP 16.09, doxgen generated documentation can be found here:
https://docs.fd.io/vpp/16.09/
Regards,
John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of yug...@telincn.com
Sent: Friday, November 11, 2016 11:16 PM
To: vpp-dev
Subject: [vpp-dev] Doxygen
Hi
--Original Message-
From: Ivan Kelly [mailto:i...@midokura.com]
Sent: Thursday, November 03, 2016 5:34 PM
To: John Lo (loj); vpp-dev
Subject: Re: [vpp-dev] ip4-lookup to vxlan and vice versa
Oops, forgot to include list.
On Thu, Nov 3, 2016 at 10:32 PM, Ivan Kelly <i...@midokura.com>
default gateway is pretty unusual. There will usually be a
particular remote BVI which can reach a particular subnet.
Regards,
John
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of John Lo (loj)
Sent: Thursday, November 03, 2016
Hi Ivan,
VXLAN tunnel is usually associated with a BD (bridge domain) and always send
ethernet packets as payload. So ethernet header should exist on packets
received at the remote VXLAN tunnel end point. It is confusing why you stated
remote side OVS does not see any L2 header.
On VPP side,
Admittedly VAT does not call every binary APIs but it is pretty complete.
Regards,
John
From: Keith Burns [mailto:alaga...@gmail.com]
Sent: Thursday, November 03, 2016 10:29 AM
To: John Lo (loj); Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES at
Cisco); vpp-dev
Subject: Re: [vpp-dev
That sounds like a good idea to me, to allow both possibilities. It would be
good to have more descriptive names.
I agree gdbserver is harder to use. It does, however, help with the following:
1. The problem of having to run gdb as root, as mentioned by Klement.
2. It lets me do target remote
+1 -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Florin Coras
Sent: Wednesday, October 26, 2016 1:42 PM
To: Dave Barach (dbarach)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP project committer nomination: Neale Ranns
+1
Florin
On Oct 26,
) [mailto:daniel.bern...@bell.ca]
Sent: Friday, October 14, 2016 1:57 PM
To: John Lo (loj)
Cc: vpp-dev@lists.fd.io
Subject: Re: bond interfaces in VPP
Thanks
As any work been done on the other modes (ie lacp) ?
Thanks
Daniel Bernier
Sent from my iphone
On Oct 6, 2016, at 4:03 PM, John Lo (loj
Hi Neal,
I believe David is using GRE tunnel in transparent ethernet bridging (TEB)
mode, to carry ethernet packet to a bridge domain. For the TEB case, the GRE
tunnel is created like an ethernet interface with calls to
register_etehrnet_interface using a MAC that's (d00b:eed0: +
101 - 180 of 180 matches
Mail list logo