Just upgraded via console (option 13) - since I use a SSD it updated very quickly  8)

Hi cmb, thanks for your description. I have decided to stay on the version now, though you mentioned it is same. BR WKN

VIPs and 1:1 NAT definitely all work fine. Packet capture, see if the traffic is coming into your WAN at all. I'm guessing it's not, and you're not seeing any ARP requests on those IPs, likely because of upstream ARP cache on your ISP's router.

It was indeed the NIC.  Or possibly the slot the NIC is in.  Unfortunately, the small board I have only has one x4 or larger slot, so I can't try it in another.  I got a replacement 2-port card that uses the x1 slot and that works fine boot after boot. Thanks again for the help.

I had this same issue when trying to upgrade from 2.3.1 to 2.3.2 last night. After the update on the first reboot I received the same error message. Tried another cloned HDD and SATA port and the issue remained. I reinstalled 2.3.1 on the exact same drive and restored my configuration to solve the issue. I will likely wait until the next update before trying again.

Missed the ps auwwx command and ended killing the process on both machines. I rebooted the secondary so I'll wait for it to happen and will get the ps output. Thanks. @cmb: What exactly is that pkg command that's running? ps auwwx|grep pkg

There was a server issue that was addressed earlier today that was causing slow downloads. It's been fine for a bit now.

Thanks Jorge, it would probably worked… :) But I solved it doing a SSH connection (using putty) and then picked option Update from console And it Worked now all is fine :)

Fixed.

I entered the gateway and reboot the server. Now I can go to the internet. Thank you very much phil.davis for your help and patient.

So ICMP (ping) works and DNS also works (port 53 UDP/TCP) but ordinary web-browsing does not work (TCP port 80 and 443). If there is traffic coming back from your browser actions that is being blocked then that means the states are somehow not being created (or not created right) when the initiating browser request packets go out through pfSense. Your description of all your settings sounds fine and should "just work". Do some packet capture to know exactly what packets are received on LAN, sent out WAN, and what comes back in to WAN. That will at least make you confident in what flows where and how far. Then when you are really stuck, post screenshots of settings, as there must be something odd that you have accidentally done.

Awesome, I will try that. Thank you!

I hate to dig up the thread just to say "me too" but this thread accurately describes my problem. My specific WAN card is an Intel PRO/1000 PT Dual Port Server Adapter - network adapter - 2 ports (EXPI9402PTBLK). Happy to provide whatever other information would be useful. Any updates on this issue? I am running pfSense 2.3.2. Would the same issue affect a Intel Pro/1000 PT Quad port D72468 39Y6137 NC364T 10N8556 EXPI9404PTG2L20 D57995?

Great, glad to hear it's working for you now  ;)

Hi, Same here, fetching various packages takes aeons… well, we ll wait then. All good things come to those etc... Edit: Done. Got there. Thanks