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@lis
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 co
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
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
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
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
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 d
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
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
addres
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 Bon
Hi Billy,
Btw, are you planning to release Vpp 1807 ?
Jerome
Le 14 août 2018 à 10:08, Billy mailto:bmcf...@redhat.com>>
a écrit :
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
con
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:
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
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 te
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
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, &line))
>process_line;
>
> Note that line will be a true u8 * vector:
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 t
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 c
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 Se
19 matches
Mail list logo