Recently I noticed there are a lot of VM starting using vmxnet3. As example, Palo Alto VM (firewall), and F5 Big-IP LTM VE.
I've been trying to setup my own Palo Alto Firewall lab using my favorite hypervisor which was VirtualBox. Unfortunately, certain network interfaces just don't work.
I've spent many days troubleshooting this issue, capturing many tcpdump packets and observed similar pattern.
It seems like there are communication issue on Layer 1 and layer 2.
2 devices (Linux and Palo Alto VM) connected with the same network adapter type (internal) and within the same network range can't ping each other.
If I use similar network setting on 2 Linux VM, I don't have this issue at all.
Apparently, I'm not alone. Found similar problem posted on the following F5 forum.
Reference: https://devcentral.f5.com/questions/ltm ... virtualboxI have been using a Big-IP LTM 10.1.0 VE Virtual Edition for several months under Virtual Box it worked great.
...
Please note, I don't want to switch to VMware even if it is free.
...
LTM VE 11.2.0 now requires VMXNET3 network adapter, which is not available in VirtualBox - this is a real show stopper for me.
Dear VirtualBox developers and contributors,
If you read this message, I would really appreciate if you can consider this request. I'm happy with VirtualBox and don't have any plan to move to VMWare yet at the moment.
Thank you for time and great job with VirtualBox. Keep it up