Whether there is a calendar event or not is up to our fearless Release
Manager for 17.01: Damjan.
I would suggest to him that it can probably be handled async via email/IRC
in a light weight fashion if he so chooses :)
Ed
On Fri, Jan 13, 2017 at 2:58 PM, Vanessa Valderrama <
vvalderr...@linuxfou
Ed,
Thank you I appreciate it. Also if there is a calendar event for the
release please be sure I am included on the invite.
Thanks,
Vanessa
On 01/13/2017 03:43 PM, Ed Warnicke wrote:
> Vanessa,
>
> Rather than enumerate the current artifacts here for vpp, I've updated
> the instructions here
Vanessa,
Rather than enumerate the current artifacts here for vpp, I've updated the
instructions here:
https://wiki.fd.io/view/VPP/CommitterTasks/CutRelease#helpdesk_email_template
to instruct the vpp person cutting the release to send a helpdesk email
from a template that *should* provide you s
Let me emphasize again, translate should be applied on one interface only and
not both. The reason you are seeing 3 tags on an interface in your earlier
experiment is because 1-2 and 2-1 translates were applied on both end of
xconnect interfaces respectively. -John
From: Nagaprabhanjan Bellar
Thanks all for the inputs. The pop approach is working fine for 1-2, 2-1,
1-1, 2-2. Checking why translate is not working.
-nagp
On Sat, Jan 14, 2017 at 12:27 AM, John Lo (loj) wrote:
> If using translate, it should be translate 1-1, so vtr will replace one
> tag on the packet with another tag.
If using translate, it should be translate 1-1, so vtr will replace one tag on
the packet with another tag. Then you only need to do it on one interface, to
replace its tag with the tag of the other interface.
If pop is used on both interfaces, a packet would have its tag poped on input
interfa
Many thanks for your replies Jan, John!
I tried translate1-2 and translate2-1, the ingress vlan is getting popped,
but the egress vlan stack instead of being (150|200), it became
(150|200|200) - i.e. there were three tags imposed on the packet, instead
of two. Looking into the issue.
John, by pop
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 less
L2 xconnect send packet as received to the other interface without any
modification. So the behavior you observed is correct. If you want to perform
VLAN tag translation to match the sub-interface, put an interface tag-rewrite
pop operation on both sub-interfaces. It will then pop the VLAN tag o
Hello nagp,
You need to use tag rewrite
l2_interface_vlan_tag_rewrite | sw_if_index [disable] [push-[1|2]]
[pop-[1|2]] [translate-1-[1|2]] [translate-2-[1|2]] [push_dot1q 0] tag1
tag2
on both interfaces.
-option translate-1-2 on sub-if1
-option translate-2-1 on sub-if2
Hi,
I have a L2 cross-connect configuration where packets arrive on a sub-if1
(with vlan id 500) and go out on sub-if2 (with a vlan stack 200, 150).
When I send packets on sub-if1, it is getting out on sub-if2, but the vlan
tags are not getting re-written. Is there anything else that should be do
On Thu, Jan 12, 2017 at 9:25 PM, Burt Silverman wrote:
> Cool. My suggestion would not have solved the issue, but looking at
> Damjan's .am files gives me a hint why the years ago project had issues,
> for example:
>
> libsvm_la_LIBADD = libvppinfra.la -lrt -lpthread
> libsvm_la_DEPENDENCIES = l
Please see https://gerrit.fd.io/r/#/c/4674. Lots more work to do, but as
given the tcp host stack manages to bring up tcp sessions.
Comments to me, Florin Coras (fco...@cisco.com), and/or Keith Burns
(k...@cisco.com).
Thanks. Dave
smime.p7s
Description: S/MIME cryptographic signature
13 matches
Mail list logo
