If I switch to VirtualBox's NAT networking it works. If I switch to a Windows host for VirtualBox it works. I've tested using a PCEngines APU2C2 box on one network and an APU2C4 on another network. Accessing the webGUI from a Win10 virtual machine that uses bridged networking.I can reproduce the issue consistently with the following: I've also been able to reproduce it on two completely separate networks, so it's not likely I'm seeing a localized problem. I can reproduce it consistently when I try to access the webGUI. My original post is below…Īfter updating to 2.4.0 I'm having a bit of trouble, but only with a very specific configuration. …for the the same driver + version I have: driver: e1000eĭisabling GRO fixed my issue instantly. I also found this Arch post that indicates newer kernels warn:ĭriver has suspect GRO implementation, TCP performance may be compromised. ![]() ![]() ![]() There's an old VirtualBox bug that deals with fixing similar GRO issues. On the host I could see packets with a payload size greater than the MTU and those packets were missing from the guest.īoth networks I was having issues with see very little LAN activity from VM guests, so it's not surprising I didn't notice the issue until the pfSense update surfaced it. After getting a decent multi-point packet capture set up, I tracked this down to generic receive offload (GRO) not working correctly on my host / guest.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |