I'll quantify that better, in previous versions of 2.2.x, cant say about earlier versions beyond that.

It was on a 64bit capable device, but one thing from memory that stuck was it was only found less than 512Mb when its 2x4GB, 4GB being the theoretical max for 32bit systems unless something like whats hilighted in the link was occurring, ie falling back to an earlier instruction set on the intel cpu forced by either the cpu or freebsd handling of instructions sets at the OS, which could have explained the memory warning about having less than 512MB. https://en.wikipedia.org/wiki/RAM_limit#32_bit_addresses.2C_24_address_pins

That is it. Thanks! Summary: When configuring multi-wan PFSense 2.0 has a hidden rule to route local network connections that overrides the explicit default rule I configured. This hidden rule no longer exists in 2.1 and newer. A lan firewall rule needs to be configured for the local connection to use the default gateways instead of the gateway group.

Yeah - Often using DHCP and just telling pfsense to allocate a certain IP to a certain MAC is easiest. Its pretty easy to screw up static IP with centos.

The error was clear but  I was pretty sure that the upgrade was from x64 version.  The reset did the job ! Many thanks, Adrian

$ cat - | base64 -d Paste the encoded data and end with Ctrl-D (EOF).

Use full install, not nano!

simple search here on pfsense forums for xenserver would of pointed you to many threads with pointing out the checksum problems. There is even a Sticky in the VM section https://forum.pfsense.org/index.php?topic=88467.0

Someone would possible even have replied if this was posted to the proper forum. (Basically, the question has nothing to do with pfSense, that VLAN clicking takes about a minute.)

Yeah, either you did not install at all or you failed to remove the CD.

Guys, I figured out what was the problem. I had Device Polling enabled, and apparently it was causing a unexpected exception in the driver. Turned it off, now everything is ok. Also had to turn the hw.ixgbe.allow_unsupported_sfp, considering that I'm using a DA cable.

That's fixed in the next snapshot.

Ahh yes, certs. I'll never forget the time a senior dev asked me if I should encrypted my random token because if it's not encrypted, then someone else may be able to spoof it. Yes, someone going to guess my 256bit crypto-grade random token. Ignoring the fact that the encryption class he wanted to use was a company internal one that uses a static key and static IV. /derp

@cmb: @heper: @cmb i've experienced the same/very similar issue on a crappy dlink nic (sk0 driver) that worked fine before upgrading from 2.1.x –> 2.2.x  .... so in my case very similar situation with a non-intel nic. (haven't found the time to swap nics) currently i'm rebooting the firewall every morning at 5am and haven't received any reports like "please fix my internets" Could be the same solution for that, try disabling MSI and MSIX. In the Intel case, it appears the new driver wants to enable things that don't work on some small minority of cards. Could be a similar cause, though completely different root problem given different hardware and driver. Some rebranded cards, like the HP i350s, may have MSIX disabled in the firmware, but still identify as an Intel i350, which can cause issues. Nothing like saving $10 on a $140 card just to have driver issues or reduced performance because they've disabled or otherwise customized the card.

In my case both of my Netgear switches support it and have through several iterations of pfSense (2.0 to now). In fact one of the Netgear switches requires management via VLAN1 so I'm somewhat stuck there. In any case, I did try to have dnsmasq listen on all interfaces as well as specific VLAN interfaces when it was flapping yesterday. In both instances I saw the same flapping behavior. I am happy to note that since reverting the dnsmasq binary back to 2.2.2 I haven't seen a single signal 11 crash, it has stayed remarkably stable on both my primary and secondary firewall.

And the built in Linux Mint Image Burner program is also problem free and stupid simple.