Are you still seeing those warnings on the console? Or in the system logs?

It sounds like they might be an unexpected connection to the LAN. Like somehow it's linked to WAN maybe. If we can see what the actual warning was we might know more.

Steve

@nicesub said in Upgrade to 2.6 slashes throughput:

@bmeeks said in Upgrade to 2.6 slashes throughput:

Most likely you are being impacted by a known bug in FreeBSD 12.3 with Hyper-V. You will need to disable RSC (Receive Side Coalescing). Check the Virtualization sub-forum here on the Netgate forums. There is a huge thread about this and how to fix it on most installs.

Edit: here is a link to that thread: https://forum.netgate.com/topic/169884/after-upgrade-inter-v-lan-communication-is-very-slow-on-hyper-v.

Thank you fort that, I upgraded a copy of pfSense to 2.7 DEV and no issues were observed and I did not need to make any tweaks to Hyper-V. It appears that 2.6 has some issues with Hyper-V so I think that I will just skip it and stay with 2.5.2 until 2.7 is official.

Yep, 2.7 DEV fixed the problem in the FreeBSD virtual NIC driver for Hyper-V. The problem came in with FreeBSD used in pfSense 2.6.

@viragomann ohh good, im so stupid!

check >> service qemu-guest-agent status
qemu_guest_agent is running as pid 517.

thats was the solution now runs qemu guest agent finaly, thx for help :*

cYa BUSTER

@planetinse
Is it a thin provision virtual disk? As far as I know, FreeBSD doesn't like this.

@wolfram There is a problem with Hyper-V, see here. It will be fixed in the next release.

I figured out how to connect my computer to the pfsense vm. On windows server 2016 i went to network connections where i can see all my ethernet adapters. Then i selected in my case ethernet 3 where my computer is connected and the internal lan adapted and bridged the two adapters. In the bridged adapter i changed the ipv4 adress and i was connected to the router.

However now i am connected but still dont have internet and i am able to ping 8.8.8.8 but not google.com i get the error dns could not be resolved when trying to access internet in chrome.

@darcey Thank you for that info, I may look into proxmox and try it out, need to expand my toolbox a bit.

@basense
Can you check out if it's an DNS issue? Try to ping a public IP, e.g. 8.8.8.8.

If that fails as well, is pfSense able to access the internet?
If not, it might rather be an issue or wrong settings in VirtualBox.

@topogigio
I have no idea about the hw upgrade or VMware.

But always backup the config file to a secure place ...
Then it's easy to reinstall pfSense , to the current state - If s... hits the fan.

/Bingo

Well, since the test is with the host, and pfsense is not involved, why it is a pfsense issue.

The host connects to the internet through the pfSense VM.

@gertjan Ah, brilliant, that did the trick. Many thanks! :)

Actually solved using gpart instead of fdisk (this way I can see and manage the disks).

Thank you.

@gdzbedfz You should start with troubleshooting where the problem lies. Run a tcpdump on the interface you're sending the PFSense logs to. If you see Syslog, then you know the issue lies within the Elk configuration. If you don't see the logs running tcpdump, you have an issue blocking PfSense syslog from reaching Elk.

You will need to set the virtual network adapter(s) to trunk mode, see Set-VMNetworkAdapterVlan

If you have more than one vmnetworkadapter you can filter by macaddress, for example:

Get-VMNetworkAdapter -VMName "vmname" | Where-Object {$_.MacAddress -eq "00155D010203"} | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "2-9" -NativeVlanId 0

@stephenw10 Oh wow. I misunderstood. Assumed this was the NIC detaching because the whole bus shouldn't be possible, as you said.

I need to dig into the Hyper-V side of this to understand that. That's absolutely baffling behavior. But hey, Microsoft...