Gateway config ignored after update

  • Hi everyone. I would like to post my experience after updating pfSense 2.0 Beta. Hopefully this will be useful for developers.

    The update was done using the auto-updater and the system was running smoothly for 40 days. The original system's build date was around August 10th, 2010 (maybe some days newer).
    The internet interface's IP was statically configured (no DHCP), needing the appropriate IP, netmask, gateway and broadcast IPs.

    After the update (which was done yesterday, Oct 7 2010) the system's build date is:

    2.0-BETA4  (i386)
    built on Thu Oct 7 17:26:20 EDT 2010
    FreeBSD 8.1-RELEASE-p1

    At this point, the pfSense box didn't have internet access. The problem was it lost it's gateway IP configuration. The only changed needed to get it working was Interfaces->WAN->Gateway->"add a new one", creating the appropriate gateway and then selecting it in the drop down menu.

    I can see in another, older, pfSense box I have, that this parameter is also set to "none", despite being statically configured and working correctly.
    I will try to update this older pfSense box next week, in a more controlled environment and confirm this behavior.
    If anyone wants me to try anything before I update the box, please tell me so.

    Hope this helps.
    Thanks for this amazing software!

  • Rebel Alliance Developer Netgate

    After the recent gateway code updates, you need to edit and save each gateway entry.

    In some cases with automatic/dynamic gateways you be better off deleting them and letting the system recreate them.

Log in to reply