Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Gateway config ignored after update

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    2 Posts 2 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      chronos00
      last edited by

      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!

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        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.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.