Re: [vpp-dev] show interface address with multiple tables

; Date: Tuesday, 17 January 2017 at 15:13 To: Dave Wallace <dwallac...@gmail.com> Cc: "Neale Ranns (nranns)" <nra...@cisco.com>, Choonho Son <choonho@gmail.com>, "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] show interface add

Re: [vpp-dev] show interface address with multiple tables

Hi Choonho, An interface can only reside in (a.k.a be bound to) a single table. So each time you do; Set int ip table loop0 X You are changing the table it is bound to, not adding tables. So the output you see at the end of the sequence is correct, the loopback has two addresses and is

Re: [vpp-dev] Get IPv6 neighbors MACs

15:10 To: "Neale Ranns (nranns)" <nra...@cisco.com> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Get IPv6 neighbors MACs Hi Neale, Your understanding is correct. However I don't see any collision here. There is following route in VRF1: vpp# ip route table 1 add b

Re: [vpp-dev] Get IPv6 neighbors MACs

Hi Dmitry, IIUC you have two devices with identical IPv6 addresses, which we’ll call P and Q, connected on two different interfaces. These interfaces are in different VRFs so the addresses do not collide. Now if we succeed in importing the discovered neighbours from VRF 0 to VRF 1, these

Re: [vpp-dev] [csit-dev] vpp make test for verify - are we there yet ? [awoken]

g .py/.pyc files? Maybe somehow the .py file's timestamp is in the past (from .pyc POV)? Thanks, Klement Quoting Neale Ranns (nranns) (2017-01-05 13:39:44) >Hi Dave, > > > >After a little more experimentation I think this error

Re: [vpp-dev] [csit-dev] vpp make test for verify - are we there yet ? [awoken]

ANTHEON TECHNOLOGIES at Cisco)" <ksek...@cisco.com>, "Maciek Konstantynowicz (mkonstan)" <mkons...@cisco.com>, "Neale Ranns (nranns)" <nra...@cisco.com> Cc: "csit-...@lists.fd.io" <csit-...@lists.fd.io>, "vpp-dev@lists.fd.io" &

Re: [vpp-dev] [csit-dev] vpp make test for verify - are we there yet ? [awoken]

Hi Klement, Maciek, What environment are you running the tests in? I get different results. Running in the default vagrant env provided in 17.0. Everything passes apart from: == Bidirectional Forwarding Detection (BFD)

Re: [vpp-dev] admin_up_down flag for loopback interface

Hi Matej, Then you should remove the address from the interface – that in turn will remove the route from the FIB – and is in the only way that that route can be removed from the FIB. Regards, neale On 02/01/2017, 15:29, "Matej Klotton -X (mklotton - PANTHEON TECHNOLOGIES at Cisco)"

Re: [vpp-dev] strange phenomenon of interface

Hi Ewan, The value 0 represents the always present local0 interface. So this: mp->next_hop_sw_if_index = ntohl (0); should be: mp->next_hop_sw_if_index = ntohl (~0); in order to specify that no interface is desried. I would also suggest; sh ip fib To give you more information about the

Re: [vpp-dev] admin_up_down flag for loopback interface

Hi Matej, Good questions, some answers, or opinions, inline. ➢ I’m trying put Loopback interface to DOWN state with set admin_up_down=0 in sw_interface_set_flags api. The interface has IPv4 address configured with /32 prefix. ➢ Should the interface’s address be in FIB when the admin_up_down

Re: [vpp-dev] [SUSPICIOUS] vppctl set interface ip address [del] problem!!

Hi Sajjad, This CLI requires the ‘del' to be placed in at the right place: set interface ip address del GigabitEthernet2/4/0

Re: [vpp-dev] Regarding IGMP implementation in VPP

Hi Deepak, I’ve given some thought to IGMP in VPP recently, but I have not started with coding. I would be interested in understanding you approach. If you could explain it in a little more detail, perhaps your new APIs and data-structures, that would be ideal. But I guess the first question

Re: [vpp-dev] Vnet enum values in the python API

Hi Ole, On 06/12/2016, 10:25, "otr...@employees.org" wrote: >Neale, > >> What’s the best (i.e. least error prone) way to export enum values to the >> python API. >> >> For example; >> From l2/l2_vtr.h: >> >> /* VTR config options for API and CLI support */ >> typedef

[vpp-dev] Debian package build failure from ubuntu 14.04 vagrant

Hi, On my freshly provisioned vagrant VM: vagrant@localhost:/vpp$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty I get the following build error when doing ‘make pkg-deb’ make[3]: Leaving

Re: [vpp-dev] about vlan tag

Hi Yu, create and configure the interface: DBGvpp# create sub-interface af_packet0 100 DBGvpp# set int state af_packet0.100 up DBGvpp# set int ip addr af_packet0.100 172.16.3.1/24 DBGvpp# set ip arp af_packet0.100 172.16.3.2 00:00:11:aa:bb:cc add a route through the sub-interface

<    1   2   3