OK.
I see in your pcap file that there are many ARP requests generated. This is
would expect if nothing is responding.
Regards,
neale
From: on behalf of "Neale Ranns via Lists.Fd.Io"
Reply to: "Neale Ranns (nranns)"
Date: Monday 4 November 2019 at 10:27
To: vyshakh
Hi Vyshakh,
VPP does not support traceroute.
The only reason it does not, is that no kind soul has implemented it yet…
/neale
From: on behalf of vyshakh krishnan
Date: Wednesday 6 November 2019 at 08:16
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] traceroute in VPP
Hi All,
Does VPP
Hi Emma,
It is not necessary for VPP and the linux kernel to act the same way. They will
both have their own reasons for acting the way they do.
From VPP’s point of view, the general programming model for all objects, is
that if they were added explicitly by the user, then they must be
Hi Vyshakh,
I’ll look into it. Please give me a few days.
/neale
From: on behalf of vyshakh krishnan
Date: Monday 4 November 2019 at 05:51
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] VPWS not working when adjacency is not resolved
Hi All,
I have been trying to setup VPWS using VPP host
Hi,
If you’re refering to basic IP ECMP (as opposed to the LB plugin), then yes, it
uses a 5-tuple hash by default. You can configure this per-table with :
set_ip_flow_hash.
/neale
From: on behalf of Cipher Chen
Date: Monday 4 November 2019 at 04:21
To: "vpp-dev@lists.fd.io"
Subject:
Hi Ruijing,
Comments inline.
/neale
From: on behalf of "Guo, Ruijing"
Date: Thursday 31 October 2019 at 09:29
To: "Ni, Hongjun" , "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev] vpp with gtpu
Hi, Hongjun
After adding the configuration, ping still failed as:
Packet 14
00:02:10:052842:
>>
Subject: RE: [vpp-dev] VPP IPSec failed to add SA
Hi Neale,
I’m really new to VPP and can you tell me where’s the plugins you mentioned?
Thanks a lot.
Best Regards,
Ruoyu
From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
mailto:vpp-dev@lists.fd.io>> On Behalf Of Nea
Hi Raj,
Thanks for spending the time for further investigation. Some comments inline.
/neale
On 18/10/2019 11:27, "vpp-dev@lists.fd.io on behalf of Raj"
wrote:
On Thu, Oct 17, 2019 at 8:45 PM Neale Ranns (nranns)
wrote:
> I think your analysis is spot on. Thank you!
> How
nes registered by default or we need to manually register them?
Thanks.
Best Regards,
Ruoyu
From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
mailto:vpp-dev@lists.fd.io>> On Behalf Of Neale Ranns via
Lists.Fd.Io
Sent: Thursday, October 17, 2019 8:36 PM
To: Ying, Ruoyu mailto:ruoyu.y.
That will work.
Looking into the fixup function, all that's used from the session is the
ergress interface. So only that needs to be 'pushed'. I suspect using the whole
session was a convenience for the orignal author, whoever that might have been
...
/neale
On 17/10/2019 18:38, "Benoit
Hi Raj,
I think your analysis is spot on. Thank you!
How you're a VPP PPPoE expert __ do you have some suggestions on a fix?
/neale
On 17/10/2019 16:18, "vpp-dev@lists.fd.io on behalf of Raj"
wrote:
Hello all,
I could do some more analysis of this issue and I think I have
Hi Ruoyo,
Possiblly because your loaded crypto engine/backend does not support the
requested algorithms. Please provide :
show crypto engine
show ipsec backend
also whenever asking for assistance:
sh version
Thanks,
neale
From: on behalf of "Ying, Ruoyu"
Date: Thursday 17 October 2019
Hi Burt,
Two separate issues :
https://gerrit.fd.io/r/c/vpp/+/22597
https://gerrit.fd.io/r/c/vpp/+/22598
thanks for the report
/neale
From: "Dave Barach (dbarach)"
Date: Monday 7 October 2019 at 21:28
To: "Benoit Ganne (bganne)" , Burt Silverman
, vpp-dev , "Neale Ranns (nranns)"
Ok this time with vppsb-dev CC’d.
/neale
From: on behalf of "Neale Ranns via Lists.Fd.Io"
Reply to: "Neale Ranns (nranns)"
Date: Monday 7 October 2019 at 13:57
To: Liran
Cc: "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev] auto-remove fib entries
Hi Liran,
I
Hi Chuan,
Please remove the SPD config. For tunnels all packets that ingress/egress the
tunnel are decrypted/encrypted, so no policy is required. The presence of the
SPD on the ingress eth0 link could be why it’s not working.
Please provide packet traces when you are reporting packet loss
Hi Chuan,
IPSec and GRE is supported using the tunnel protection mechanism :
https://wiki.fd.io/view/VPP/IPSec
GRE over IPSec is only support when the SA is in tunnel mode. This means there
is a double encap of the IP header ; once by the SA (in tunnel mode) and once
by the tunnel itself.
From: on behalf of Aswin Surendran
Date: Thursday 26 September 2019 at 15:43
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] Packet hits wrong FIB look up
Hi,
I am facing an issue in FIB entry look-up in vpp-18.07 version.
A packet is being sent with source IP as 10.60.186.218 and
I Gyan,
Maybe this :
https://gerrit.fd.io/r/c/vpp/+/20558
/neale
From: on behalf of Gyan Ranjan
Date: Thursday 29 August 2019 at 10:00
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] fib_urpf_check_size crash during interface flap
Hello experts
I am seeing below backtrace when the interface
Hi Dave,
As with all IP routing, you need to configure the route with the nexthop on
that interface’s subnet.
So :
Ip route 173.2.0.0/24 via GigEthx/y/z
Rather than
Ip route 173.2.0.0/24 via GigEthx/y/z
/neale
From: shi dave
Date: Friday 23 August 2019 at 09:36
To: "Neale Ranns
Hi Dave,
That flow would suggest the packet was correctly sent out of GigEth0/a/0 with
the destination MAC of 172.16.3.1. was that not the case? Or was that your
desired flow not the actual?
/neale
De : shi dave
Date : vendredi 23 août 2019 à 09:11
À : "Neale Ranns (nranns)" ,
Hi Dave,
When routing to GigabitEthernet0/a/0 what destination MAC address should the
packet have?
/neale
De : shi dave
Date : vendredi 23 août 2019 à 05:01
À : "Neale Ranns (nranns)" , "vpp-dev@lists.fd.io"
Objet : 回复: [vpp-dev] Add ip route without next-hop-address
Hi Neale,
yes, it's
Hi Dave,
but from the trace, it send a ARP request to ask 173.2.0.1 directly
ip4-lookup -> ip4-glean -> GigabitEthernet0/a/0-output -> ip4-glean: ARP
requests sent
how could I avoid this ARP request, like ?
ip4-lookup -> ip4-rewrite (GigabitEthernet0/a/0) -> ipsec-output-ip4
VPP is ARPing
Hi Carlito,
You almost certainly want them in the same table.
As I said, if you do this:
ping 8.8.8.8 source wan1
then the ping packet will be constructed with a source address from wan1, but
it will still follow your routing config for transmission. This means that if
you have:
ip
Your VPP configs look fine. I can only guess at general network issues.
My first guess would be that the DHCP process did not complete, yet.
For my second guess, this:
vpp# ping 8.8.8.8 source wan1
means take the source address from wan1, but this:
ip route add 0.0.0.0/0 via
Hi Sam,
Please upgrade to at least 19.04. a lot of work went into IPSec for this
release.
/neale
De : au nom de "Caffeine Coder via Lists.Fd.Io"
Répondre à : "caffeine.co...@yahoo.com"
Date : mercredi 14 août 2019 à 00:16
À : Vpp-dev
Cc : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] ipsec
The FIB is a shared resource and each user of that shared resource needs to be
managed so they don’t interfere with one another. Different users are termed
‘sources’. FIB treats the API and CLI as separate ‘sources’ of routes. One
source cannot delete the state (routes nor paths) added by
Hi,
I don’t really understand what you’re asking, but if the question is, can I
delete routes via the CLI that I add via the API, the answer is no (nor
vice-versa).
/neale
De : au nom de "dengxun...@163.com"
Date : vendredi 9 août 2019 à 10:33
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev]
De : au nom de "amitmulay...@gmail.com"
Date : lundi 5 août 2019 à 07:21
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] ipsec traffic backend
Hello Guys
i wanted to ask how can i know if my ipsec is running with QAT (intel quick
assist) traffic backend (i am sure that i have a cpu that
Hi Dmitry,
It’s definitely a good idea to add changes that prevent things breaking The
question is how do you do it?
You’ll have noticed in your testing that the following sequence is disallowed:
DBGvpp# loop cre
DBGvpp# ip table add 2
DBGvpp# set int ip addr loop0 10.10.10.10/24
DBGvpp#
Hi,
Here’s the fix:
https://gerrit.fd.io/r/c/20914/
/neale
De : au nom de "Neale Ranns via Lists.Fd.Io"
Répondre à : "Neale Ranns (nranns)"
Date : lundi 29 juillet 2019 à 19:25
À : "fdr.koz...@yandex.com" , "vpp-dev@lists.fd.io"
Cc : "vpp-de
Hi Brayan,
Please try with:
https://gerrit.fd.io/r/c/20913/
/neale
De : au nom de brayan ortega
Date : dimanche 28 juillet 2019 à 12:44
À : "Neale Ranns (nranns)"
Cc : "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] abf problem with arp
Dear Neale,
I have tried to config vpp based on your
Hi,
You can reorder the route and ABF programming as a work around.
I’ll have a fix shortly.
/neale
De : au nom de "fdr.koz...@yandex.com"
Date : lundi 29 juillet 2019 à 08:24
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] SIGSEGV when adding route and abf with the same gateway
Hi vpp-dev
Hi Brayan,
First let’s discuss a bit your config and your objectives:
acl ID 0 permit { any }
set int ip addr GigabitEthernetb/0/0 30.30.30.1/24
set int ip addr GigabitEthernet3/0/0 20.20.20.1/24
abf policy add id 9001 acl 0 via 0.0.0.0 GigabitEthernetb/0/0
abf attach ip4 policy
Dear Brayan,
You should always add a next-hop to a path when IP routing.
Answers comments inline.
/neale
De : au nom de brayan ortega
Date : mercredi 24 juillet 2019 à 11:25
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] abf problem with arp
Dear VPP Folks,
I'm using vpp
Hi Matt,
Sounds like exactly what we need.
/neale
De : Matthew Smith
Date : mercredi 17 juillet 2019 à 14:52
À : "Neale Ranns (nranns)"
Cc : vpp-dev
Objet : Re: [vpp-dev] loopback admin status
Hi Neale,
Thanks for your reply.
I noticed that there is a function for IPv6 named
Hi Matt,
I would tend to agree with you. The interface’s IP addresses should not be
programmed in the FIB if the interface is down.
/neale
De : au nom de "Matthew Smith via Lists.Fd.Io"
Répondre à : "mgsm...@netgate.com"
Date : mardi 16 juillet 2019 à 21:42
À : vpp-dev
Cc :
Hi Raj,
There's no good way to do it, there's also no notification should the feature
be disabled or enabled.
Instead I'd suggest you 'listen' to the entity enabling/disabling the feature.
Or maybe you can configure your feature to run before this one, then it's not
important whether it's
Here’s a fix for BIER:
https://gerrit.fd.io/r/c/20349/
/neale
De : au nom de Florin Coras
Date : mercredi 26 juin 2019 à 00:51
À : "Dave Barach (dbarach)"
Cc : Paul Vinciguerra , "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] test-debug in the CI
This [1] seems to solve sctp issues with
Hi Chore,
Thank you for the patch, I have merged it.
/neale
De : au nom de emma sdi
Date : mercredi 26 juin 2019 à 07:06
À : Damjan Marion
Cc : vpp-dev
Objet : Re: [vpp-dev] NAT dose not exist in MAINTAINERS file
Hi Dear VPP
Would you please take a look at
Hi Alexander,
Then your applications need a message bus. VPP does not provide that
functionality for you. Notifications are only provided for data that VPP
learns, not what other client programme it with.
Regards,
Neale
De : au nom de "Alexander Chernavin via Lists.Fd.Io"
Répondre à :
Hi Anthony,
That wiki page you reference describes this setup. Perhaps if you ask specific
questions on the parts that are not clear I can help you.
/neale
De : au nom de Anthony Linz
Date : mardi 18 juin 2019 à 12:10
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] VPP MPLS VPN Configuration
Dear All,
Please note that:
https://gerrit.fd.io/r/c/12296/
has been merged into VPP and has changed the route add/del API.
/neale
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13321): https://lists.fd.io/g/vpp-dev/message/13321
Mute This
Hi Yi-Lin,
You need to select the correct back end:
https://wiki.fd.io/view/VPP/IPSec#IPSec_Implementations
/neale
De : au nom de Yilin Shieh
Date : mardi 18 juin 2019 à 14:01
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] #vpp How to enable intel QAT hw cryptpdev
Hi all,
I tried to enable
Hi Matt,
I have no explanation for why adj_index[VLIB_RX] is set to the same value as
the TX, AFAICT it’s been that way since time immemorial I think we should
change that logic to RX=TX; TX=lbi. I don’t see anything in the code that
relies on RX being set to the TX.
In that case the RX will
Pre 1908 :
static clib_error_t *
my_module_init (vlib_main_t * vm)
{
if ((error = vlib_call_init_function (vm, some_other_module_init)))
return (error);
} ;
post 1908 :
VLIB_INIT_FUNCTION (my_module_init) =
{
.runs_after = VLIB_INITS("some_other_module_init"),
};
/neale
o the new calls more straightforward. At least for me :)
Thanks,
-Matt
On Mon, May 20, 2019 at 11:59 AM Neale Ranns via
Lists.Fd.Io<http://Lists.Fd.Io>
mailto:cisco@lists.fd.io>> wrote:
Hi VPP-IPSec-ers,
I'd like to gauge comments on this article:
https://wiki.fd.io/view/VPP/IPSec
and t
Hi Uzzam,
I have already tried using the command 'sudo vppctl set interface l2 bridge
loopX 1 bvi' but the vpp crashes after few seconds.
Can we see a back trace, please?
While on the other hand when I use the command 'sudo vppctl set interface l2
bridge loopX 1', loop1 does not receive
Hi Uzzam,
All these:
sudo vppctl set interface l2 bridge loopX 1
Should be:
sudo vppctl set interface l2 bridge loopX 1 bvi
/neale
De : au nom de Uzzam Javed
Répondre à : Uzzam Javed
Date : jeudi 23 mai 2019 à 14:50
À : "vpp-dev@lists.fd.io"
Cc : "b...@xflowresearch.com"
Objet :
HI Murthy,
There are two plugins, that I know of, that use the ACL as a service; ACL based
forwarding (ABF) and group based policy (GBP).
Both of these plugins expect that the user first configures the ACL using the
ACL plugin, then passes the index of the ACL during ABF/GBP programming. This
Hi Ole,
Thanks for taking the time to examine the proposal. Lots of comments inline
> Answering as a non VPP-IPsec'er. More like an anti-IPsec'er if anything.
;-)
> Eecutive summary: Not a fan.
> This tastes too much of the dreams of the IPsec'ers of the past. Where
IPsec
Hi VPP-IPSec-ers,
I'd like to gauge comments on this article:
https://wiki.fd.io/view/VPP/IPSec
and the proposal for the IPSec tunnel re-model.
The associated patch is:
https://gerrit.fd.io/r/#/c/18956/
thanks,
Neale
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this
Hi Christian,
Type 'recheck' as a review comment, with Jenkins as a review, he'll kick of the
job again.
/neale
-Message d'origine-
De : au nom de Christian Hopps
Date : samedi 18 mai 2019 à 15:54
À : "vpp-dev@lists.fd.io"
Cc : "cho...@chopps.org"
Objet : [vpp-dev] Jenkins
Hi,
VRFs are an ingress function, encryption is egress, so I’m not sure I
understand your request. Perhaps you could give us more details on your use
case.
Regards,
neale
De : au nom de "omid via Lists.Fd.Io"
Répondre à : "zeinalpouro...@yahoo.com"
Date : samedi 18 mai 2019 à 09:40
À :
Dear cmh2014011443,
You can send the packets that you want to drop to the ‘ip4-drop’ or ‘ip6-drop’
nodd.
regards,
Neale
De : au nom de "cmh2014011...@gmail.com"
Date : jeudi 16 mai 2019 à 10:51
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] how to drop packet in the vpp's plugin?
Recently,
Hi Andreas,
From your description, I don't think you are doing anything wrong. You are
probably breaking new ground on the number of interfaces and routes through
those interfaces.
There is a per-interface adjacency DB, this is what is being allocated in the
backtrace below. We size this for
Hi Charles,
Does this fix it :
https://gerrit.fd.io/r/#/c/18944/
/neale
De : au nom de "charlesb...@gmail.com"
Date : mardi 16 avril 2019 à 22:14
À : "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] pcap trace status in 19.04 reports local0 instead of
specified interface
Thank you for the
Hi Satish,
There is no such unit-test harness to test individual nodes in isolation.
Instead what we do is configure VPP ‘end-to-end’ using API calls and then
inject packets on the appropriate interfaces and examine their fate, by for
example, capturing them on the interface they were
Hi Jon,
This is where ip6_sw_interface_add_del() (and other registered callbacks) are
invoked from:
call_sw_interface_add_del_callbacks
in the branch you’re using, check the signature of the function is exactly what
is expected.
/neale
De : Jonathan Richardson
Date : mardi 26 mars 2019 à
Hi Raj,
ABF, which is a feature that runs in the L3 path, has not (to my knowledge
anyway) been tested with MACIP ACLs – this ACL type is usually applied to L2
traffic. Try an L3 ACL instead (i.e. use acl_add_replace to create the ACL, not
macip_acl_rule).
Regards,
neale
De : au nom de
Hi Raj,
If you're looking for VPP to send your agent/app a notification across the
binary API when an ARP and/or ND entry is created then your app needs to call;
want_ip4_arp_events and/or want_ip6_nd_events respectively.
/neale
-Message d'origine-
De : au nom de Raj
Date :
And the GBP plugin.
/neale
-Message d'origine-
De : au nom de Andrew Yourtchenko
Date : jeudi 14 mars 2019 à 11:09
À : chetan bhasin
Cc : vpp-dev
Objet : Re: [vpp-dev] I want to disable acl plugin but VPP is not coming up
hi Chetan,
ABF plugin uses ACL plugin, so you
Hi Lolita,
I have reproduced this issue and this is the resulting fix:
https://gerrit.fd.io/r/#/c/18138/
could you please also verify it fixes all your test cases.
Thanks,
Neale
De : Lollita Liu
Date : jeudi 7 mars 2019 à 03:52
À : "Neale Ranns (nranns)" , "vpp-dev@lists.fd.io"
Objet :
Hi lolita,
What GTPU code are you running. Your test case does not work for me on master:
DBGvpp# create gtpu tunnel src 1.1.1.1 dst 1.1.1.4 teid-in 3 teid-out 4
create gtpu tunnel: parse error: 'teid-in 3 teid-out 4'
to answer your questions:
1) You should be able to delete the
I'll bite __ why would you want to do that?
/neale
-Message d'origine-
De : au nom de Prashant Upadhyaya
Date : lundi 4 mars 2019 à 16:06
À : "Dave Barach (dbarach)"
Cc : "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] Regarding node on a feature arc
Thanks Dave, this is cool !
Hi,
In the spirit of this work I’d like to propose a change to the route add/del
APIs to make use of the fib_path structure. The fib_path structure, which
describes how to deal which the matched packets, is consistent across each of
the route types; IP, MPLS, BIER and ABF.
By using a fib_path
+1.
/neale
De : au nom de "Dave Barach via Lists.Fd.Io"
Répondre à : "Dave Barach (dbarach)"
Date : mercredi 27 février 2019 à 13:38
À : "vpp-dev@lists.fd.io"
Cc : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] New vpp project committer nomination: Paul Vinciguerra
In view of significant code
Hi Rupseh,
Interfaces that are not ip6 enabled show these features enabled:
ip6-multicast:
ip6-not-enabled
ip6-unicast:
ip6-not-enabled
it’s the ip6-not-enabled node/feature that is enabled on the interface as an
input feature that drops the packets.
/neale
De : au nom de Rupesh
Hi Rupesh,
An IPv6 packet arriving on an interface that is not IPv6 enabled should be
dropped in ip6-input.
Can you please show me:
sh int feat loop0
sh ip6 interface loop0
local0 is a special case. Think of it as a means for VPP to consume the ID 0 so
that we can be sure that no other
Hi Sun,
It is my understanding that it is not possible to configure both AH and ESP for
a given ‘flow’. It is something we identified only recently and we are working
towards a fix.
Regards,
Neale
De : au nom de "saint_sun 孙 via Lists.Fd.Io"
Répondre à : "saint_...@aliyun.com"
Date :
Hi Fedor,
This is one of those cases where you cannot/should not remove an object on
which others depend.
In principle with VPP you should unconfigure in the reverse order to configure.
Regards,
neale
-Message d'origine-
De : au nom de Fedor Kazmin
Date : mercredi 13 février 2019 à
Dear All,
We propose to deprecate the STN plugin in favour of the ipX_redirect punt
feature.
For all those with objections please raise them AYEC.
Thanks,
Neale
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12069):
Hi All,
As you know a while back we introduced the use of typesdef and enums for use in
VPP’s .api files.
Example types are mac_address_t, address_t and prefix_t.
This patch:
https://gerrit.fd.io/r/#/c/14138/
updates all the APIs in ip.api to use these new types and new enums where
??
Great job is VPP.
El 29 de enero de 2019 3:54:07 AM GMT-05:00, "Neale Ranns via Lists.Fd.Io"
escribió:
Hi,
You just need to give the interface an IPv4 and IPv6 address.
DBGvpp# loop cre
DBGvpp# ip table 1
DBGvpp# set int ip table loop0 1
DBGvpp# set int state loop0 up
DBGvpp# se
Hi,
You just need to give the interface an IPv4 and IPv6 address.
DBGvpp# loop cre
DBGvpp# ip table 1
DBGvpp# set int ip table loop0 1
DBGvpp# set int state loop0 up
DBGvpp# set int ip address loop0 10.10.10.10/24
DBGvpp# set int ip address loop0 2001::10/64
The creation of the IP table 1 is
Hi Michal,
Thanks for the fixes. I’ll merge them when they verify.
/Neale
De : au nom de "Michal Cmarada via Lists.Fd.Io"
Répondre à : "Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco)"
Date : vendredi 18 janvier 2019 à 13:35
À : "vpp-dev@lists.fd.io" , "hc2...@lists.fd.io"
Hi Satish,
Statistics handling did change in !8.10, see:
https://docs.fd.io/vpp/18.10/md_src_vpp_stats_stats.html
there is no longer an exporter thread, instead there is a shared memory segment
from which your client can read the stats at the period of your choosing.
/neale
De : au nom
PLS packets
Hi Neale,
Route for destination IP of GRE tunnel was also added as an MPLS route.
And MPLS in VPP doesn't work for L2 forwarding, hence GRE tunnel was dropping
packets.
Thanks.
Best Regards,
Omer
On 2019-01-08 17:12, Neale Ranns via Lists.Fd.Io wrote:
Hi Omer,
Your config loo
Hi Jon.
In all cases it refers to the table related to the path (not the prefix). A
path determines where to send the packet and is described by all keywords after
the ‘via’ keyword.
The two use cases you mention would be:
Ip route add table 10.1.1.0/24 via 20.20.20.20 next-hop-table
Hi Omer,
Your config looks OK. I would start debugging with a packet trace.
/neale
De : au nom de Omer Majeed
Date : lundi 7 janvier 2019 à 20:47
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] :: GRE tunnel dropping MPLS packets
Hi,
I'm running VPP on Centos 7 machine (say machine A), and
Hi Chore,
By default interface stats are collected for rx, tx, drops etc. However, to
collect stats related to whether the RX/TX packet is unicast, multicast or
broadcast requires extra checks in the data-plane that do not come for free.
So, to able these extra stats, and hence incur the
uestion is
this: What unit test can we write that expose the proper and improper
behaviors? Something in test_vapi.py maybe?
On Thu, Dec 20, 2018 at 7:33 AM Neale Ranns via Lists.Fd.Io<http://Lists.Fd.Io>
mailto:cisco@lists.fd.io>> wrote:
/root/zhiyong/vpp/src/vnet/ethernet/eth
at expose the proper and improper
behaviors? Something in test_vapi.py maybe?
On Thu, Dec 20, 2018 at 7:33 AM Neale Ranns via Lists.Fd.Io<http://Lists.Fd.Io>
mailto:cisco@lists.fd.io>> wrote:
/root/zhiyong/vpp/src/vnet/ethernet/ethernet_types_api.h:25:13: note: expected
‘con
neale
De : au nom de "Neale Ranns via Lists.Fd.Io"
Répondre à : "Neale Ranns (nranns)"
Date : jeudi 20 décembre 2018 à 13:33
À : Ole Troan , Zhiyong Yang
Cc : "vpp-dev@lists.fd.io"
Objet : Re: [vpp-dev] build errors on CenOS 7.5
/root/zhiyong/vpp/src/vnet/e
/root/zhiyong/vpp/src/vnet/ethernet/ethernet_types_api.h:25:13: note: expected
‘const u8 * {aka const unsigned char *}’ but argument is of type
‘vl_api_mac_address_t {aka struct _vl_api_mac_address}’
extern void mac_address_decode (const u8 * in, mac_address_t * out);
the argument is not of
De : au nom de raju
Date : vendredi 14 décembre 2018 à 14:58
À : vpp-dev
Objet : [vpp-dev] Feature arc and ordering graph nodes in an existing feature
arc.
Hi
I am trying to add a feature (say 'my_node') to ip4_unicast arc.
Goal is just like ip4_gtpu_bypass to by pass the IP stack and
Looking at the that log, I don’t think the failure is related to the issue
discussed here, but it does warrant further investigation. I don’t see it
happen on my machine, but if some-one can get me a log.txt from the test case,
I’ll take a look.
/neale
De : au nom de
Hi Xuekun,
The transaction ID used by VPP is from a series of random numbers, however,
each VPP seeds the RNG the same, so the sequence will be the same. Please
update:
static clib_error_t *
dhcp_client_init (vlib_main_t * vm)
{
dhcp_client_main_t *dcm = _client_main;
dcm->vlib_main = vm;
Hi Rubina,
The pings should work continuously. I’ll need more information to make an
analysis:
https://wiki.fd.io/view/VPP/BugReports
thanks,
neale
De : au nom de Rubina Bianchi
Date : dimanche 9 décembre 2018 à 10:45
À : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] Problem with adding
Hi Brian,
If you’re adding lots of routes, you’ll also need to bump the heap size for the
IP FIBs as well as the main heap:
https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/users/configuring/startup.html#ip
to run in gdb:
sudo service vpp stop (or your OS equivalent)
make build
] question about multicast mpls
Hi Neale，
Is there any cli configuration examples about multicast mpls ?
Thanks,
Xue
From: Neale Ranns via Lists.Fd.Io<mailto:nranns=cisco@lists.fd.io>
Date: 2018-11-28 20:59
To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io>
Hi Ole,
I think this should fix the GRE tests:
https://gerrit.fd.io/r/#/c/16272/
/Neale
-Message d'origine-
De : au nom de Ole Troan
Date : mercredi 28 novembre 2018 à 19:55
À : vpp-dev
Objet : [vpp-dev] Verify issues (GRE)
Guys,
The verify job have been unstable
Hi Xue,
To my knowledge it has not been tried nor tested. GRE interfaces today do not
support a multicast destination address. However, other tunnel types (like
VXLAN) do so adding support shouldn’t be too hard. After that the mfib support
egress out of any interface type.
I also have a draft
Hi Xue,
MPLS multicast has been supported for a while. Please see the unit tests for
examples: test/test_mpls.py test_mcast_*()
Regards,
Neale
De : au nom de xyxue
Date : mercredi 28 novembre 2018 à 13:04
À : vpp-dev
Objet : [vpp-dev] question about multicast mpls
Hi guys,
I found
Hi Chetan,
The null-node should not be encountered under normal operation. The null-node
always has an index/value of 0, therefore if the previous node has not been
properly configured, or the arc taken from that node was wrong, then the packet
can likely end up at the null-node.
To debug
Hi,
We do not support FRR, nor is there currently a plan to.
However, if your label/tunnel/route has only one path, you can achieve a
similar result to FRR by installing the primary path with a better (lower)
preference to the backup path. VPP will then cutover when the primary path goes
Hi Ray,
By way of explanation.. without the interface the route is recursive, i.e.
20.20.20.20/24 is sent via 1.1.1.2. So the forwarding can be thought of as
happening in two stages, firstly the lookup for the packet’s destination that
matches 20.20.20.20/24 then the ‘lookup’ on the result of
+1
-Message d'origine-
De : au nom de "Dave Barach via Lists.Fd.Io"
Répondre à : "Dave Barach (dbarach)"
Date : jeudi 8 novembre 2018 à 13:13
À : "vpp-dev@lists.fd.io"
Cc : "vpp-dev@lists.fd.io"
Objet : [vpp-dev] New Committer Nomination: Andrew Yourtchenko
In view of
Hi Eyal, John,
I missed the fact that the tunnel classification is based only on the senders
IP. Now it makes sense.
Thanks,
Neale
-Message d'origine-
De : au nom de "John Lo (loj) via Lists.Fd.Io"
Répondre à : "John Lo (loj)"
Date : lundi 5 novembre 2018 à 16:17
À : Xuekun ,
Hi Saint,
With this change an attacker could send a packet with both the source and
destination both set to one of VPP’s own addresses. If you include in this new
sub-condition to only accept locally generated packets, then we should be good
(b->flags & VNET_BUFFER_F_LOCALLY_ORIGINATED).
It’s a known limitation. Contributions to fix it would be welcome.
/neale
De : au nom de "saint_sun 孙 via Lists.Fd.Io"
Répondre à : "saint_...@aliyun.com"
Date : jeudi 25 octobre 2018 à 09:40
À : vpp-dev
Cc : "vpp-dev@lists.fd.io"
Objet : [vpp-dev]ping local address
Hello all:
An basic
101 - 200 of 241 matches
Mail list logo
