It was just a warning, but patch was being applied correct. I've fixed it. Thanks!

How did I miss this? Thanks.

Thank you! As for the file, here it is (part of it, anyway): <interfaces><wan><enable><if>pppoe0</if>         <blockpriv><blockbogons><ipaddr>pppoe</ipaddr>         <spoofmac></spoofmac></blockbogons></blockpriv></enable></wan>     <lan><enable><if>vmx1</if>         <ipaddr>192.168.1.1</ipaddr>         <subnet>24</subnet>         <ipaddrv6>2001:67c:2158:a019::1</ipaddrv6>         <subnetv6>120</subnetv6>         <blockbogons><spoofmac><mtu>9000</mtu></spoofmac></blockbogons></enable></lan>     <opt1><if>vmx2</if>         <enable><spoofmac><mtu>9000</mtu></spoofmac></enable></opt1>     <opt2><if>vmx0</if>         <enable><ipaddr>dhcp</ipaddr>         <dhcphostname><alias-address><alias-subnet>32</alias-subnet>         <dhcprejectfrom><adv_dhcp_pt_timeout><adv_dhcp_pt_retry><adv_dhcp_pt_select_timeout><adv_dhcp_pt_reboot><adv_dhcp_pt_backoff_cutoff><adv_dhcp_pt_initial_interval><adv_dhcp_pt_values>SavedCfg</adv_dhcp_pt_values>         <adv_dhcp_send_options><adv_dhcp_request_options><adv_dhcp_required_options><adv_dhcp_option_modifiers><adv_dhcp_config_advanced><adv_dhcp_config_file_override><adv_dhcp_config_file_override_path><blockbogons><spoofmac></spoofmac></blockbogons></adv_dhcp_config_file_override_path></adv_dhcp_config_file_override></adv_dhcp_config_advanced></adv_dhcp_option_modifiers></adv_dhcp_required_options></adv_dhcp_request_options></adv_dhcp_send_options></adv_dhcp_pt_initial_interval></adv_dhcp_pt_backoff_cutoff></adv_dhcp_pt_reboot></adv_dhcp_pt_select_timeout></adv_dhcp_pt_retry></adv_dhcp_pt_timeout></dhcprejectfrom></alias-address></dhcphostname></enable></opt2>     <opt3><if>bridge0</if>         <enable><spoofmac><mtu>9000</mtu></spoofmac></enable></opt3>     <opt4><if>gif0</if>         <enable><blockbogons><spoofmac><mtu>1472</mtu></spoofmac></blockbogons></enable></opt4>     <opt5><if>vmx1_vlan4</if>         <enable><ipaddr>192.168.2.1</ipaddr>         <subnet>24</subnet>         <ipaddrv6>2001:67c:2158:a019::2:1</ipaddrv6>         <subnetv6>120</subnetv6>         <blockbogons><spoofmac><mtu>9000</mtu></spoofmac></blockbogons></enable></opt5></interfaces>

Also working here, thanks.

Fixed thanks for the report.

since you have the setup. Can you find issues with CP on multiple interface?

Just so i do not forget. At 256MB RAM APC is disabled. That was from my testing the best choice. Though it can speedup things if needed at cost of memory.

Ok did some tests. pfSense side: PC1 connected to APU with an AR9580 (3x3) PC2 side: AR9580 (3x3) on 2.4GHz 40MHz, Switching between MCS22 and MCS23 Switching between short GI on and off [  3] 167.0-168.0 sec  34.3 MBytes  288 Mbits/sec  0.043 ms    0/24451 (0%) [  3] 168.0-169.0 sec  33.5 MBytes  281 Mbits/sec  0.066 ms    0/23869 (0%) [  3] 169.0-170.0 sec  32.4 MBytes  271 Mbits/sec  0.046 ms    0/23076 (0%) [  3] 170.0-171.0 sec  33.9 MBytes  284 Mbits/sec  0.044 ms    0/24176 (0%) [  3] 171.0-172.0 sec  34.2 MBytes  287 Mbits/sec  0.041 ms    0/24402 (0%) [  3] 172.0-173.0 sec  34.5 MBytes  289 Mbits/sec  0.033 ms    0/24612 (0%) [  3] 173.0-174.0 sec  34.7 MBytes  291 Mbits/sec  0.051 ms    0/24763 (0%) [  3] 174.0-175.0 sec  32.5 MBytes  273 Mbits/sec  0.090 ms    0/23206 (0%) [  3] 175.0-176.0 sec  30.8 MBytes  258 Mbits/sec  0.051 ms    1/21953 (0.0046%) [  3] 176.0-177.0 sec  29.4 MBytes  247 Mbits/sec  0.044 ms    0/20995 (0%) [  3] 177.0-178.0 sec  31.1 MBytes  261 Mbits/sec  0.034 ms    0/22208 (0%) [  3] 178.0-179.0 sec  33.8 MBytes  283 Mbits/sec  0.173 ms    0/24107 (0%) [  3] 179.0-180.0 sec  32.9 MBytes  276 Mbits/sec  0.155 ms    0/23466 (0%) [  3] 180.0-181.0 sec  32.2 MBytes  270 Mbits/sec  0.034 ms    0/22993 (0%) [  3] 181.0-182.0 sec  30.6 MBytes  257 Mbits/sec  0.039 ms    0/21830 (0%) [  3] 182.0-183.0 sec  35.0 MBytes  294 Mbits/sec  0.134 ms    0/24979 (0%) [  3] 183.0-184.0 sec  32.0 MBytes  268 Mbits/sec  0.051 ms    0/22812 (0%) [  3] 184.0-185.0 sec  34.6 MBytes  290 Mbits/sec  0.036 ms    0/24650 (0%) [  3] 185.0-186.0 sec  34.7 MBytes  291 Mbits/sec  0.034 ms    0/24729 (0%) on 5GHz 40MHz, Switching between MCS22 and MCS23 Switching between short GI on and off [  3] 117.0-118.0 sec  34.2 MBytes  287 Mbits/sec  0.057 ms    0/24365 (0%) [  3] 118.0-119.0 sec  33.4 MBytes  280 Mbits/sec  0.055 ms    0/23841 (0%) [  3] 119.0-120.0 sec  31.6 MBytes  265 Mbits/sec  0.035 ms    0/22567 (0%) [  3] 120.0-121.0 sec  35.2 MBytes  296 Mbits/sec  0.055 ms    0/25139 (0%) [  3] 121.0-122.0 sec  32.7 MBytes  274 Mbits/sec  0.057 ms    0/23306 (0%) [  3] 122.0-123.0 sec  33.8 MBytes  283 Mbits/sec  0.060 ms    0/24087 (0%) [  3] 123.0-124.0 sec  30.3 MBytes  254 Mbits/sec  0.115 ms    0/21628 (0%) [  3] 124.0-125.0 sec  32.8 MBytes  275 Mbits/sec  0.031 ms    0/23420 (0%) [  3] 125.0-126.0 sec  31.8 MBytes  267 Mbits/sec  0.051 ms    0/22673 (0%) [  3] 126.0-127.0 sec  34.9 MBytes  293 Mbits/sec  0.039 ms    0/24888 (0%) [  3] 127.0-128.0 sec  30.4 MBytes  255 Mbits/sec  0.123 ms    0/21713 (0%) [  3] 128.0-129.0 sec  30.1 MBytes  253 Mbits/sec  0.040 ms    0/21477 (0%) [  3] 129.0-130.0 sec  31.7 MBytes  266 Mbits/sec  0.073 ms    0/22636 (0%) [  3] 130.0-131.0 sec  31.5 MBytes  264 Mbits/sec  0.044 ms    0/22457 (0%) [  3] 131.0-132.0 sec  31.3 MBytes  263 Mbits/sec  0.051 ms    0/22348 (0%) [  3] 132.0-133.0 sec  34.0 MBytes  285 Mbits/sec  0.048 ms    0/24243 (0%) [  3] 133.0-134.0 sec  33.7 MBytes  283 Mbits/sec  0.046 ms    0/24063 (0%) [  3] 134.0-135.0 sec  35.9 MBytes  301 Mbits/sec  0.043 ms    0/25585 (0%) [  3] 135.0-136.0 sec  35.9 MBytes  302 Mbits/sec  0.046 ms    0/25641 (0%) [  3] 136.0-137.0 sec  35.9 MBytes  302 Mbits/sec  0.041 ms    0/25642 (0%)

Well you have to understand how php-fpm works. It spawns processes and has provisioning for worst case. Since php in pfSense 'abuses' exit instead of returning from scripts the php-fpm helpers are closed after a request. Hence you end most of the time in respwaning a child php process when working from GUI. It will be solved moving forward but step-by-step.

2.2-ALPHA (i386) built on Mon Apr 14 15:07:07 CDT 2014 Site-to-site client is up and connected to main office. Working, thanks.

2.2-ALPHA (i386) built on Mon Apr 14 15:07:07 CDT 2014 FreeBSD 10.0-STABLE Tested on default port and on a specified port - both working, thanks.

Replying to myself…. I just saw that the AMD64 snapshots were updated and installed 'pfSense-memstick-2.2-DEVELOPMENT-amd64-20140414-0550'. No problems whatsoever, install went smooth. So whatever was the issue with the i386 snaphot, I really don't care anymore...  8) Richard

Sorry for hijacking this thread with the issue about boot messages. That actually turned out to be a "feature" in the way the new Log File Size option was implemented in Status: System logs: Settings I have fixed that up with https://github.com/pfsense/pfsense/pull/1088 So I will stop my thread hijack now  ;) Edit: Confirmed working fine now on 2.2-ALPHA (i386) built on Mon Apr 14 15:07:07 CDT 2014

I've reported it on git commit that included the @ https://github.com/pfsense/pfsense/commit/6e767d170cfb629ebf3e3d9d8677c15c741ae0d2#commitcomment-5975825

Yeah the new snapshots have not really used the latest fixes so far.

I've sent a fix for gitsync after manual git install https://github.com/pfsense/pfsense/pull/1072 https://redmine.pfsense.org/issues/3593