@jimp: @diablo266: Sorry for bringing back an old thread but i've ordered a 6501-70 with slc msata ssd. Are the changes required for booting from msata listed here: http://doc.pfsense.org/index.php/Boot_Troubleshooting#NanoBSD_on_Newer_Hardware persistent across updates? This is going to be installed remotely and i'd like to limit any possible complications. If an update is capable of stopping the device from booting I think I will go with a USB drive install over msata (will be nanobsd regardless). Thanks! Yes, changes to loader.conf.local are preserved across updates. Excellent, thank for clearing that up jimp!

We have seen a similar thing happen on upgrade before but we could never reproduce it even with the same customer configuration. The IP is taken from the 'interface' selection on the IPsec Phase 1 settings. On 2.0.x, the vip "interface" names were different (vip1, vip2, etc where the number is the VHID), and on 2.1 the names changed to intX_vipY where the VIP interface (e.g. em0, fxp1, vr2, etc) is a part of the name. The code to rename the interfaces in the config.xml data during the upgrade must not have properly translated the old names to the new names.

About problem 2: I encountered the same issue after upgrading 2.0.2 to 2.1-RELEASE. The fix you suggested (editing captiveportal.inc) worked okay. This issue did not occur on fresh installs of 2.1 or when upgrading 2.1 BETA/RC to 2.1-RELEASE, only for 2.0 to 2.1.

Do you have multiwan? Ipv6 enabled? This can cause your symptoms: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference Also have a look through the suggestions in this thread: http://forum.pfsense.org/index.php/topic,68164.0.html Steve

Unfortunately that product id covers a number of revisions and not all are supported. The 8111e and earlier are supported. You could try this: https://forum.pfsense.org/index.php/topic,65355.msg365028.html#msg365028 Steve

Awesome, I'm glad that proved to be useful :-) Happy bridging

I'll check this weekend when I work on the box. Been busy with work. I'm going to completely hook the box directly to my cable modem, then to my network"s wireless router and see what happens.

Thanks biggsy. I've read through that first document. I'll try the second one. I just wasn't sure if packets would go through the pfSense VM first before going to the Server VM (being that they are on the same vSwitch).

@jimp: The versions must match for DHCP failover to work. Upgrade the primary and it will go back to normal. But now also the primary is in recover/unknown-state and not assigns me the lease…. ?!?!?!?!?!?

Problem solved. I tested the 64bit version of the nanobsd 4g and now it is working. The only thing what sucks is tha tthe igmpproxy is not working correct. IPTV is not working. After a few seconds of stream over udp it should change to multicast stream, but nothing happens. With my alix and 2.0.3 everything is ok. kdk EDIT: at the moment i think the Problem is a routing issue. http://forum.pfsense.org/index.php/topic,66776.30.html

Are you still trying to use a USB-Serial converter? I don't see it listed. Steve

Not sure if you could do it via the upgrade process. The config file would be incompatible but I know you have a 1.2.3 file backed up.  ;) One way that would definitely work would be to remove the CF card and write the 1.2.3 image to it. I couldn't recommend you do that though. There have been security updates since 1.2.3 which you would not then have. Steve

yes, it works on the pfsense box i have running 1.2.3 but with the identical settings per my screenshots on v2 pfsense it doesn't (tried 2 lots of hardware) and i cant work out why

I dont know why, but it is now working after resetting and doing the same thing for like the 20th time.

@stephenw10: @mevans336: If I set hw.igb.enable_msix="0" in the loader.conf, will that persist across an upgrade? No but if you add it to loader.conf.local it will. Steve I have an identical server here at home minus one thing, a 2-port PCI-Express Intel NIC. I performed an upgrade on it and it went flawlessly. I think the Intel NIC in our co-lo firewalls are to blame. To test, I changed the server here at home from AHCI to IDE mode and it failed at the mountroot> prompt much later in the boot process, not as in my screenshot above, immediately after initializing the processors. I'm going to give the hw.igb.enable_msix="0" option a shot when I return to the datacenter in a few weeks. I'll report back.

Bump Wondering the same thing PF Sense 2.1 Keeps rebooting every hour or so.

Yes i do! But i can't see BL items that appeared in Target Rules List (click here) (in Common ACL or Gropus ACL). Thank you jimp!

^up multicast is going to be there, and lets not forget all the dhcp traffic, and arp traffic.. Think of your blinking light as – hey its connected and there is traffic.