@phunni: If I downgrade, will the dansguardian package become available? It occurs to me that, since it's no longer supported, it might just not be available anymore. For the benefit of future readers, the packages for 2.2.* are still online for installs from 2.2.* systems. But they are no longer being maintained - e.g. if there are new versions of the underlying upstream code to fix security stuff or… then you won't get them.

Yeh, it depends on the situation. In the case you describe, you want to failover even though the "primary" WAN is actually up (it is slow for a known reason). In many cases the netadmin wants to know that the link is up (even if overloaded), and keep using it (because, for example, the backup link is even slower). So "it depends".

I disabled the Gateway Monitoring Daemon and it worked for me.

pent III, still running - wow ;)

@sporkme: Any idea why the 2.3 upgrade shoved me to i386?  This is not a modern box, but it was running amd64 and the one cause I could find googling did not seem to be my issue.  My backup config had this line, which I don't think forces me to a "non-standard" update URL (or is it?): That's the standard update URL, but for 32 bit. The 64 bit URL has amd64 in it. You manually set it to that at some point. It's no longer possible to intentionally or unintentionally switch architectures in >=2.3, so it won't happen again. But you should reinstall 2.3.1 64 bit and restore your config backup to get back to 64 bit. You can include the RRD data in the backup and it'll restore post-reinstall.

@divsys: It's not likely that any of your described attempts would create an xml file that the pfSense Restore system would understand. If you're trying to do a batch setup of DHCP static addresses, try: Manually create two or three static assignments in DHCP. Export the xml data using the pfSense Backup system, selecting only DHCP for Backup. Examine the xml file using a text editor and note the key data lines Cut and paste a few lines of data from your previous attempts to modify the file exported in 2) Import the modified file using the pfSense Restore facility and verify the DHCP changes occur as you expect. Repeat the modification with rest of your data. It's not that hard once you get an idea of what the file should look like internally. I tried this and the xml files were completely different. I ended up just manually entering them in. It took a fair amount of work but it will be worth it.

anyone can help ?

So how many esxi hosts do you have that you setup.. Are you going to run pfsense in carp mode?  Since you seem pretty worried about failover.  So your esxi box has 8 nics?  So take it your wan and lan networks are going to come in on the VM vswitch.  Is this a standard vswitch or a distributed switch? IF you only have 1 switch tied to a pair of interfaces that connect into your real network, then your going to have to use vlan tagging.

@naex: Thanks for the information, this was driving me crazy. I find this option a little strange since I can still apply system patches, edit the config file manually, and grant/remove that privilege to any user. There are multiple ways in to the system. Some of the Diagnostics menu options effectively give you all privilege - Edit File and Command Prompts come to mind. If someone has either of those then they can effectively do anything they like, editing config.xml to make a user with all privs, or execute any command they like. Similarly with system patches, a user with access to that can make whatever patch they like to the code and apply it. So that is another option that is effectively "all privs".

All fixed by adding DNS.

My CP page is kinda complex with mysql, css, bootstrap and a lot of php code. Setting maximum concurrent connections from 10 to 3 decreased cpu usage from 100 to 30%. Setting keepalive 2 gave an additionnal cpu drop, usage is now 7%-15%. Maybe setting keepalive to 2 is indeed a good solution for next release ? Regards, Ozy.

@pppfsense: ….. Difference in the fstab, it looks like now they are using labels to mount filesystems. .... Even when you skip a boat load of updates and upgrades, read all release info ;)

Thanks for all the replies. I'll give it a go.

Ah ok, that makes sense. Thanks for your time.

I just read your post and I have the same problem with this board: http://www.inctel.com.cn/product/detail/119 It has 4 LAN ports and the other I believe is the RJ45-DB9 port for console access. I installed pfsense as normal and 1 of the ports doesn't seem to work. I managed to connect through 3 LAN interfaces. 1 is configured as WAN and the other two are bridged to LAN - I followed this post https://forum.pfsense.org/index.php?topic=48947.45 all 3 work perfectly but the the 4th interface just doesn't come up, when I plug in the cable no lights come on. I ran some commands that I found on the forum: This is the output from pciconf -lv command. hostb0@pci0:0:0:0: class=0x060000 card=0x0f318086 chip=0x0f008086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register'     class      = bridge     subclass  = HOST-PCI vgapci0@pci0:0:2:0: class=0x030000 card=0x0f318086 chip=0x0f318086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series Graphics & Display'     class      = display     subclass  = VGA ahci0@pci0:0:19:0: class=0x010601 card=0x0f238086 chip=0x0f238086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series SATA AHCI Controller'     class      = mass storage     subclass  = SATA xhci0@pci0:0:20:0: class=0x0c0330 card=0x0f358086 chip=0x0f358086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series USB xHCI'     class      = serial bus     subclass  = USB none0@pci0:0:26:0: class=0x108000 card=0x0f188086 chip=0x0f188086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine'     class      = encrypt/decrypt hdac0@pci0:0:27:0: class=0x040300 card=0x0f048086 chip=0x0f048086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller'     class      = multimedia     subclass  = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x0f488086 chip=0x0f488086 rev=0x0e hdr=0x01     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series PCI Express Root Port 1'     class      = bridge     subclass  = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x0f4a8086 chip=0x0f4a8086 rev=0x0e hdr=0x01     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series PCI Express Root Port 2'     class      = bridge     subclass  = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x0f4c8086 chip=0x0f4c8086 rev=0x0e hdr=0x01     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series PCI Express Root Port 3'     class      = bridge     subclass  = PCI-PCI pcib4@pci0:0:28:3: class=0x060400 card=0x0f4e8086 chip=0x0f4e8086 rev=0x0e hdr=0x01     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series PCI Express Root Port 4'     class      = bridge     subclass  = PCI-PCI ehci0@pci0:0:29:0: class=0x0c0320 card=0x0f348086 chip=0x0f348086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series USB EHCI'     class      = serial bus     subclass  = USB isab0@pci0:0:31:0: class=0x060100 card=0x0f1c8086 chip=0x0f1c8086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor Z36xxx/Z37xxx Series Power Control Unit'     class      = bridge     subclass  = PCI-ISA none1@pci0:0:31:3: class=0x0c0500 card=0x0f128086 chip=0x0f128086 rev=0x0e hdr=0x00     vendor    = 'Intel Corporation'     device    = 'Atom Processor E3800 Series SMBus Controller'     class      = serial bus     subclass  = SMBus em0@pci0:1:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00     vendor    = 'Intel Corporation'     device    = '82583V Gigabit Network Connection'     class      = network     subclass  = ethernet em1@pci0:3:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00     vendor    = 'Intel Corporation'     device    = '82583V Gigabit Network Connection'     class      = network     subclass  = ethernet em2@pci0:4:0:0: class=0x020000 card=0x00008086 chip=0x150c8086 rev=0x00 hdr=0x00     vendor    = 'Intel Corporation'     device    = '82583V Gigabit Network Connection'     class      = network     subclass  = ethernet

@Knight: ….it so it took me quite a while to have a working system again...). What should take time : Ones its up, you create a backup 'disk' (CD, USB stick, etc) so when your principal media dies (SSH, Hard disk etc) you can reboot 'in a snap'. Ones in a while, when you're up and running, and you modify your pfSense config, store it also in a save place - better yet : write it to your backup media …. ;) You do can all this while "all is good and you have plenty of time". Btw : you should only do this if the "internet access" is important for you. I do understand you have other things to do (as we all)  ;D Now, the update day arrives. Now, you are ready ! Without even thinking, you hit that upgrade button. If things go downhill afterwards, well, you reboot from your backup media ..... and you're up. I assure you that you have a workable solution in 5 minutes, whatever the outcome will be : new version, or boot to old version. Added to that : something I don't do - but, which I should do : I'm running pfSense a a vanilla ancient Dell Office Desktop PC" (stripped down - I removed everything not needed on a firewall. What I should do : every time pfSense includes a new freeBSD kernel (meaning : new drivers etc) I install FIRST the original new FreeBSD OS. If that goes well, I'll have a pretty good that pfSense works also. Easier will be : run pfSense on pfSense certified machines .....

Well, that's a very obscure description of the problem, offering virtually no information to let anyone help you. I can tell you that when I upgraded from 2.2 to 2.3 I did encounter a problem with /var/log filling and causing the system to be unbootable, there were also a few corrupted files, not sure of the cause. I ended up reinstalling. Maybe this will help, if not try to provide more relevant information.

I finally found the option to make it work  :D. I configured the virtual IP as "Proxy Arp" and not "Ip Alias "