Re: [vpp-dev] NAT Fragment Reassembly

[Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io]

Hi Jon,

NAT plugin does virtual fragment reassembly – it enables to translate 
non-initial fragments without L4 header otherwise NAT is unable to gather port 
information from the non-initial fragment, packet is still broken into several 
fragments after NAT translation.

Matus


From: vpp-dev@lists.fd.io  On Behalf Of Jon Loeliger
Sent: Tuesday, August 14, 2018 11:53 PM
To: vpp-dev 
Subject: [vpp-dev] NAT Fragment Reassembly

VPPeople,

A few months ago, the vppctl command 'set interface reassembly' was
added along with its API call, ip_reassembly_enable_disable (commit
4c53313cd7e9b866412ad3e04b2d91ac098c1398).

What is the relationship of this fragment reassembly and this
enable/disable flag WRT to the NAT's fragment reassembly?

Specifically, should a NAT fragment reassembly be controlled by this flag?
Empirically, the answer is 'yes'.

So it appears that one should interpret this enable/disable flag more like:

When you use `set interface reassembly  off`, the  fragments are 
forwarded
without any sort of reassembly.  The fragments flow through unmolested.  
The NAT
fragmentation limits are not respected as they aren't even involved.

When you use `set interface reassembly  on`, the fragments are 
reassembled
before being forwarded.  So the interface will process, and possibly limit, 
fragment
reassembly, even for NAT rewritten packets.

Does that sound right?

And should the reassembly be enabled/disabled on the ingress interface?
Or are there different scenarios where one would want them reassembled on
the egress interface?

Thanks,
jdl



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Where could I find the example of vcl.conf

[wylandrea]

Thanks, Florin!  I tried, but unfortunately got segment fault like
below(pull from master today):

The segfault caused by the mq=0x204005440, the addr could not be refered in
APP side,  looks like  the address is alloc in segment_manager_init L293,

I used the example vcl.conf you provided, just comments the line
"api-socket-name /run/vpp-api.sock".

==

VCL<23469>: configured VCL debug level (4) from VCL_DEBUG!
VCL<23469>: allocated VCL heap = 0x7fffe010, size 268435456 (0x1000)
VCL<23469>: configured app_scope_local (1)
VCL<23469>: configured app_scope_global (1)
VCL<23469>: configured with mq with eventfd
VCL<23469>: completed parsing vppcom config!
vppcom_connect_to_vpp:803: VCL<23469>: app (ldp-23469-app) connecting to
VPP api (/vpe-api)...
[New Thread 0x7fffd700 (LWP 23474)]
vppcom_connect_to_vpp:819: VCL<23469>: app (ldp-23469-app) is connected to
VPP!
[New Thread 0x7fffdf7fe700 (LWP 23475)]
vppcom_app_create:714: VCL<23469>: sending session enable
vppcom_app_create:724: VCL<23469>: sending app attach

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd700 (LWP 23474)]
0x7510a403 in svm_msg_q_set_consumer_eventfd (mq=0x204005440, fd=0)
at /home/wenjiang/vpp/build-data/../src/svm/message_queue.c:242
242   mq->q->consumer_evtfd = fd;
Missing separate debuginfos, use: debuginfo-install dpdk-18.05-1.x86_64
libgcc-4.8.5-28.el7_5.1.x86_64 libstdc++-4.8.5-28.el7_5.1.x86_64
numactl-libs-2.0.9-7.el7.x86_64
(gdb) bt
#0  0x7510a403 in svm_msg_q_set_consumer_eventfd (mq=0x204005440,
fd=0) at /home/wenjiang/vpp/build-data/../src/svm/message_queue.c:242
#1  0x74fede84 in vl_api_application_attach_reply_t_handler
(mp=0x30066c40) at /home/wenjiang/vpp/build-data/../src/vcl/vcl_bapi.c:119
#2  0x75111bba in msg_handler_internal (am=0x75360880
, the_msg=0x30066c40, trace_it=0, do_it=1, free_it=1) at
/home/wenjiang/vpp/build-data/../src/vlibapi/api_shared.c:425
#3  0x75111e1a in vl_msg_api_handler (the_msg=0x30066c40) at
/home/wenjiang/vpp/build-data/../src/vlibapi/api_shared.c:551
#4  0x75113344 in vl_msg_api_queue_handler (q=0x30207ec0) at
/home/wenjiang/vpp/build-data/../src/vlibapi/api_shared.c:762
#5  0x75117f4e in rx_thread_fn (arg=0x0) at
/home/wenjiang/vpp/build-data/../src/vlibmemory/memory_client.c:94
#6  0x7763ce25 in start_thread (arg=0x7fffd700) at
pthread_create.c:308
#7  0x7715ebad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113



startup.conf
root@192.168.122.252:/home/wenjiang/dmm/release/bin (master) $ cat
~/startup.conf
unix {
  #nodaemon
  interactive
  log /var/log/vpp/vpp.log
  cli-listen localhost:5002
  full-coredump
}

api-trace {
  on
}


dpdk {
  socket-mem 1024
  dev :00:09.0
}

session { evt_qs_memfd_seg  }
#socksvr { socket-name /run/vpp-api.sock }

==
root@192.168.122.252:/home/wenjiang/dmm/release/bin (master) $ cat
/etc/vpp/vcl.conf
vcl {
  #rx-fifo-size 400
  #tx-fifo-size 400
  app-scope-local
  app-scope-global
  #api-socket-name /run/vpp-api.sock
  use-mq-eventfd
}






Florin Coras  于2018年8月14日周二 下午11:15写道：

> Hi Yalei,
>
> You have an example of how to write a vcl.conf file in vcl/vcl_test.conf.
> It’s just an example, so if you want to try out eventfd, here’s what I’ve
> been recently using:
>
> vcl {
>   rx-fifo-size 400
>   tx-fifo-size 400
>   app-scope-local
>   app-scope-global
>   api-socket-name /run/vpp-api.sock
>   use-mq-eventfd
> }
>
> For this to work, vpp must come up with the binary api socket transport
> configured and the session layer event queues must be allocated in a memfd
> segment. So, add the following to your vpp startup conf:
>
> socksvr { socket-name /run/vpp-api.sock }
> session { evt_qs_memfd_seg  }
>
> Also, to have vcl read your config file, remember to do something like:
> "export VCL_CONFIG=/path/to/your/file”. Finally, this is still very much
> ongoing work so if you hit any issues, do let me know :-)
>
> Hope this helps,
> Florin
>
> > On Aug 14, 2018, at 5:38 AM, 汪亚雷  wrote:
> >
> > Hi Florin,
> >
> > vppcom_cfg_read_file will try to parse the vcl.conf, but where could I
> get the example?
> >
> > actually I want to have a try "use-mq-eventfd"
> >
> > Thanks!
> >
> > /yalei
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] NAT Fragment Reassembly

[Jon Loeliger]

VPPeople,

A few months ago, the vppctl command 'set interface reassembly' was
added along with its API call, ip_reassembly_enable_disable (commit
4c53313cd7e9b866412ad3e04b2d91ac098c1398).

What is the relationship of this fragment reassembly and this
enable/disable flag WRT to the NAT's fragment reassembly?

Specifically, should a NAT fragment reassembly be controlled by this flag?
Empirically, the answer is 'yes'.

So it appears that one should interpret this enable/disable flag more like:

When you use `set interface reassembly  off`, the  fragments are
forwarded
without any sort of reassembly.  The fragments flow through
unmolested.  The NAT
fragmentation limits are not respected as they aren't even involved.

When you use `set interface reassembly  on`, the fragments are
reassembled
before being forwarded.  So the interface will process, and possibly
limit, fragment
reassembly, even for NAT rewritten packets.

Does that sound right?

And should the reassembly be enabled/disabled on the ingress interface?
Or are there different scenarios where one would want them reassembled on
the egress interface?

Thanks,
jdl
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

[Michael Yu]

Hello Dave,

Thanks much for the answer and guide, I will study and have a try on IRB.
Regarding to the interface selection, as I mentioned in another email, we don’t 
want to rely on the standard route procedure performed in lookup node.
we are thinking about some product specific logic to decide which VLAN to tag 
the packet and which interface to send it out, VRF sounds like a promising 
solution for now.

Best Regards
Michael


From: Dave Barach (dbarach) 
Sent: 2018年8月14日 19:44
To: Yu, Michael A. (NSB - CN/Qingdao) ; vpp-dev 

Cc: Neale Ranns (nranns) ; Ole Troan 
Subject: RE: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

Dear Michael,

It is completely normal for a router data plane to forbid this scenario. Given 
a packet to route to 13.13.13.114, which interface should the data plane choose?

From what I can tell, it looks like you’re trying to route untagged as well as 
VLAN 11 and VLAN 12 packets. This sounds like an IRB use case to me. Please see 
https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#VLAN_Tag_Rewrite

HTH... Dave

From: vpp-dev@lists.fd.io 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Michael Yu
Sent: Monday, August 13, 2018 10:48 PM
To: vpp-dev mailto:vpp-dev@lists.fd.io>>
Cc: Neale Ranns (nranns) mailto:nra...@cisco.com>>; Ole Troan 
mailto:otr...@employees.org>>
Subject: Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

Hello,

I have checked the latest code in master branch and confirm ” VPP does not 
support multiple interfaces in the same subnet” is still true.
And I can understand the commit https://gerrit.fd.io/r/#/c/8057/ is to expand 
the check of overlapping subnet to all interfaces in the same table/VRF.
From draft check and previous discussion I can also understand that the 
limitation is that only one fib entry (the latter one) can exist in the fib 
table for one given subnet, but I am not sure if this is the only place 
limitation exists.
And from what I see there is no plan to support “multiple interfaces in the 
same subnet” configuration.

Could you help confirm my understanding? Thanks.
Actually overlapping IP configuration is one of use cases we want to support in 
our project so we want to understand the limitation and to see how we can 
handle it, thanks for your help.

Best Regards
Michael

From: Yu, Michael A. (NSB - CN/Qingdao)
Sent: 2018年8月13日 14:51
To: 'Neale Ranns' mailto:nra...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Overlapping IP/subnet support on base/vlan interface

Hello Neale and VPP experts,

We have one use case to support in VPP, to configure overlapping IP on flat 
interface and VLAN sub-interface, like below:

Eth1-- 13.13.13.114
Eth1.11  -- 13.13.13.114
Eth1.12  -- 13.13.13.114

But we found that this kind of configuration is not supported yet and below 
error would be printed after we configure one IP on the flat interface and when 
we configure the same IP on the vlan sub-interface. (we are using 18.01)

[root@localhost tools]# vppctl set int ip addr host-veth1.111 13.13.13.114/24
set interface ip address: Prefix 13.13.13.114/24 already found on interface 
host-veth1

We made some search and found in attached email it’s claimed ” VPP does not 
support multiple interfaces in the same subnet.” and 
https://gerrit.fd.io/r/#/c/8057/ was submitted to forbid this kind of 
configuration.

Our questions are that:


1.  If the statement ” VPP does not support multiple interfaces in the same 
subnet” is still true in latest implementation? (my assumption is yes)

2.  Is there any plan to support this kind of configuration (overlapping subnet 
or IP on flat interface and vlan sub-interface) in the future?

3.  Do you know where this limitation comes from? we want to understand the 
feasibility to break this limitation.

Could you help? Thanks!

Best Regards
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

[Michael Yu]

Hello Ole,

I just had a try on VRF, probably this is what I am looking for.
Regarding to the FIB lookup, we don’t want to rely on the standard route 
procedure performed in lookup node.
We are thinking about some product specific logic to decide which VLAN to tag 
the packet and which interface to send packet out.

host-veth1 (up):
  13.13.13.114/24
host-veth1.111 (up):
  13.13.13.114/24 table 2

Thanks much for your help.

Best Regards
Michael

-Original Message-
From: Ole Troan  
Sent: 2018年8月14日 17:46
To: Yu, Michael A. (NSB - CN/Qingdao) 
Cc: vpp-dev ; Neale Ranns 
Subject: Re: Overlapping IP/subnet support on base/vlan interface

Michael,

> I have checked the latest code in master branch and confirm ” VPP does not 
> support multiple interfaces in the same subnet” is still true.
> And I can understand the commit https://gerrit.fd.io/r/#/c/8057/ is to expand 
> the check of overlapping subnet to all interfaces in the same table/VRF.
> From draft check and previous discussion I can also understand that the 
> limitation is that only one fib entry (the latter one) can exist in the fib 
> table for one given subnet, but I am not sure if this is the only place 
> limitation exists.
> And from what I see there is no plan to support “multiple interfaces in the 
> same subnet” configuration.
>  
> Could you help confirm my understanding? Thanks.
> Actually overlapping IP configuration is one of use cases we want to support 
> in our project so we want to understand the limitation and to see how we can 
> handle it, thanks for your help.

This is traditionally solved by either VRFs or bridging.
Can you explain how you imagine this to work?

How should the FIB lookup work how should address resolution work?

Best regards,
Ole


> From: Yu, Michael A. (NSB - CN/Qingdao)
> Sent: 2018年8月13日 14:51
> To: 'Neale Ranns' ; vpp-dev 
> Subject: Overlapping IP/subnet support on base/vlan interface
>  
> Hello Neale and VPP experts,
>  
> We have one use case to support in VPP, to configure overlapping IP on flat 
> interface and VLAN sub-interface, like below:
>  
> Eth1-- 13.13.13.114
> Eth1.11  -- 13.13.13.114
> Eth1.12  -- 13.13.13.114
>  
> But we found that this kind of configuration is not supported yet and 
> below error would be printed after we configure one IP on the flat 
> interface and when we configure the same IP on the vlan sub-interface. 
> (we are using 18.01)
>  
> [root@localhost tools]# vppctl set int ip addr host-veth1.111 
> 13.13.13.114/24 set interface ip address: Prefix 13.13.13.114/24 
> already found on interface host-veth1
>  
> We made some search and found in attached email it’s claimed ” VPP does not 
> support multiple interfaces in the same subnet.” and 
> https://gerrit.fd.io/r/#/c/8057/was submitted to forbid this kind of 
> configuration.
>  
> Our questions are that:
>  
> 1.   If the statement ” VPP does not support multiple interfaces in the 
> same subnet” is still true in latest implementation? (my assumption is yes)
> 2.   Is there any plan to support this kind of configuration (overlapping 
> subnet or IP on flat interface and vlan sub-interface) in the future?
> 3.   Do you know where this limitation comes from? we want to understand 
> the feasibility to break this limitation.  
>  
> Could you help? Thanks!
>  
> Best Regards
> Michael

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] LACP link bonding issue

[steven luong via Lists.Fd.Io]

I forgot to ask if these 2 boxes’ interfaces are connected back to back or 
through a switch.

Steven

From:  on behalf of "steven luong via Lists.Fd.Io" 

Reply-To: "Steven Luong (sluong)" 
Date: Tuesday, August 14, 2018 at 8:24 AM
To: Aleksander Djuric , "vpp-dev@lists.fd.io" 

Cc: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] LACP link bonding issue

Aleksander

It looks like the LACP packets are not going out to the interfaces as expected 
or being dropped. Additional output and trace are needed to determine why. 
Please collect the following from both sides.

clear hardware
clear error

wait a few seconds

show hardware
show error
show lacp details
trace add dpdk-input 50

wait a few seconds

show trace

Steven

From:  on behalf of Aleksander Djuric 

Date: Tuesday, August 14, 2018 at 7:28 AM
To: "vpp-dev@lists.fd.io" 
Subject: [vpp-dev] LACP link bonding issue

Hi all,

I'm trying to setup bonding in mode 4 (LACP) between 2 VPP hosts and
I have encounterd the problem of no active slaves on bond interface. Both hosts 
runs VPP v18.10-rc0. Same config runs perfect in other modes. Any idea?

1st VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.1/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

2nd VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.2/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

vpp1# ping 10.0.0.2
Statistics: 5 sent, 0 received, 100% packet loss

vpp1# sh int
 Name   IdxState  MTU (L3/IP4/IP6/MPLS) Counter 
 Count
BondEthernet0 5  up  9000/0/0/0 tx packets  
  10
   tx bytes 
420
   drops
 10
GigabitEtherneta/0/0  1  up  9000/0/0/0 tx-error
   1
GigabitEtherneta/0/1  2  up  9000/0/0/0 tx-error
   1
GigabitEtherneta/0/2  3 down 9000/0/0/0
GigabitEtherneta/0/3  4 down 9000/0/0/0
local00 down  0/0/0/0   drops   
   2

vpp1# sh bond
interface name   sw_if_index  mode load balance  active slaves  slaves
BondEthernet05lacp l23   0  2

vpp1# show lacp
actor state 
 partner state
interface namesw_if_index  bond interface   
exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act
GigabitEtherneta/0/0  1BondEthernet0  0   0   0   0   0   1 
  1   10   0   0   0   0   0   0   1
  LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0001), 
(,00-00-00-00-00-00,0005,00ff,0001)]
  RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX
GigabitEtherneta/0/1  2BondEthernet0  0   0   0   0   0   1 
  1   10   0   0   0   0   0   0   1
  LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0002), 
(,00-00-00-00-00-00,0005,00ff,0002)]
  RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX

Regards,
Aleksander

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] LACP link bonding issue

[steven luong via Lists.Fd.Io]

Aleksander

It looks like the LACP packets are not going out to the interfaces as expected 
or being dropped. Additional output and trace are needed to determine why. 
Please collect the following from both sides.

clear hardware
clear error

wait a few seconds

show hardware
show error
show lacp details
trace add dpdk-input 50

wait a few seconds

show trace

Steven

From:  on behalf of Aleksander Djuric 

Date: Tuesday, August 14, 2018 at 7:28 AM
To: "vpp-dev@lists.fd.io" 
Subject: [vpp-dev] LACP link bonding issue

Hi all,

I'm trying to setup bonding in mode 4 (LACP) between 2 VPP hosts and
I have encounterd the problem of no active slaves on bond interface. Both hosts 
runs VPP v18.10-rc0. Same config runs perfect in other modes. Any idea?

1st VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.1/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

2nd VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.2/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

vpp1# ping 10.0.0.2
Statistics: 5 sent, 0 received, 100% packet loss

vpp1# sh int
 Name   IdxState  MTU (L3/IP4/IP6/MPLS) Counter 
 Count
BondEthernet0 5  up  9000/0/0/0 tx packets  
  10
   tx bytes 
420
   drops
 10
GigabitEtherneta/0/0  1  up  9000/0/0/0 tx-error
   1
GigabitEtherneta/0/1  2  up  9000/0/0/0 tx-error
   1
GigabitEtherneta/0/2  3 down 9000/0/0/0
GigabitEtherneta/0/3  4 down 9000/0/0/0
local00 down  0/0/0/0   drops   
   2

vpp1# sh bond
interface name   sw_if_index  mode load balance  active slaves  slaves
BondEthernet05lacp l23   0  2

vpp1# show lacp
actor state 
 partner state
interface namesw_if_index  bond interface   
exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act
GigabitEtherneta/0/0  1BondEthernet0  0   0   0   0   0   1 
  1   10   0   0   0   0   0   0   1
  LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0001), 
(,00-00-00-00-00-00,0005,00ff,0001)]
  RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX
GigabitEtherneta/0/1  2BondEthernet0  0   0   0   0   0   1 
  1   10   0   0   0   0   0   0   1
  LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0002), 
(,00-00-00-00-00-00,0005,00ff,0002)]
  RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state: 
PERIODIC_TX

Regards,
Aleksander

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Where could I find the example of vcl.conf

[Florin Coras]

Hi Yalei, 

You have an example of how to write a vcl.conf file in vcl/vcl_test.conf. It’s 
just an example, so if you want to try out eventfd, here’s what I’ve been 
recently using:

vcl {
  rx-fifo-size 400
  tx-fifo-size 400
  app-scope-local
  app-scope-global
  api-socket-name /run/vpp-api.sock
  use-mq-eventfd
}

For this to work, vpp must come up with the binary api socket transport 
configured and the session layer event queues must be allocated in a memfd 
segment. So, add the following to your vpp startup conf:

socksvr { socket-name /run/vpp-api.sock }
session { evt_qs_memfd_seg  }

Also, to have vcl read your config file, remember to do something like: "export 
VCL_CONFIG=/path/to/your/file”. Finally, this is still very much ongoing work 
so if you hit any issues, do let me know :-)

Hope this helps, 
Florin

> On Aug 14, 2018, at 5:38 AM, 汪亚雷  wrote:
> 
> Hi Florin,
> 
> vppcom_cfg_read_file will try to parse the vcl.conf, but where could I get 
> the example?
> 
> actually I want to have a try "use-mq-eventfd"
> 
> Thanks!
> 
> /yalei

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] VPP and mlx4 issue

[Brandon Kopinski]

Hi,

I have been trying to use VPP with the mlx4 pmd.  However, VPP is not
processing any packets.  My current setup includes two machines that are
directly connected.  One machine is running VPP with the mlx4 pmd.  The
other machine is using the Linux kernel for networking. I assigned an ip
address (10.0.1.1/24) to the VPP interface and brought the interface up. I
assigned (10.0.1.2/24) to the interface on the other machine and brought it
up. Pinging the VPP interface from the other machine is unsuccessful. Also,
the 'show int' command displays 'dpdk tx failure' after pinging from VPP.
I was able to verify with a debugger that the RX queues are being polled,
but there are no packets available to process.  I enabled tracing on the
dpdk input node, but no packets end up being traced.  I'm not sure if this
is just a configuration issue or some other problem.

Here is the VPP and DPDK versions I am currently using. Any help will be
greatly appreciated.

Version:  v18.10-rc0~43-g631de0d
Compiled by:  bkopinski
Compile host: localhost.localdomain
Compile date: Wed Aug  1 14:13:41 EDT 2018
Compile location: /home/bkopinski/sw/vpp
Compiler: GCC 4.8.5 20150623 (Red Hat 4.8.5-28)
Current PID:  7355

DPDK Version: DPDK 18.05.0
DPDK EAL init args:   -c 2 -n 4 --huge-dir /run/vpp/hugepages
--file-prefix vpp -w :09:00.0 --master-lcore 1 --socket-mem 1024


Sincerely,
Brandon Kopinski
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] LACP link bonding issue

[Aleksander Djuric]

Hi all,

I'm trying to setup bonding in mode 4 (LACP) between 2 VPP hosts and
I have encounterd the problem of no active slaves on bond interface. Both
hosts runs VPP v18.10-rc0. Same config runs perfect in other modes. Any
idea?

1st VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.1/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

2nd VPP config:

create bond mode lacp load-balance l23
bond add BondEthernet0 GigabitEtherneta/0/0
bond add BondEthernet0 GigabitEtherneta/0/1
set interface ip address BondEthernet0 10.0.0.2/24
set interface state GigabitEtherneta/0/0 up
set interface state GigabitEtherneta/0/1 up
set interface state BondEthernet0 up

vpp1# ping 10.0.0.2
> Statistics: 5 sent, 0 received, 100% packet loss
>


> vpp1# sh int
>  Name   IdxState  MTU (L3/IP4/IP6/MPLS)
> Counter  Count
> BondEthernet0 5  up  9000/0/0/0 tx
> packets10
>tx
> bytes 420
>drops
> 10
> GigabitEtherneta/0/0  1  up  9000/0/0/0
> tx-error   1
> GigabitEtherneta/0/1  2  up  9000/0/0/0
> tx-error   1
> GigabitEtherneta/0/2  3 down 9000/0/0/0
> GigabitEtherneta/0/3  4 down 9000/0/0/0
> local00 down  0/0/0/0   drops
>  2



> vpp1# sh bond
> interface name   sw_if_index  mode load balance  active slaves
> slaves
> BondEthernet05lacp l23   0  2
>


> vpp1# show lacp
> actor state
>   partner state
> interface namesw_if_index  bond interface
>  exp/def/dis/col/syn/agg/tim/act  exp/def/dis/col/syn/agg/tim/act
> GigabitEtherneta/0/0  1BondEthernet0  0   0   0   0
>  0   1   1   10   0   0   0   0   0   0   1
>   LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0001),
> (,00-00-00-00-00-00,0005,00ff,0001)]
>   RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state:
> PERIODIC_TX
> GigabitEtherneta/0/1  2BondEthernet0  0   0   0   0
>  0   1   1   10   0   0   0   0   0   0   1
>   LAG ID: [(,00-0b-ab-f4-f9-66,0005,00ff,0002),
> (,00-00-00-00-00-00,0005,00ff,0002)]
>   RX-state: EXPIRED, TX-state: TRANSMIT, MUX-state: DETACHED, PTX-state:
> PERIODIC_TX


Regards,
Aleksander
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] :: vppctl fails to start (Centos 7.5.1804)

[Billy]

Omer,

On CentOS, the 'vpp' RPM has a prerequisite on the 'vpp-selinux-policy'
RPM, so the 'vpp-selinux-policy' RPM should have already been installed.
Can you confirm if the 'vpp-selinux-policy' RPM was already installed? Any
logs around the error?

Thanks,
Billy McFall

On Mon, Aug 13, 2018 at 1:43 PM, Edward Warnicke  wrote:

> We do have an se linux package that should in principle let you keep
> working with se linux enforce
> try
>
> yum install vpp-selinux-policy
>
> and see if that helps :)
>
> Ed
>
> On August 13, 2018 at 12:41:37 PM, omer.maj...@sofioni.com (
> omer.maj...@sofioni.com) wrote:
>
> Thank Ed.
>
> Changed SELINUX=enforcing in /etc/selinux/config
>
> Restarted the machine, and it worked.
>
> Best Regards,
>
> Omer
>
>
>
> On 2018-08-13 22:21, Edward Warnicke wrote:
>
> This feels like SE Linux may be involved...
>
> Ed
>
>
>
> On August 13, 2018 at 12:17:09 PM, omer.maj...@sofioni.com (
> omer.maj...@sofioni.com) wrote:
>
>
>
> Hi,
>
> I've built VPP on centos 7.5.1804, took the RPM packages to another
> machine to deploy VPP there.
>
> After installing RPM packages there when I run $vppctl it gives me
> following error.
>
> *clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): No such file or
> directory*
>
>
> I thought there might be something wrong with the build or something so
> took packages from following repository
>
> http://a.centos.org/centos/7.5.1804/nfv/x86_64/fdio/vpp/vpp-1804/
>
> I get the same error when running vppctl after installation. Could someone
> help with the error?
>
> Best Regards,
>
> Omer
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10126): https://lists.fd.io/g/vpp-dev/message/10126
> Mute This Topic: https://lists.fd.io/mt/24505099/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10127): https://lists.fd.io/g/vpp-dev/message/10127
> Mute This Topic: https://lists.fd.io/mt/24505099/984664
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [omer.maj...@sofioni.com
> ]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10129): https://lists.fd.io/g/vpp-dev/message/10129
> Mute This Topic: https://lists.fd.io/mt/24505099/675237
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [bmcf...@redhat.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>


-- 
*Billy McFall*
Networking Group
CTO Office
*Red Hat*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[vpp-dev] Where could I find the example of vcl.conf

[wylandrea]

Hi Florin,

vppcom_cfg_read_file will try to parse the vcl.conf, but where could I get
the example?

actually I want to have a try "use-mq-eventfd"

Thanks!

/yalei
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] NAT64 TCP Session never expire

[Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io]

Hi,

Fix for TCP expire issue https://gerrit.fd.io/r/#/c/14207/

Matus


From: vpp-dev@lists.fd.io  On Behalf Of xuliang
Sent: Monday, August 13, 2018 6:32 AM
To: vpp-dev@lists.fd.io
Cc: mocan ; wenxu ; 'houzhiyuan' 

Subject: [vpp-dev] NAT64 TCP Session never expire

Hi Dear VPP，

   I did some testing on the Stateful NAT64 feature last week and found that 
the tcp session never times out.

   I checked the source code and found :
   a. because nat64_tcp_session_set_state has not been called, 
nat64_db_st_entry_t.tcp_state == 0 (CLOSED)
   b. calling nat64_session_reset_timeout, the nat64_db_st_entry_t.expire never 
be set

   I think it's BUG, right ?

  Other question about multiple thread. There is BIB and session DB per thread 
in nat64_main_t. How to ensure that IPv6 and IPv4 packets of the same session 
are processed by the same thread?


徐亮 | Leo.Xu
网络架构部
Tel：  021-55509888
Mobile：   18049731937
Email: leo...@ucloud.cn
Homepage:www.ucloud.cn
Address：  上海市杨浦区隆昌路619号城市概念创业园区10号楼B座
UCloud-专业云计算服务商 | 上海 ・ 北京 ・ 深圳・ 广州 ・ 成都・ 杭州
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

[Dave Barach via Lists.Fd.Io]

Dear Michael,

It is completely normal for a router data plane to forbid this scenario. Given 
a packet to route to 13.13.13.114, which interface should the data plane choose?

>From what I can tell, it looks like you’re trying to route untagged as well as 
>VLAN 11 and VLAN 12 packets. This sounds like an IRB use case to me. Please 
>see 
>https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#VLAN_Tag_Rewrite

HTH... Dave

From: vpp-dev@lists.fd.io  On Behalf Of Michael Yu
Sent: Monday, August 13, 2018 10:48 PM
To: vpp-dev 
Cc: Neale Ranns (nranns) ; Ole Troan 
Subject: Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

Hello,

I have checked the latest code in master branch and confirm ” VPP does not 
support multiple interfaces in the same subnet” is still true.
And I can understand the commit https://gerrit.fd.io/r/#/c/8057/ is to expand 
the check of overlapping subnet to all interfaces in the same table/VRF.
>From draft check and previous discussion I can also understand that the 
>limitation is that only one fib entry (the latter one) can exist in the fib 
>table for one given subnet, but I am not sure if this is the only place 
>limitation exists.
And from what I see there is no plan to support “multiple interfaces in the 
same subnet” configuration.

Could you help confirm my understanding? Thanks.
Actually overlapping IP configuration is one of use cases we want to support in 
our project so we want to understand the limitation and to see how we can 
handle it, thanks for your help.

Best Regards
Michael

From: Yu, Michael A. (NSB - CN/Qingdao)
Sent: 2018年8月13日 14:51
To: 'Neale Ranns' mailto:nra...@cisco.com>>; vpp-dev 
mailto:vpp-dev@lists.fd.io>>
Subject: Overlapping IP/subnet support on base/vlan interface

Hello Neale and VPP experts,

We have one use case to support in VPP, to configure overlapping IP on flat 
interface and VLAN sub-interface, like below:

Eth1-- 13.13.13.114
Eth1.11  -- 13.13.13.114
Eth1.12  -- 13.13.13.114

But we found that this kind of configuration is not supported yet and below 
error would be printed after we configure one IP on the flat interface and when 
we configure the same IP on the vlan sub-interface. (we are using 18.01)

[root@localhost tools]# vppctl set int ip addr host-veth1.111 13.13.13.114/24
set interface ip address: Prefix 13.13.13.114/24 already found on interface 
host-veth1

We made some search and found in attached email it’s claimed ” VPP does not 
support multiple interfaces in the same subnet.” and 
https://gerrit.fd.io/r/#/c/8057/ was submitted to forbid this kind of 
configuration.

Our questions are that:


1. If the statement ” VPP does not support multiple interfaces in the same 
subnet” is still true in latest implementation? (my assumption is yes)

2. Is there any plan to support this kind of configuration (overlapping 
subnet or IP on flat interface and vlan sub-interface) in the future?

3. Do you know where this limitation comes from? we want to understand the 
feasibility to break this limitation.

Could you help? Thanks!

Best Regards
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Regarding CLI command parsing

[Prashant Upadhyaya]

Thanks Dave !
Your trick worked for me exactly as I needed.

Regards
-Prashant


On Mon, Aug 13, 2018 at 11:39 PM, Dave Barach (dbarach)
 wrote:
> Try this in mycmd:
>
> u8 * line;
> if (unformat (input, "%U", unformat_line, ))
>process_line;
>
> Note that line will be a true u8 * vector: no null-termination. If you need 
> null termination: vec_add1 (line, 0);
>
> Remember to vec_free(...) it unless you're planning to keep it.
>
> HTH... Dave
>
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Prashant 
> Upadhyaya
> Sent: Monday, August 13, 2018 1:53 PM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Regarding CLI command parsing
>
> Hi,
>
> I am relatively new to this and trying to learn the art of using 
> format/unformat.
> My requirement is that if my command is "mycmd" followed by some string 
> (which may have spaces in it), then I should be able to read the entire 
> string up to the \n character typed by the user.
>
> Eg. if the command is typed like
>
> mycmd foo1 foo2 foo3
>
> (the "path" of the VLIB_CLI_COMMAND  is "mycmd") Then in my CLI callback 
> function, I want to be able to get the string
> "foo1 foo2 foo3" setup in a u8* variable. If the leading and trailing spaces 
> are trimmed, I am fine by that. I am looking for the correct way to call the 
> unformat functions in my command callback function to achieve this.
>
> Regards
> -Prashant
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] Overlapping IP/subnet support on base/vlan interface

[Ole Troan]

Michael,

> I have checked the latest code in master branch and confirm ” VPP does not 
> support multiple interfaces in the same subnet” is still true.
> And I can understand the commit https://gerrit.fd.io/r/#/c/8057/ is to expand 
> the check of overlapping subnet to all interfaces in the same table/VRF.
> From draft check and previous discussion I can also understand that the 
> limitation is that only one fib entry (the latter one) can exist in the fib 
> table for one given subnet, but I am not sure if this is the only place 
> limitation exists.
> And from what I see there is no plan to support “multiple interfaces in the 
> same subnet” configuration.
>  
> Could you help confirm my understanding? Thanks.
> Actually overlapping IP configuration is one of use cases we want to support 
> in our project so we want to understand the limitation and to see how we can 
> handle it, thanks for your help.

This is traditionally solved by either VRFs or bridging.
Can you explain how you imagine this to work?

How should the FIB lookup work how should address resolution work?

Best regards,
Ole


> From: Yu, Michael A. (NSB - CN/Qingdao) 
> Sent: 2018年8月13日 14:51
> To: 'Neale Ranns' ; vpp-dev 
> Subject: Overlapping IP/subnet support on base/vlan interface
>  
> Hello Neale and VPP experts,
>  
> We have one use case to support in VPP, to configure overlapping IP on flat 
> interface and VLAN sub-interface, like below:
>  
> Eth1-- 13.13.13.114
> Eth1.11  -- 13.13.13.114
> Eth1.12  -- 13.13.13.114
>  
> But we found that this kind of configuration is not supported yet and below 
> error would be printed after we configure one IP on the flat interface and 
> when we configure the same IP on the vlan sub-interface. (we are using 18.01)
>  
> [root@localhost tools]# vppctl set int ip addr host-veth1.111 13.13.13.114/24
> set interface ip address: Prefix 13.13.13.114/24 already found on interface 
> host-veth1
>  
> We made some search and found in attached email it’s claimed ” VPP does not 
> support multiple interfaces in the same subnet.” and 
> https://gerrit.fd.io/r/#/c/8057/was submitted to forbid this kind of 
> configuration.
>  
> Our questions are that:
>  
> 1.   If the statement ” VPP does not support multiple interfaces in the 
> same subnet” is still true in latest implementation? (my assumption is yes)
> 2.   Is there any plan to support this kind of configuration (overlapping 
> subnet or IP on flat interface and vlan sub-interface) in the future?
> 3.   Do you know where this limitation comes from? we want to understand 
> the feasibility to break this limitation.  
>  
> Could you help? Thanks!
>  
> Best Regards
> Michael

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] syslog in snat

[Ole Troan]

Hi Matt,

> I see NAT syslog mentioned in the VPP 18.07 release notes 
> (https://docs.fd.io/vpp/18.07/release_notes_1807.html) but I'm unable to find 
> documentation on how to implement, any tips? Or are there examples somewhere?

Currently only ipfix supported.
Feel free to provide a patch. We could consider a “logging” module to shared 
memory, and an external agent that would produce syslog, ipfix or whatever 
other NAT telemetry you needed.
Patches welcome! ;-)

Best regards,
Ole-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [vpp-dev] NAT64 TCP Session never expire

[Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES@Cisco) via Lists.Fd.Io]

Hi,

You are right there is bug.

For multiple thread there is handoff node which send packet to correct thread.


Matus


From: vpp-dev@lists.fd.io  On Behalf Of xuliang
Sent: Monday, August 13, 2018 6:32 AM
To: vpp-dev@lists.fd.io
Cc: mocan ; wenxu ; 'houzhiyuan' 

Subject: [vpp-dev] NAT64 TCP Session never expire

Hi Dear VPP，

   I did some testing on the Stateful NAT64 feature last week and found that 
the tcp session never times out.

   I checked the source code and found :
   a. because nat64_tcp_session_set_state has not been called, 
nat64_db_st_entry_t.tcp_state == 0 (CLOSED)
   b. calling nat64_session_reset_timeout, the nat64_db_st_entry_t.expire never 
be set

   I think it's BUG, right ?

  Other question about multiple thread. There is BIB and session DB per thread 
in nat64_main_t. How to ensure that IPv6 and IPv4 packets of the same session 
are processed by the same thread?


徐亮 | Leo.Xu
网络架构部
Tel：  021-55509888
Mobile：   18049731937
Email: leo...@ucloud.cn
Homepage:www.ucloud.cn
Address：  上海市杨浦区隆昌路619号城市概念创业园区10号楼B座
UCloud-专业云计算服务商 | 上海 ・ 北京 ・ 深圳・ 广州 ・ 成都・ 杭州
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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