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

    I can not from 2.1.5 to 2.2.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    26 Posts 6 Posters 3.8k 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.
    • Y
      yon
      last edited by

      my bois have no this option. where find it ?

      IMG_20150302_161903.jpg
      IMG_20150302_161903.jpg_thumb
      IMG_20150302_161703_mh1425284487689.jpg
      IMG_20150302_161703_mh1425284487689.jpg_thumb

      If you are interested in free peering for clearnet and dn42,contact me !

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

        I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

        Steve

        1 Reply Last reply Reply Quote 0
        • K
          kejianshi
          last edited by

          To turn on smart, you will have to look inside each one of those menus there and find smart.  Turn it on and save.  As for the run(4) issue, if thats a freebsd issue, you may be just screwed.

          1 Reply Last reply Reply Quote 0
          • Y
            yon
            last edited by

            @kejianshi:

            To turn on smart, you will have to look inside each one of those menus there and find smart.  Turn it on and save.  As for the run(4) issue, if thats a freebsd issue, you may be just screwed.

            i have no find the smart option.

            If you are interested in free peering for clearnet and dn42,contact me !

            1 Reply Last reply Reply Quote 0
            • Y
              yon
              last edited by

              @stephenw10:

              The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

              I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

              Steve

              I will try remove interface in pf2.1.5

              If you are interested in free peering for clearnet and dn42,contact me !

              1 Reply Last reply Reply Quote 0
              • Y
                yon
                last edited by

                @stephenw10:

                The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

                I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

                Steve

                your are right.  it is becasue not using  interface has no remove.  just upgrad to PF2.2.1

                but the pf2.2.x  ipv6 not normal work. just ipv6 gateway show online, but LAN ipv6 can not go to internet.  The DHCPV6 not normal work.

                ![pf2.2.1 ipv6 - Status Dashboard.png](/public/imported_attachments/1/pf2.2.1 ipv6 - Status Dashboard.png)
                ![pf2.2.1 ipv6 - Status Dashboard.png_thumb](/public/imported_attachments/1/pf2.2.1 ipv6 - Status Dashboard.png_thumb)

                If you are interested in free peering for clearnet and dn42,contact me !

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  You will need to be more specific. IPv6 is not broken as far as I know in 2.2.1 snaps.

                  Steve

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

                    @stephenw10:

                    I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

                    Just FYI, run(4) should be fixed in the next snapshot:
                    https://redmine.pfsense.org/issues/4117#change-17648

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Yep, I tested it this morning and it worked fine.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • K
                        kejianshi
                        last edited by

                        run(away)

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