PfSense 2.2 not passing traffic, but ping does get through

[qctech]

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.

pfsense: 2.4.4-RELEASE-p3
vm host: ubuntu 16.04.6
using KVM and virtio NICs

[openaspace]

@Bullz3y3 Hello..
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...

ooh s***!!!

[Derelict]

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.

[openaspace]

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....

[Derelict]

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).

[openaspace]

[Derelict]

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.

[openaspace]

e1000 is only one of the test changing ethernet card type.
I was using virtio first.. same problem

[openaspace]

if I apply the reboot with re-run startup sequences all works newly in the lan...
really strange

[openaspace]

@Derelict installed now windows 10, and don't have the network problem that affect linux vps...

[marcelleung]

@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