PfSense 2.2 not passing traffic, but ping does get through
I had the same problem as described in op with Xen and pfSense. The first sticky post in this forum describes the problem and a workaround. In the end, I had to turn off just the checksum offload on my private network using ethtool.
IMPORTANT: Xen/KVM networking will not work on 2.2 using default hypervisor settings!
I had this same problem with ProxmoVE. pfSense installed as KVM with "VirtIO" emulator which is default for KVM. WAN bride with eth0 and go out. Local bridge for LAN side of pfSense.
Installed Windows & Ubuntu with VirtIO Driver. When Windows VM was set to go through pfSense I could ping but no internet no TCP/UDP connections at all. Same scenario. After bashing my head on the wall for whole sleepless night trying to resolve this. Finally I decided to setup XenServer instead of Proxmox which runs Xen hypervisor.
Implemented the same setup in XenServer with all default settings. Windows was installed with default Realtek NIC driver. Alverything worked perfectly fine.
When I installed xe-tools which turned Realtek NIC to "Xen Paravirtualized driver" it stopped work with same results as above. When I uninstalled xe-tools it worked again.
From this what I can see is Paravirtualzied drives are causing this issue in both setup. VirtIO in KVM & PV in Xen. With other NIC emulators like e1000 or Realtek it works fine.
I haven't found a solution to get this working with para drivers which will improve the performance.
I wanted to post here to first say a deep and heartfelt THANK YOU for posting this as I spent days trying to work out why all my Linux boxes didn't have internet but my Mac's and Windows machines did. After trying loads of tests and variations I found your thread which was the final clue :)
For the record (and to help people searching with similar issues) I am running pfsense on a Virtualised installation on a QNAP server, it worked great apart from Linux VM's not having internet and the QNAP itself (if sharing a virtualised switch) also lacking internet. If you route the QNAP via a none virtualised ethernet socket then you aren't affected.
Ping worked just fine. When I swapped to the Realtek ethernet emulator everything started working again.
@Bullz3y3 Your advice on switching to e1000 is as good on the latest version of Proxmox and the latest version of pfsense as it was in 2015, this was driving me insane, thank you!
@bullz3y3 I can definitely confirm your suggestion to change the network adapter to e1000 for proxmox. Thanks!
I am having no problems putting traffic through modern pfSense installs on a modern proxmox VE installation using the virtio drivers.
I, too, suffered from the issue with XenServer but there were fixes (using HV drivers or disabling the checksums in the VM).
@derelict could you please run iperf from pfsense to the host and copy&paste the output here? And maybe from a linux vm to the host?
Full speed, but I only have 350/30 here.
The problems on XenServer resulted in almost no throughput when using TCP, like single-digit kilobits-per-second. If you are seeing just lower-than-expected throughput then it's a completely separate issue and you should start a different thread.
Don't performance-test by running iperf on the firewall. Test through the firewall.
@derelict thx for your replay, i already stared a thread "https://forum.netgate.com/topic/138988/pfsense-on-kvm-slow-network-speed" but nobody replayed, that's why i asked here. ^^
i am more interested in throughput between two local subnets through the firewall than between local net and internet.
1.6 Gbit/sec between two VMs in each direction. Single-stream TCP.
iperf3 hosts are on 1302 and 1201.
Sorry for adding to an old post but just wanted to add another +1 to this in case someone else is struggling.
Anything ICMP related seemed to work fine (ping, trace route etc) but no web, ssh, telnet, etc.
under System / Advanced / Networking; disabled Hardware Checksum Offloading, saved the setting and everything seems to have sprung into life again.
vm host: ubuntu 16.04.6
using KVM and virtio NICs
here same situation... really frustrating..
I have tried any kind of network card in proxmox.. can't reach internet from the virtual lan.
If start all lan virtual machines and I reboot the pfsense.. all works.. if i restart a lan VM with pfesense running, no internet connection...
My entire lab is in proxmox. Works absolutely fine.
It is key to disable the checksum offloads or you won't be able to pass traffic reliable becasue the checksums will fail due to the way the networking stack in proxmox/kvm works. This is not an uncommon requirement in other hypervisors either.
But it is the first setting that i have made on pfsense after installation..
I have tried to change the network type..and nothing.. and the fact is that this error replicate in any other proxmox host installation....
I do not have such problems. Those settings should only be needed on guests that actually pass traffic through them.
I have never needed to do anything special on guests that simply transmit and receive traffic on one interface (Linux, Windows, FreeBSD, etc).
No idea about e1000. I always use virtio.
I do know that these checksum issues were completely absent in XenServer when you disabled PV NICs but you had to tweak the VM interfaces to not use checksums if you used PV NICs so what you have might behave completely different from what I am doing.
e1000 is only one of the test changing ethernet card type.
I was using virtio first.. same problem
if I apply the reboot with re-run startup sequences all works newly in the lan...
@Derelict installed now windows 10, and don't have the network problem that affect linux vps...
@bullz3y3 Have same issue in 2021, and fixed by changing the Network Type from Virtio to e1000 also. Your finding in 2015 is still helping others. Thanks.
My case is having a PCI Passthrough WAN, and 2 bridge LAN, hosted on KVM on debian 10