I did it removing samba36.conf from /usr/local/etc/pkg/repos

PFBlockerNG 2.1.1_2 Memory Errors

Thanks for the tip. As I stated before there was no changes made, it's fresh out of the box config. However I figured out the problem. The documentation for setting up in Hyper V states to use legacy network adaptor settings. I changed it back from legacy to regular and it jumped back up in speeds. Everything is running fine now.

Try again from ssh or the console using option 13 or "pfSense-upgrade -d" from a shell, and before you start, run "pkg clean"

Right, so I gave up on my install completely, I have gone for a complete reinstall, I'm still not seeing consistent internet access though. What I have done: Tried two different versions of pfsense as clean installs on esxi host, no back up from config xml, set them both up from new. Initial version that exhibited problems 2.3.1 i386 - problems described in this thread. New versions tried: 2.2.6 x64 2.3.2 x64 Both new (clean) versions exhibit the same gateway issues. Known differences from my initial setup, both the 2.2.6 and 2.3.2 x64 versions seem to have DNS resolver enabled by default, I was originally using dns forwarder. I don't recall if this was something I changed originally, it would have been years ago if I did. Not sure if/how this affects my problems now. I don't know if I should go back to an even older version to check if that would work, but from by best memory 2.2.6 was working for me in my initial setup. So this is currently leading me to think this a setup issue of my making. No surprises there…! :o So, in the new versions I have installed I am seeing WAN Interface gets an IP no problems. WAN_DHCP gateway fluctuates between online and offline quite frequently and regularly, and hence internet access is affected inline with this. My system log seems to point to something weird going on with WAN, namely it repeats this error over and over again. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: Info: starting on em1. Aug 7 19:44:50 php-fpm 29545 /rc.newwanipv6: rc.newwanipv6: No IPv6 address found for interface WAN [wan]. Can anyone explain what is going on here?? Is this a problem that I should fix?? My gateway logs are taken up with dpinger alerts that show the fluctuating internet access. See below. Aug 7 18:57:38 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8826us stddev 9725us loss 21% Aug 7 18:58:08 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1178329us stddev 6722886us loss 70% Aug 7 18:58:39 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7930us stddev 2873us loss 53% Aug 7 18:59:08 dpinger WAN_DHCP 176.26.X.X: Clear latency 7733us stddev 2029us loss 5% Aug 7 19:00:50 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7837us stddev 2265us loss 21% Aug 7 19:01:25 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1800145us stddev 8209140us loss 81% Aug 7 19:01:57 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7688us stddev 640us loss 50% Aug 7 19:02:27 dpinger WAN_DHCP 176.26.X.X: Clear latency 20475us stddev 44552us loss 7% Aug 7 19:13:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 9490us stddev 16525us loss 21% Aug 7 19:15:04 dpinger WAN_DHCP 176.26.X.X: Clear latency 83613us stddev 641992us loss 14% Aug 7 19:15:16 dpinger WAN_DHCP 176.26.X.X: Alarm latency 79299us stddev 671765us loss 21% Aug 7 19:15:55 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1556632us stddev 8193464us loss 75% Aug 7 19:16:20 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8150us stddev 2703us loss 60% Aug 7 19:16:54 dpinger WAN_DHCP 176.26.X.X: Clear latency 7864us stddev 1783us loss 5% Aug 7 19:18:58 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7711us stddev 403us loss 22% Aug 7 19:19:30 dpinger WAN_DHCP 176.26.X.X: Alarm latency 2216698us stddev 8411963us loss 73% Aug 7 19:20:06 dpinger WAN_DHCP 176.26.X.X: Alarm latency 0us stddev 0us loss 100% Aug 7 19:20:09 dpinger WAN_DHCP 176.26.X.X: Alarm latency 35555248us stddev 1018363us loss 94% Aug 7 19:20:46 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7738us stddev 641us loss 68% Aug 7 19:21:08 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1045933us stddev 6229170us loss 68% Aug 7 19:21:40 dpinger WAN_DHCP 176.26.X.X: Alarm latency 11149us stddev 7093us loss 92% Aug 7 19:22:00 dpinger WAN_DHCP 176.26.X.X: Alarm latency 11225886us stddev 19425589us loss 89% Aug 7 19:22:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 7700us stddev 460us loss 59% Aug 7 19:22:59 dpinger WAN_DHCP 176.26.X.X: Clear latency 7673us stddev 507us loss 6% Aug 7 19:25:38 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8322us stddev 2945us loss 22% Aug 7 19:26:09 dpinger WAN_DHCP 176.26.X.X: Alarm latency 1275590us stddev 6943279us loss 73% Aug 7 19:26:39 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8116us stddev 2273us loss 51% Aug 7 19:27:08 dpinger WAN_DHCP 176.26.X.X: Clear latency 8017us stddev 2098us loss 5% Aug 7 19:33:26 dpinger WAN_DHCP 176.26.X.X: Alarm latency 8084us stddev 2627us loss 22% Aug 7 19:34:49 dpinger WAN_DHCP 176.26.X.X: Clear latency 7715us stddev 681us loss 5% That's all for this update I think, I'm happy to provide anything that would be of use to help diagnose this. Note the above log snippets are from the 2.3.2 x64 version. I figure I might as well use the latest version that I would prefer to continue with going forwards - even if it currently isn't working! Any suggestions or discussion welcomed!  :) rancid

Looks like a failed upgrade for some reason in the OP as the info posted indicates the kernel is still RELENG_2_3_0, not RELENG_2_3_2. See if there is anything interesting in /cf/conf/upgrade_log.txt

It probably isn't locked up there. At that point it switches over to displaying the pfSense startup console messages, but for some reason it cannot. It's possible there is something amiss with the console or terminal settings on the box at that point. By far the fastest and easiest way to recover is to reinstall and restore your configuration. If you don't have a backup, use the "rescue config.xml" option in the installer – multiple times if it fails the first try -- and you'll be back up in a few minutes. If you haven't yet registered your firewall, do so and/or login to https://portal.pfsense.org/ and you should have a link to the factory firmware for that unit. If your support expired, just grab the ADI install image from pfsense.org for 2.3.2 and do the same.

Make sure it's outside your pfsense DHCP range so you don't end up with a IP conflict.

Right. Someone modified the package repository files to include samba36. There is no such repository in the standard installation.

Thank you very much :)

@heper Changing the slots was the first thing I did, but no luck. The bios has the last version, updating the driver, I don't know how to do it. I read some posts, but I didn't find a good answer, compiling within the kernel, I'm afraid to do it.

For 2.3.0 and 2.3.1 we have been releasing smaller "patch" updates with security fixes between regular releases. You might have seen them as 2.3.1_5 for example. They were smaller updates and did not have much if any negative impact. NanoBSD dual boots as you suggest but it's been a source of problems over the years and is being phased out. It was more trouble than it was worth. We will have the capability for things like ZFS snapshots on 2.4 which may prove to be more worthwhile.

I got it to work now I selected the parallel port in general setting and display 2x20

I have gained a lot of business ventures.

Hi, forget to reply that is working. Thank so much for the help

+1 for Old GUI Old GUI had much better Themes/Skins to choose from.  8)

https://forum.pfsense.org/index.php?topic=116223.0 The update to pkg will get you back on track.