If you choose the Intel 1000 adapter i ESXi, it will also show 1000Base-T as a connect option - because the adapter emulates physical hardware.
That's what I would expect. That's what hardware emulation should do.
VMXnet3 is a paravirtual adapter that does not emulate specific physical hardware, but is software only - and software speed limited only.
virtIO is paravirtualized as well. That is all, what I was saying. Above you mentioned paravirtualization as the only reason for not showing any connection speed. But this seems not to be the whole story.
Obviously virtIO signals the operating system that it is a 10Gb hardware, but vmxnet3 does not.
@tibere86 if you are still interested, had a similar issue with virtio in Proxmox and after several changes, reboots and iperfs later I found this combination of hardware offloading config offered the best performance System>Advanced>Networking
You can check whether it's running before deprovision by running service waagent status.
I deployed the image with both NICs DHCP and also left them DHCP in Azure. You may have to wait a few minutes after booting the VM to access the LAN NIC on either http or https whichever you have configured.
Although the Redmine Ticket seems to show this fixed back in 2.5.1, your problem seems eerily similar to this one: https://redmine.pfsense.org/issues/11483. Might be something weird going on with the way Hyper-V is presenting the virtual disks ???
I think I got it working! I couldn't access the Proxmox web interface anymore either no matter what I tried so I reinstalled Promox entirely. After reinstalling it still didn't work, so I tried again using another subnet in the network configuration during setup, and manually connecting my laptop to that subnet. After that I was able to access the Proxmox web interface again, so I continued following the steps like I did before. I was now able to connect to the pfSense interface too. I think the issue was with DHCP not working yet because the setup of pfSense in the web interface wasn't completed yet; the new subnet I used is the same subnet I used for pfSense (192.168.1.x), so that's probably why I was able to connect now.
For now I can't test any further until tomorrow because our switch is in my parents bedroom, and they're asleep now. I did test another laptop and that did immediately get an IP within the subnet, it also was able to connect to the internet.
If anyone's still interesting in this topic, here is the brief instruction:
Download pfsense ISO
Create a FreeBSD x64 VM in VirtualBox with PAE/NX, VMDK hard drive on IDE controller, disable audio and usb; attach the ISO to the VM
Boot the VM and install pfsense on the virtual hard drive
After installation completed, let the VM start rebooting and power it off
Create an OS bucket in OCI and upload the VMDK into the bucket
Switch to Compute/Instances/Custom Images and import the VMDK image from the bucket
From now you can create an instance from the custom image
@awebster yes, you are right. i have an etherchannel on the switch and nic teaming with IP hash on the esx. the configuration is not a problem; i followed guides for it.
Problem might be with the network card's driver in esxi, which although it is supported, it might have some problems.
Proxmox with a FreeBSD guest
Proxmox recommends using ntpd daemon in a FreeBSD client to maintain client real time synchronization. See pve.proxmox. com/wiki/FreeBSD_Guest_Notes and forum.proxmox. com/threads/time-drift-in-windows-7-guest.41268/#post-198848
Real time is set in the guest when it first starts. After which the guest clock drifts with the hosts processor crystal.
ntpd is the ntp daemon. See www.freebsd. org/cgi/man.cgi?query=ntpd&apropos=0&sektion=8&manpath=FreeBSD+12.2-stable&arch=default&format=html
Configured via /etc/ntp.conf
Command line interface ntpq See www.freebsd. org/cgi/man.cgi?query=ntpq&sektion=8&apropos=0&manpath=FreeBSD+12.2-RELEASE+and+Ports
11 minute hardware real time clock update can be enable by adding the line "SYNC_HWCLOCK=yes" to /etc/sysconfig/ntpdate
date gives time of day to 1 second resolution
Qemu guest agent
I think qemu can also sync time between the guest and Porxmox host.
Doing so is suggested github. com/aborche/qemu-guest-agent/blob/master/supported_command_reference.md
Other virtualization systems such as vmware have time synchronization between host and guest via the agent
Time synchronization should be done via only one system otherwise interaction between them decreases time system accuracy. Which mean if an agent and ntpd is used then there would need to be a way of disabling time synchronization via the agent. I'm not sure how to do this.
pfsense guest on Proxmox host
Given it is probably best to run ntp (chrony) on Proxmox then synch time in pfsense to the Proxmox host via ntpd over the LAN interface. Ideally I would like to do the following but not sure how to acheive that in pfsense
Enable ntpd on pfsense but not listening to clients on any interface. Selecting no interfaces in the GUI does the reverse.
Disable hardware real time clock update by pfsense. This is done every 11 minutes by chronyd on the Proxmox host. In pfsense the directory structure is different, so I can't goto to /etc/sysconfig/ntpdate and set SYNC_HWCLOCK=no
@julio12345 I will file a request for this to be changed to ALTQ kernel module instead of compiled in the kernel, then when ALTQ shaping is enabled the module could be simply loaded by pfsense and everything is good.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.