Hi Ole,
ACLS be extended to support port-ranges.
Is there a plan to support ipv6 in URPF?
Thanks,
Xyxue
From: Ole Troan
Date: 2018-04-09 19:23
To: 薛欣颖
CC: vpp-dev
Subject: Re: [vpp-dev] the source_and_port_range_check and the URPF support
ipv6?
Xyxue,
> Do the source_and_port_range_check
All,
I have created the v18.04-rc2 tag on the HEAD of VPP branch stable/1804 and
verified that the build artifacts arrived on nexus.fd.io[1][2]. This completes
the RC2 release milestone for VPP 18.04.
As a reminder, per the release
Hi Ole,
I really don't mind that you all derailed my discussion. I think a good
design discussion is a good thing. Especially when the end result is a
better product, or in this case, better integration between products.
What I have found with respect to OSPFv3, is that the OSPF multicast
packets
> On Apr 11, 2018, at 12:19 PM, Ole Troan wrote:
>
> VPP API used to program routes. learn interface events, addresses etc. Pure
> user-land no involvement from kernel.
>
We’re also not “fans” of the router plugin. (And we’ve done a lot of work on
it.)
We have a
Jan Hugo,
> But this basically means that, for now, it won't be possible to create a BGP
> router with a combination of FRR and VPP doing both IPv4 and IPv6 with OSPF
> and BGP.
> Or do you see possibilities to make OSPFv3 work?
Sorry, for derailing your thread and making it into an
But this basically means that, for now, it won't be possible to create a
BGP router with a combination of FRR and VPP doing both IPv4 and IPv6
with OSPF and BGP.
Or do you see possibilities to make OSPFv3 work?
Jan Hugo Prins
On 04/11/2018 03:20 PM, Ray Kinsella wrote:
> Hi Ole,
>
> I agree -
Hi Ole,
I agree - but completely reinventing the wheel is not a the best course
either. These are tried and tested implementations and are worth
reusing, I do agree that integrating through the Linux Kernel is not ideal.
We developed the router plugin to show that integration was possible we
Hi Jan,
Yes we have been developing/maintaining the router plugin for sometime.
Ray K
On 11/04/2018 00:27, Jan Hugo Prins | BetterBe wrote:
Hello,
Is someone actively maintaining the router plugin?
Jan Hugo
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Ole,
That sounds to me like the router / rtnetlink plugins are a dead horse,
not worth any more of my time ;-)
I have setup a BGP session on IPv4 and the first results are not that
good. The session is setup, the routes are installed in the
Hi Jan Hugo,
> The main thing I'm currently missing is OSPFv3. The multicast packets
> don't arrive in linux kernel.
> Attached is a pcap file showing the dropped packets.
> OSPFv2 seems to be working fine.
> I hope to test the BGP for IPv4 and IPv6 today.
>
> I have put my findings in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Ole,
The main thing I'm currently missing is OSPFv3. The multicast packets
don't arrive in linux kernel.
Attached is a pcap file showing the dropped packets.
OSPFv2 seems to be working fine.
I hope to test the BGP for IPv4 and IPv6 today.
I
Hi Jan,
> Is someone actively maintaining the router plugin?
I'm not a big fan of the router plugin.
The starting point of the router plugin is "how can you take an unmodified
routing protocol implementation and make it work with VPP".
That leads to all kinds of complexities as the two methods
I first bind VF to igb_uio in /etc/rc.local of VM, and I guess VPP take
the config.
I did not edited startup.conf yesterday, and I edit it today as below.
cpu {
workers 2
}
dpdk {
dev :00:08.0
dev :00:09.0
uio-driver igb_uio
}
Anyway, I got to succeed to measure VPP/DPDK
If I remember correctly, you mentioned in early email that you do _NOT_ modify
the startup.conf file for VPP. Can you confirm that?
By looking at the startup.conf file coming with VPP v18.04 the default mechanism
driver used is vfio-pci. That as mentioned before (and found out by you too)
won't
14 matches
Mail list logo