Hi,
We have 3 interfaces. First two belong to different VRFs and the third one
is a global interface (GigabitEthernet0/6/0).
How we can configure VPP so that the packets received through any of the
first two interfaces will be sent to the global interface
(GigabitEthernet0/6/0).
The default GW is
hanks,
>
> neale
>
>
>
> *From: * on behalf of Michael Borokhovich <
> michael...@gmail.com>
> *Date: *Wednesday, 9 August 2017 at 18:50
> *To: *"vpp-dev@lists.fd.io"
> *Subject: *[vpp-dev] Configuring multiple VFRs
>
>
>
> Hi,
>
>
Hi,
We are using VPP 1707 and the load balancer plugin.
We have only one public IP available for the load balancer VM and we use
this IP as VIP.
In the VPP 1609, we were able to assign the same VIP to the public
interface and everything worked fine.
However, in VPP 1707, the behaviour has chang
Hi,
Is there an example of how to configure the FIB to push/pop MSPL labels?
I see that the set of MPLS commands has changed (reduced) between 1609 and
1707.
Any simple example would help.
Thanks,
Michael.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
.fd.io/images/7/71/FIB_2.0_-_Hierarchical%2C_
> Protocol_Independent..pdf
>
>
>
> thanks,
>
> neale
>
>
>
> *From: * on behalf of Michael Borokhovich <
> michael...@gmail.com>
> *Date: *Thursday, 10 August 2017 at 17:01
> *To: *"vpp-dev@list
Hi,
I'm adding a label using the following command:
ip route add 10.100.2.0/24 table 1 via 10.100.4.12 GigabitEthernet0/6/0
out-label 222
And on the receiving side poping it with:
set interface mpls GigabitEthernet0/6/0 enable
mpls local-label 222 ip4-lookup-in-table 1
However, this didn't wor
>
>
>
> ‘add’ is the default.
>
> It’s necessary to specify ‘eos’ because it I the end-of-stack entry you
> are adding and the default (i.e. without ‘eos’) is to add the
> non-end-of-stack entry.
>
>
>
> Regards,
>
> neale
>
>
>
> *From: * on behal
00.2.0/24) then
> the command you are looking for is;
>
>mpls local-label 222 10.100.2.0/24
>
> this does what the API refers to as a ‘bind’. It says, whatever IP does
> for 10.100.2.0/24, MPLS should do for label 222. It will add the eos and
> non-eos entries appropri
Hi,
Is it true that in VPP 1707 we have to give IP to the pg0 interface?
In the previous VPP version (1609), the packet generator worked without IP
address on pg0, but in 1707 it gives "ip4 adjacency drop" and no packets
come out. Configuring pg0 with some fake IP worked.
Thanks,
Michael.
__
gt; interfaces for us to be able to test all the features.
>
>
>
> Regards,
>
> Neale
>
>
>
>
>
> *From: * on behalf of Michael Borokhovich <
> michael...@gmail.com>
> *Date: *Monday, 14 August 2017 at 23:03
> *To: *"vpp-dev@lists.fd.io"
Hi,
Are there APIs available for setting routes and MPLS labels?
Would be great to have REST APIs, but it looks like Honecomb does not
support these operations.
Are there Jvpp APIs for these operations so that we would be able to create
Honecomb plugins for them?
The operations I'm talking about
Hi Burt, Pawel,
Did you eventually manage to install the router plugin with the latest VPP?
Thanks,
Michael.
On Tue, Sep 19, 2017 at 6:05 PM, Burt Silverman wrote:
> Same problem here. I guess the vlib code was updated but the vppsb has not
> caught up.
>
> Burt
>
> On Mon, Sep 18, 2017 at 12
_socket;
>template.private_data = (uword) (ns - rm->streams);
> - ns->unix_index = unix_file_add (&unix_main, &template);
> + ns->unix_index = clib_file_add (&file_main, &template);
>return 0;
> }
>
>
> On Wed, Sep 27, 2017 at 1:41 PM, Michael Boro
hat the README.md in vppsb/router is more reliable than the
> README.md in vppsb/netlink: the reliable README.md will make certain that
> the header files get installed as needed into vpp/build-root/install-vpp-
> native/vpp/include/
>
> Burt
>
> On Wed, Sep 27, 2017 at 2:50 P
Hi,
Is it possible to forward some specific packets (e.g., OSPF control
packets) from VPP to Linux kernel where the routing daemon would run?
I know that router plugin is intended to do this. However, it is not
supported anymore and does not work with the latest VPP.
Is there a way to achieve the
Hi,
I'm trying to configure the following setup.
GigabitEthernet0/4/0 - Table 1
GigabitEthernet0/5/0 - Table 2
GigabitEthernet0/6/0 - Table 0 (default)
If a packet with DST_IP="10.5.1.0/24" received at GigabitEthernet0/4/0 or
GigabitEthernet0/5/0 it needs to be sent via GigabitEthernet0/6/0.
Th
On Wed, Oct 4, 2017 at 10:33 PM, Florin Coras
wrote:
> Michael,
>
> I would recommend you switched to a newer release (17.07 or the soon to be
> release 17.10) since the fib code has been completely reworked in 17.01.
>
> Florin
>
> On Oct 4, 2017, at 7:13 PM, Michael
gt;
> - Pierre
>
>
> Le 5 oct. 2017 à 05:22, Michael Borokhovich a
> écrit :
>
> Hi Florin,
>
> Thank you for the response. The reason I stick to 1609 is the router
> plugin (vppsb) that works with 1609 but does not with any other VPP version
> I tried. So, I
7b9d440 ,
> input=0x7fffb669efb0) at /root/vpp/build-data/../src/vlib/main.c:1774
>
> #8 0x779647d1 in thread0 (arg=140737349538880) at
> /root/vpp/build-data/../src/vlib/unix/main.c:514
>
> #9 0x7663100c in clib_calljmp () at /root/vpp/build-data/../src/
> vppin
/root/vpp/build-data/../src/
> vlib/main.c:1625
>
> #6 0x778f67d6 in vlib_main_loop (vm=0x77b9d440
> ) at /root/vpp/build-data/../src/vlib/main.c:1644
>
> #7 0x778f6e61 in vlib_main (vm=0x77b9d440 ,
> input=0x7fffb669efb0) at /root/vpp/build-data/../src/vlib
should have set this correctly.
>
>
>
> /neale
>
>
>
> *From: *Michael Borokhovich
> *Date: *Friday, 6 October 2017 at 15:49
> *To: *"Shaw, Jeffrey B"
> *Cc: *"Pierre Pfister (ppfister)" , Florin Coras <
> fcoras.li...@gmail.com>, vpp-dev
e at:
>
> Function tap_inject_enabel(): add IPv4 multicast route.
>
> Please take a look at this function and multicast route involved.
>
>
>
> -Hongjun
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Michael Borokhovich
Hi,
After applying the fixes suggested by Jeff, I was able to compile the
router plugin with VPP 1707.
It runs and allows to enable tap-inject and set up interfaces addresses
without crashing.
The problem I'm facing now is with setting up FRR OSPF on top of the
VPP+router plugin.
FRR OSPF is co
1:18 PM, Shaw, Jeffrey B
wrote:
> I’ve submitted changes 8716, 8717, and 8718, which should fix the issues
> we’ve discussed in this thread.
>
>
>
> Thanks,
>
> Jeff
>
>
>
> *From:* Michael Borokhovich [mailto:michael...@gmail.com]
> *Sent:* Monday, October 0
nges 8716, 8717, and 8718, which should fix the issues
> we’ve discussed in this thread.
>
>
>
> Thanks,
>
> Jeff
>
>
>
> *From:* Michael Borokhovich [mailto:michael...@gmail.com]
> *Sent:* Monday, October 09, 2017 9:07 AM
> *To:* Ni, Hongjun
> *Cc
cksum 0x2986
fragment id 0x9b15
00:05:18:276595: error-drop
ip4-input: ip4 adjacency drop
On Mon, Oct 9, 2017 at 12:14 PM, Michael Borokhovich
wrote:
> Hi,
>
> After applying the fixes suggested by Jeff, I was able to compile the
> router plugin with VPP 1707.
>
> It
working the same as it has in the past.
>
>
>
> With the FIB changes since the router plugin was initially developed,
> there might be a different/better way to get multicast packets delivered to
> our node.
>
>
>
> -Jef
>
>
>
>
>
> *From:* vppsb-dev
[] [weight
> ]] | [via arp ] |
>
>[via
> drop|punt|local|arp|classify ] [lookup in table
> ]
>
>
>
> -Jeff
>
>
>
> *From:* Michael Borokhovich [mailto:michael...@gmail.com]
> *Sent:* Monday, October 09, 2017
x9b15
00:05:18:276595: error-drop
ip4-input: ip4 adjacency drop
On Tue, Oct 10, 2017 at 4:31 AM, Neale Ranns (nranns)
wrote:
>
>
> Hi Michael,
>
>
>
> Could you give me a ‘sh trace’ ?
>
>
>
> Thanks,
>
> neale
>
>
>
> *From: * on behalf of
> (mfib). Your 224.0.0.0/24 route now needs to be in the mfib not the
> unicast FIB. Please try the mfib APIs I mentioned in my previous mail.
>
>
>
> Thanks,
>
> Neale
>
>
>
>
>
>
>
> *From: *Michael Borokhovich
> *Date: *Wednesday, 11 October 20
Hi,
Does router plugin (vppsb) support MPLS? We would like to use FRR's LDP in
the control plane and VPP in the data plane.
Thanks,
Michael.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Hi,
I can see in "vppsb/netlink/librtnl/mapper.h" that each Linux namespace is
mapped to a separate FIB in VPP.
However, the 4.6 Linux kernel has support for VRFs (e.g., using "ip link
add dev NAME type vrf table ID").
If we use the second (VRFs) approach to create multiple FIBs in Linux, can
th
and VPP's mpls fib?
>
> Thanks
>
>
> On Tue, Nov 14, 2017 at 9:26 PM, Michael Borokhovich > wrote:
>
>> Hi,
>>
>> Does router plugin (vppsb) support MPLS? We would like to use FRR's LDP
>> in the control plane and VPP in the data plane.
>
Hi,
Does router plugin support the following features?
1) Multiple VRFs
2) MPLS
>From our initial experiments, the above features are not supported.
Multiple VRFs do not work (I tried with namespaces).
The MPLS information is not passed from Linux to VPP's FIBs.
Please let me know what you thin
#x27;t support any of these.
>
> Better approach is to use Honeycomb, with or without ODL.
>
> Ray K
>
>
>
> On 22/11/2017 18:53, Michael Borokhovich wrote:
>
>> Hi,
>>
>> Does router plugin support the following features?
>>
>> 1) Multiple
So, for the control plane, we can use e.g., FRR that will populate Linux's
FIB and MPLS table. Then, we need to sync this info to VPP's FIB and VPP's
MPLS table.
While the "router plugin" provides support for FIB synchronization, there
is no support for MPLS sync. Does anyone know if there are pla
er option is to use HC
> instead of FRR for BGP.
>
> Ray K
>
>
> On 08/12/2017 21:23, Michael Borokhovich wrote:
>
>> So, for the control plane, we can use e.g., FRR that will populate
>> Linux's FIB and MPLS table. Then, we need to sync this info to VPP's
37 matches
Mail list logo
