Ben,
Yes, thanks, I can now connect to google.ca through VPP in Azure!
Ok, in that case, do you recommend I open a separate thread for the VPP/NAT
discussion?
Thanks,
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15363): https://lists.fd
Hi Chris,
> I managed to get my internet traffic routed properly using Azure firewall.
Ok, so the problem you mentioned in your previous email is solved (connecting
to google.ca through VPP in Azure)?
> However, I'm looking for a VPP/NAT alternative way to do this and the
> documentation I've r
I managed to get my internet traffic routed properly using Azure firewall.
However, I'm looking for a VPP/NAT alternative way to do this and the
documentation I've read didn't help me much. Does anyone have experience
setting up VPP/NAT in Azure?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all me
Ben,
I am still seeing some odd behaviour when trying to route traffic to the
Internet though (again from Azure). I've added a default route through
FailsafeEthernet2 and this is what I get when trying to connect to
www.google.ca on port 80 with netcat on a box on my 10.4.2.0/24 subnet:
vpp# s
Ben,
Yes, for instance, if I ping a new destination from a new source 10 times, I
will get 8 responses because the first 2 packets are dropped. Once the ARP
entries are in, the pings start going through:
ping -c 10 10.4.2.7
PING 10.4.2.7 (10.4.2.7) 56(84) bytes of data.
64 bytes from 10.4.2.7: i
Hi Chris,
> I've done some testing and am now happy to report that my interfaces are
> receiving and forwarding traffic! This is a great milestone - thanks!
Glad to hear!
> I did, however, run into the ARP issues you mentioned. The first time I
> try to hit a destination IP I notice the followi
Ben,
I've done some testing and am now happy to report that my interfaces are
receiving and forwarding traffic! This is a great milestone - thanks!
I did, however, run into the ARP issues you mentioned. The first time I try to
hit a destination IP I notice the following:
1) first attempt fails,
Ben,
Here is the output you requested - I haven't really tested things yet, but the
devices seem to attach and the hardware says it's up! I think you were right
about running with LD_LIBRARY_PATH in the same runtime environment! There are
still some concerning error messages, but not sure that
o: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] interface activation problem using VPP in Azure
> with DPDK failsafe interfaces #vpp #dpdk #azure
>
> Ben,
>
> I tried what you suggested but it didn't work for me (yet) :-(. In order
> to get the *glue* libraries to build I
[Edited Message Follows]
[Reason: Fix minor typo]
Ben,
I tried what you suggested but it didn't work for me (yet) :-(. In order to
get the *glue* libraries to build I had to go into vpp/build/external/packages
and run 'make dpdk-install'. Then I set LD_LIBRARY_PATH (was previously unset)
and
Ben,
I tried what you suggested but it didn't work for me (yet) :-(. In order to
get the *glue* libraries to build I had to go into vpp/build/external/packages
and run 'make dpdk-install'. Then I set LD_LIBRARY_PATH (was previously unset)
and I issued the following commands:
echo $LD_LIBRARY_
> Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to
> 'y' and I still get the "EAL: Driver cannot attach the device" errors when
> starting VPP.
Do you have LD_LIBRARY_PATH exported so that the DPDK can find the
librte_pmd_mlx[45]_glue.so.* library?
Eg. from the the vpp b
[Edited Message Follows]
[Reason: Renaming 10dtap.link to 10-dtap.link]
Ben,
I'm glad you got it to work - thanks for the info!
Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to 'y'
and I still get the "EAL: Driver cannot attach the device" errors when starting
VPP.
I
Ben,
I'm glad you got it to work - thanks for the info!
Interestingly, I had already modified those 4 lines in dpdk.mk from 'n' to 'y'
and I still get the "EAL: Driver cannot attach the device" errors when starting
VPP.
I noticed in your config file above that it says DPDK_VERSION ?= 19.08. My
ng on it,
> we'll keep you posted (hopefully by end of this week).
>
> Best
> ben
>
> > -Original Message-
> > From: vpp-dev@lists.fd.io On Behalf Of Chris King
> > Sent: mardi 28 janvier 2020 16:56
> > To: vpp-dev@lists.fd.io
> > Subje
lf Of Chris King
> Sent: mardi 28 janvier 2020 16:56
> To: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] interface activation problem using VPP in Azure
> with DPDK failsafe interfaces #vpp #dpdk #azure
>
> Damjan (and group),
>
> Any pointers as to exactly how I would conf
Damjan (and group),
Any pointers as to exactly how I would configure VPP to use the RDMA drivers?
What would I put in the vdev line in the VPP startup.conf?
Also, do you know if this is expected to work on Azure?
Thanks,
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to thi
Thanks for your reply and for looping in Damjan.
I have had a fair bit of success initializing DPDK directly on this same box on
the same adapters. Both of the following testpmd commands work for me and the
interfaces are attached to properly:
sudo ./testpmd -l 0-3 -n 4 --vdev='net_failsafe0,dev
blem using VPP in Azure with
DPDK failsafe interfaces #vpp #dpdk #azure
Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib
drivers which are required for my NICs on Azure. I noticed that something was
wrong when looking at the output of 'sudo vppctl show log'. I
activation problem using VPP in Azure with
DPDK failsafe interfaces #vpp #dpdk #azure
Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib
drivers which are required for my NICs on Azure. I noticed that something was
wrong when looking at the output of 'sudo vppctl show lo
Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib
drivers which are required for my NICs on Azure. I noticed that something was
wrong when looking at the output of 'sudo vppctl show log'. I then went back
and tried to get DPDK's testpmd application to work and from the ou
[Edited Message Follows]
As the subject indicates, I am having difficulty getting my VPP interfaces
activating properly. I am trying to use DPDK-enabled netvsc devices with VPP in
Ubuntu 18.04 in Azure.
I am trying to follow this guide:
https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interfac
Gbps
Ethernet address 00:0d:3a:f4:eb:8d
FailsafeEthernet
carrier down
Thanks!
--
Regards,
Balaji.
From: on behalf of Chris King
Date: Wednesday, January 22, 2020 at 11:01 AM
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev] interface activation problem using VPP in Azure
As the subject indicates, I am having difficulty getting my VPP interfaces
activating properly. I am trying to use DPDK-enabled netvsc devices with VPP in
Ubuntu 18.04 in Azure.
I am trying to follow this guide:
https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP
Here is some bas
24 matches
Mail list logo