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

    2.1.1-PRERELEASE Snapshots Available

    Scheduled Pinned Locked Moved 2.1.1 Snapshot Feedback and Problems - RETIRED
    27 Posts 13 Posters 24.9k 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
      ccb056
      last edited by

      Does it fix this issue:

      https://redmine.pfsense.org/issues/3321

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

        @ccb056:

        Does it fix this issue:

        https://redmine.pfsense.org/issues/3321

        I'm not sure anything has changed there, but it's worth testing and updating the ticket with your results.

        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
        • C
          ccb056
          last edited by

          @jimp:

          @ccb056:

          Does it fix this issue:

          https://redmine.pfsense.org/issues/3321

          I'm not sure anything has changed there, but it's worth testing and updating the ticket with your results.

          Just upgraded and ran a test.

          After rebooting the modem, my IPSEC tunnels now come back online.  Problem Solved!  :)

          1 Reply Last reply Reply Quote 0
          • W
            wladikz
            last edited by

            Hello,

            Anyone has chance to test ixgbe drivers? my 2 firewalls are in production and i can't use it for test :(

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              @jimp:

              Update URLs for use in firmware update settings:
              http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/.updaters/
              http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters/

              Hmmm… Not really working for me.

              Unable to check for updates.
              Could not contact custom update server.

              1 Reply Last reply Reply Quote 0
              • F
                fragged
                last edited by

                The snapshot server is down right now.

                1 Reply Last reply Reply Quote 0
                • W
                  wladikz
                  last edited by

                  @fragged:

                  The snapshot server is down right now.

                  Any Estimations when snapshot server will back online?

                  1 Reply Last reply Reply Quote 0
                  • C
                    Criggie
                    last edited by

                    @wladikz:

                    @fragged:

                    The snapshot server is down right now.

                    Any Estimations when snapshot server will back online?

                    The snapshots server is not responding to port 80 requests via IPv4, however it does reply to ping.

                    If I connect to the webserver by IPv6 it responds, but shows a set of files from 2011.

                    pfSense-2.0-RC1-4g-i386-nanobsd_vga.full.img.gz 2011-Mar-30 01:14:14    130.1M
                    pfSense-2.0-RC1-4g-i386-nanobsd_vga.upgrade.img.gz      2011-Mar-30 01:24:35    65.0M

                    I'm sure IPv6 isn't that lagged!

                    $ ping snapshots.pfsense.org
                    PING snapshots.pfsense.org (66.111.2.168) 56(84) bytes of data.
                    64 bytes from 66.111.2.168.static.nyinternet.net (66.111.2.168): icmp_seq=1 ttl=46 time=212 ms
                    64 bytes from 66.111.2.168.static.nyinternet.net (66.111.2.168): icmp_seq=2 ttl=46 time=214 ms
                    ^C
                    –- snapshots.pfsense.org ping statistics ---
                    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
                    rtt min/avg/max/mdev = 212.237/213.517/214.798/1.361 ms

                    $ ping6 snapshots.pfsense.org
                    PING snapshots.pfsense.org(2610:1c0:1:25::51) 56 data bytes
                    64 bytes from 2610:1c0:1:25::51: icmp_seq=1 ttl=46 time=217 ms
                    64 bytes from 2610:1c0:1:25::51: icmp_seq=2 ttl=46 time=217 ms
                    ^C
                    --- snapshots.pfsense.org ping statistics ---
                    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
                    rtt min/avg/max/mdev = 217.560/217.773/217.987/0.513 ms

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      Well yeah the URLs are 404, I cannot see the server being actually down.

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

                        Try again now.

                        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
                        • D
                          doktornotor Banned
                          last edited by

                          @jimp:

                          Try again now.

                          Thanks, works now.  8)

                          Still having issues with http://files.pfsense.org/lists/fullbogons-ipv4.txt and http://files.pfsense.org/lists/fullbogons-ipv6.txt though, getting a timeout.

                          1 Reply Last reply Reply Quote 0
                          • D
                            doktornotor Banned
                            last edited by

                            Well, I think it is still somehow broken…

                            
Current version: 2.1.1-PRERELEASE
  NanoBSD Size : 2g
       Built On: Fri Jan 17 15:24:41 EST 2014
    New version: Sun Jan 19 02:56:26 EST 2014

  Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_RELENG_2_1/.updaters/

                            This Jan 19 update for nanobsd-2g is just not there, just the version file. It is not here either. Looks like none of the Jan 19 nano-bsd snapshots for i386 got uploaded; amd64 looks OK.

                            1 Reply Last reply Reply Quote 0
                            • M
                              maverick_slo
                              last edited by

                              Yup it does not work…
                              I just did upgrade and I still have update available warning on frontpage...

                              1 Reply Last reply Reply Quote 0
                              • P
                                phil.davis
                                last edited by

                                There are 20-Jan snapshots there now. The snapshot builder will run again every 8 hours or so if it finds any changes in GitHub (and I think it runs every 24 hours or so even if nothing seems to have changed?). So there will be times when you update, then 5 minutes later a new snapshot build happens to finish and so it tells you there is another update available.

                                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                1 Reply Last reply Reply Quote 0
                                • M
                                  maverick_slo
                                  last edited by

                                  Nope, that was not the case.
                                  I upgraded to snapshot lets say "1005" and it reminded me that upgrade to version "1005" is available.
                                  I understand build process fairly good I would say :)

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    jasonlitka
                                    last edited by

                                    I just upgraded the backup of my CARP pair as a test because I've had more than a few issues with the 2.3.1 version of the igb driver.

                                    No issues on the first boot, but I'm disappointed to see that the newer igb driver (2.4.0) was included even though it still breaks altq.  I assumed that since no mention of that issue was included in the notes that the team had come up with a workaround.  Guess I was wrong.

                                    EDIT:  On the plus side though, I no longer have to disable MSI-X and I can now enable multiple queues for igb.  Looks like I'll have a decision to make when 2.1.1 drops. See below for a reply from jimp.

                                    I can break anything.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      mastahfr
                                      last edited by

                                      Any chance of the WAN DHCP client option to be put sometimes in the snapshots (Option 60, etc) ? I remember that a pull allowing to add option on dhcp client has been done a while ago on 2.2 (from memory).

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

                                        @Jason:

                                        I just upgraded the backup of my CARP pair as a test because I've had more than a few issues with the 2.3.1 version of the igb driver.

                                        No issues on the first boot, but I'm disappointed to see that the newer igb driver (2.4.0) was included even though it still breaks altq.  I assumed that since no mention of that issue was included in the notes that the team had come up with a workaround.  Guess I was wrong.

                                        EDIT:  On the plus side though, I no longer have to disable MSI-X and I can now enable multiple queues for igb.  Looks like I'll have a decision to make when 2.1.1 drops.

                                        That was unintentional, there was supposed to be a legacy TX option that was set to allow ALTQ to function on the new driver.

                                        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
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate
                                          last edited by

                                          @mastahfr:

                                          Any chance of the WAN DHCP client option to be put sometimes in the snapshots (Option 60, etc) ? I remember that a pull allowing to add option on dhcp client has been done a while ago on 2.2 (from memory).

                                          Unlikely, this is focusing on bug fixes and not features.

                                          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
                                          • J
                                            jasonlitka
                                            last edited by

                                            @jimp:

                                            @Jason:

                                            I just upgraded the backup of my CARP pair as a test because I've had more than a few issues with the 2.3.1 version of the igb driver.

                                            No issues on the first boot, but I'm disappointed to see that the newer igb driver (2.4.0) was included even though it still breaks altq.  I assumed that since no mention of that issue was included in the notes that the team had come up with a workaround.  Guess I was wrong.

                                            EDIT:  On the plus side though, I no longer have to disable MSI-X and I can now enable multiple queues for igb.  Looks like I'll have a decision to make when 2.1.1 drops.

                                            That was unintentional, there was supposed to be a legacy TX option that was set to allow ALTQ to function on the new driver.

                                            That sounds suspiciously like the patch I found and added to the ticket I have open with support.  Excellent, thanks.

                                            I can break anything.

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