Re: [vpp-dev] VPP MPLS VPN Configuration #vpp #mpls #vpn

2019-06-22 Thread Anthony Linz
Dear Neale,
Thank you very much for your response.
The way I asked my question might have been a bit confusing.
Although I have read the wiki, I could not actually get the topology.
By topology I mean what configurations may be applied on what device.
Shortly, I need to know how to configure each and every one of my VPP devices 
according to the topology I have demonstrated.
Thank you very much again
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13349): https://lists.fd.io/g/vpp-dev/message/13349
Mute This Topic: https://lists.fd.io/mt/32105211/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #mpls: https://lists.fd.io/mk?hashtag=mpls=1480452
Mute #vpn: https://lists.fd.io/mk?hashtag=vpn=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] VPP MPLS VPN Configuration #vpp #mpls #vpn

2019-06-18 Thread Anthony Linz
Hello
I am trying to implement the following network topology:

I have trouble finding out a step by step configuration for my VPP devices to 
communicate over MPLS VPN.
I have read the Wiki:
https://wiki.fd.io/view/VPP/MPLS_FIB
but still did not get what to do.
I was wondering if someone could guide me precisely through how to config VPP 
appropriately according to above-mentioned network topology.
Thanks in advance for your solution
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13315): https://lists.fd.io/g/vpp-dev/message/13315
Mute This Topic: https://lists.fd.io/mt/32105211/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #mpls: https://lists.fd.io/mk?hashtag=mpls=1480452
Mute #vpn: https://lists.fd.io/mk?hashtag=vpn=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] Bond interface won't respond ping #vnet #vpp

2019-02-24 Thread Anthony Linz
Dear Steven
Thank you very much.
As you said Bond interfaces should have been bundled in order to act as L3.
I have now ping and everything.
Thanks again.
Wish you all the best
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12334): https://lists.fd.io/g/vpp-dev/message/12334
Mute This Topic: https://lists.fd.io/mt/29916205/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #vnet: https://lists.fd.io/mk?hashtag=vnet=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] Bond interface won't respond ping #vnet #vpp

2019-02-22 Thread Anthony Linz
Dear Steven
Thank you very much for your quick and nice response.
I suppose the beginning of my question might misguide you.
Let me clear my test scenario:

I have a Virtual Machine (VM1) which runs VPP and has an interface called 
GigabitEthernet0/8/0. I have another Virtual Machine (VM2) that it's interface 
(eth1) is in the same Kernel bridge as GigabitEthernet0/8/0 (and does not run 
VPP). So that I am able to ping GigabitEthernet0/8/0 easily (from VM2).

After creating a Bond interface (in VM1) with LACP mode (and also setting the 
state up and giving it IP address) and binding GigabitEthernet0/8/0 to the Bond 
interface I have neither ping of  GigabitEthernet0/8/0 nor Bond interface (from 
VM2).

I traced packets and It seems Bond interface is able to receive ARP packets 
(and learn it), however is not able to respond back to it. So I went ahead and 
set arps (for VM2) so that it started to send ICMP packets and again Bond 
interface (in VM1) was able to receive it but could not respond to it.

So my question really is:

1) Why don't Bond interface is not able to respond to either ARP or ICMP 
packets?
2) Is my config incomplete? (or maybe wrong)
3) Is it logical to ping a Bond Interface?

Thank you again for your response,
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12331): https://lists.fd.io/g/vpp-dev/message/12331
Mute This Topic: https://lists.fd.io/mt/29916205/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #vnet: https://lists.fd.io/mk?hashtag=vnet=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] Bond interface won't respond ping #vnet #vpp

2019-02-19 Thread Anthony Linz
Dear all
I was working on some LACP testing in VPP 19.01.
I configured VPP like this:

create bond mode lacp
set interface state BondEthernet0 up
bond add BondEthernet0 GigabitEthernet0/x/0

The 'GigabitEthernet0/x/0' has some IP address like '10.10.10.80/24' and before 
adding it as a slave to Bond interface, pinging the interface from another 
Virtual Machine with IP address '10.10.10.81/24' was all OK (Both interfaces 
are in the same switch).
After binding GigabitEthernet to Bond, slave interface stopped responding . The 
trace looks like this:

00:02:07:006939: dpdk-input
  GigabitEthernet0/8/0 rx queue 0
  buffer 0x494a: current data 0, length 98, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x0
                 ext-hdr-valid 
                 l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
  PKT MBUF: port 0, nb_segs 1, pkt_len 98
    buf_len 2176, data_len 98, ol_flags 0x0, data_off 128, phys_addr 0x22b25300
    packet_type 0x0 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
    rss 0x0 fdir.hi 0x0 fdir.lo 0x0
  IP4: 52:54:00:16:b8:43 -> 52:54:00:d8:95:e0
  ICMP: 10.10.10.81 -> 10.10.10.80
    tos 0x00, ttl 64, length 84, checksum 0x168f
    fragment id 0xfb65, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xb04d
00:02:07:010073: bond-input
  src 52:54:00:16:b8:43, dst 52:54:00:d8:95:e0, GigabitEthernet0/8/0 -> 
BondEthernet0
00:02:07:010103: ethernet-input
  IP4: 52:54:00:16:b8:43 -> 52:54:00:d8:95:e0
00:02:07:010129: ip4-input
  ICMP: 10.10.10.81 -> 10.10.10.80
    tos 0x00, ttl 64, length 84, checksum 0x168f
    fragment id 0xfb65, flags DONT_FRAGMENT
  ICMP echo_request checksum 0xb04d
00:02:07:010139: ip4-not-enabled
    ICMP: 10.10.10.81 -> 10.10.10.80
      tos 0x00, ttl 64, length 84, checksum 0x168f
      fragment id 0xfb65, flags DONT_FRAGMENT
    ICMP echo_request checksum 0xb04d
00:02:07:010154: error-drop
  ethernet-input: no error

I thought Bond interface needs an IP so I tried to give it an IP as 
'60.60.60.60/24' and so change Virtual Machine's IP as '60.60.60.81/24' and 
tried to ping Bond interface this time.
I wasn't able to get ICMP packets so I tried to manually set ARPs in both VPP 
and VM.
Result of pinging trace looks pretty like this:

00:27:21:247255: dpdk-input
  GigabitEthernet0/8/0 rx queue 0
  buffer 0x115a5: current data 0, length 98, free-list 0, clone-count 0, 
totlen-nifb 0, trace 0x1
                  ext-hdr-valid 
                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
  PKT MBUF: port 0, nb_segs 1, pkt_len 98
    buf_len 2176, data_len 98, ol_flags 0x0, data_off 128, phys_addr 0x22e569c0
    packet_type 0x0 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
    rss 0x0 fdir.hi 0x0 fdir.lo 0x0
  IP4: 52:54:00:16:b8:43 -> 52:54:00:d8:95:e0
  ICMP: 60.60.60.81 -> 60.60.60.60
    tos 0x00, ttl 64, length 84, checksum 0xeee1
    fragment id 0x5ac2, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x7fb4
00:27:21:247283: bond-input
  src 52:54:00:16:b8:43, dst 52:54:00:d8:95:e0, GigabitEthernet0/8/0 -> 
BondEthernet0
00:27:21:247286: ethernet-input
  IP4: 52:54:00:16:b8:43 -> 52:54:00:d8:95:e0
00:27:21:247287: ip4-input
  ICMP: 60.60.60.81 -> 60.60.60.60
    tos 0x00, ttl 64, length 84, checksum 0xeee1
    fragment id 0x5ac2, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x7fb4
00:27:21:247288: ip4-lookup
  fib 0 dpo-idx 4 flow hash: 0x
  ICMP: 60.60.60.81 -> 60.60.60.60
    tos 0x00, ttl 64, length 84, checksum 0xeee1
    fragment id 0x5ac2, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x7fb4
00:27:21:247290: ip4-local
    ICMP: 60.60.60.81 -> 60.60.60.60
      tos 0x00, ttl 64, length 84, checksum 0xeee1
      fragment id 0x5ac2, flags DONT_FRAGMENT
    ICMP echo_request checksum 0x7fb4
00:27:21:247290: ip4-icmp-input
  ICMP: 60.60.60.81 -> 60.60.60.60
    tos 0x00, ttl 64, length 84, checksum 0xeee1
    fragment id 0x5ac2, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x7fb4
00:27:21:247292: ip4-icmp-echo-request
  ICMP: 60.60.60.81 -> 60.60.60.60
    tos 0x00, ttl 64, length 84, checksum 0xeee1
    fragment id 0x5ac2, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x7fb4
00:27:21:247293: ip4-load-balance
  fib 0 dpo-idx 24 flow hash: 0x
  ICMP: 60.60.60.60 -> 60.60.60.81
    tos 0x00, ttl 64, length 84, checksum 0x71aa
    fragment id 0xd7f9, flags DONT_FRAGMENT
  ICMP echo_reply checksum 0x87b4
00:27:21:247293: ip4-rewrite
  tx_sw_if_index 3 dpo-idx 7 : ipv4 via 60.60.60.81 BondEthernet0: mtu:9000 
52540016b843525400d895e00800 flow hash: 0x
  : 52540016b843525400d895e008004554d7f94000400171aa3c3c3c3c3c3c
  0020: 3c5187b40fc7000bf6bf6b5c3b8a0c001011
00:27:21:247294: BondEthernet0-output
  BondEthernet0
  IP4: 52:54:00:d8:95:e0 -> 52:54:00:16:b8:43
  ICMP: 60.60.60.60 -> 60.60.60.81
    tos 0x00, ttl 64, length 84, checksum 0x71aa
    fragment id 0xd7f9, flags DONT_FRAGMENT
  ICMP echo_reply checksum 0x87b4

It seems that bond is able to receive and reply ICMP packet 

Re: [vpp-dev] VPP 19.01 C API gets segmentation fault #binapi #vpp #vppcapi

2019-01-08 Thread Anthony Linz
Dear Dave,
Thank you very much for your great and exact response.
The program now works like a dream.
Best wishes,
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11875): https://lists.fd.io/g/vpp-dev/message/11875
Mute This Topic: https://lists.fd.io/mt/28972181/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #binapi: https://lists.fd.io/mk?hashtag=binapi=1480452
Mute #vppcapi: https://lists.fd.io/mk?hashtag=vppcapi=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Re: [vpp-dev] VPP 19.01 C API gets segmentation fault #binapi #vpp #vppcapi

2019-01-08 Thread Anthony Linz
Dear Dave,
Thanks for you reply.
I could not find " clib_memory_init()" in vpp.
Did you mean "vlibmemory_init()"?
If yes where and how in my code I should use it?
Thanks
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11869): https://lists.fd.io/g/vpp-dev/message/11869
Mute This Topic: https://lists.fd.io/mt/28972181/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #binapi: https://lists.fd.io/mk?hashtag=binapi=1480452
Mute #vppcapi: https://lists.fd.io/mk?hashtag=vppcapi=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


[vpp-dev] VPP 19.01 C API gets segmentation fault #binapi #vpp #vppcapi

2019-01-08 Thread Anthony Linz
Hi
Recently I tried to learn VPP's C API and I found a sample C program in 
https://www.marosmars.com/blog/managing-vpp-c-edition blog.
I have compiled the program like this:
gcc myprog.c -o myprog -lvppinfra -lvlibmemoryclient -lsvm
and it has been compiled successfully.
The problem is that when I try to run the program I will get segmentation fault 
like this:

program received signal SIGSEGV, Segmentation fault.
mspace_malloc (msp=0x0, bytes=bytes@entry=20) at 
/root/vpp/src/vppinfra/dlmalloc.c:4338
warning: Source file is more recent than executable.
4338  if (!PREACTION(ms)) {

And the back trace looks pretty like this:

#0  mspace_malloc (msp=0x0, bytes=bytes@entry=20) at 
/root/vpp/src/vppinfra/dlmalloc.c:4338
#1  0x77bb9308 in mspace_get_aligned (msp=0x0, n_user_data_bytes=20, 
n_user_data_bytes@entry=16, align=align@entry=8, 
    align_offset=align_offset@entry=8) at /root/vpp/src/vppinfra/dlmalloc.c:4177
#2  0x77bae5f8 in clib_mem_alloc_aligned_at_offset 
(os_out_of_memory_on_failure=1, align_offset=8, align=8, size=16)
    at /root/vpp/src/vppinfra/mem.h:118
#3  vec_resize_allocate_memory (v=v@entry=0x0, 
length_increment=length_increment@entry=8, data_bytes=16, 
header_bytes=, header_bytes@entry=0, 
    data_align=data_align@entry=8) at /root/vpp/src/vppinfra/vec.c:59
#4  0x77b549a6 in _vec_resize_inline (data_align=, 
header_bytes=, data_bytes=, 
    length_increment=, v=) at 
/root/vpp/src/vppinfra/vec.h:147
#5  va_format (s=0x0, fmt=, va=va@entry=0x7fffe228) at 
/root/vpp/src/vppinfra/format.c:403
#6  0x77b548f7 in format (s=s@entry=0x0, fmt=fmt@entry=0x77929a4c 
"/dev/shm%s%c") at /root/vpp/src/vppinfra/format.c:423
#7  0x7791e524 in vl_map_shmem (region_name=0xc7a2 "/vpe-api", 
is_vlib=is_vlib@entry=0) at /root/vpp/src/vlibmemory/memory_shared.c:544
#8  0x7791f8cb in vl_client_api_map (region_name=) at 
/root/vpp/src/vlibmemory/memory_client.c:389
#9  0x7791f90c in connect_to_vlib_internal (svm_name=, 
client_name=0xcae9 "test", rx_queue_size=32, want_pthread=1, 
    do_map=) at /root/vpp/src/vlibmemory/memory_client.c:416
#10 0x74c6 in connect_to_vpe ()
#11 0x9261 in main () 

My Operating System is Ubuntu 18.04.01 and I have tested this on Ubuntu 16.04 
as well with the same result.
I was wondering if anyone could help me with the problem.
Thanks in advance for your help,
Best regards
--
Anthony
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11863): https://lists.fd.io/g/vpp-dev/message/11863
Mute This Topic: https://lists.fd.io/mt/28972181/21656
Mute #binapi: https://lists.fd.io/mk?hashtag=binapi=1480452
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp=1480452
Mute #vppcapi: https://lists.fd.io/mk?hashtag=vppcapi=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-