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

    Don't upgrade to x86 CE build 2.4.0.r.20171008.0625

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    68 Posts 27 Posters 15.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.
    • denningsrogueD
      denningsrogue
      last edited by

      Mine too.

      1 Reply Last reply Reply Quote 0
      • S
        Sedorox
        last edited by

        I'm seeing it too. Testing in a VM at the moment, so upgrading from yesterday's build (which was a fresh install).

        pfsense.png
        pfsense.png_thumb

        1 Reply Last reply Reply Quote 0
        • P
          perlenbacher
          last edited by

          The latest 2.4.0-RC x64 release (as of 3 hours ago) bust my PPPOE connection. No IP was assigned…
          Rolled back to 2.4.0.r.20171003.1349 (when I had last made a memstick) and all was ok again.

          PS. I upgraded, in place, from the WebUI

          1 Reply Last reply Reply Quote 0
          • S
            Sedorox
            last edited by

            I just did a fresh install with today's build, and everything seems to be working.
            So it looks like it might be an issue during an upgrade?

            1 Reply Last reply Reply Quote 0
            • B
              bimmerdriver
              last edited by

              Same for AMD64. No LAN.

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

                Hmm, like no static IP on the LAN interface?

                I just upgraded a box here and am not seeing that.

                Logging is working as the files were already present. There may be an issue on fresh installs from that snap.

                What exactly are you seeing? Anything logged?

                Steve

                1 Reply Last reply Reply Quote 0
                • B
                  bimmerdriver
                  last edited by

                  All I can see is the console. hn0 -> nothing.

                  I can't access the webgui because the pc can't get an ip address.

                  Tried resetting to factory defaults. That did not work, going to reinstall from scratch using the previous version.

                  1 Reply Last reply Reply Quote 0
                  • V
                    vukomir
                    last edited by

                    Hi,

                    DHCP is not working for me, I get the following error on boot

                    Can't attach interface lagg0_vlan15 to bpf device /dev/bpf0: Invalid argument

                    1 Reply Last reply Reply Quote 0
                    • Raul RamosR
                      Raul Ramos
                      last edited by

                      Update a remote pFsense and no access.

                      If someone have a fast fix please put here.

                      Tomorrow i have to go onsite and fix or reinstall the firewall.

                      Thanks

                      pfSense:
                      ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                      Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                      NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                      1 Reply Last reply Reply Quote 0
                      • B
                        bimmerdriver
                        last edited by

                        Reinstalled from the previous release (yesterday). It's back up.

                        1 Reply Last reply Reply Quote 0
                        • G
                          GMoyse
                          last edited by

                          For me, DHCPd and DNSmask service don't start.

                          Go back

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

                            Ditto. Updated from yesterday’s build and the router is no longer accessible remotely and network is down.

                            1 Reply Last reply Reply Quote 0
                            • D
                              dstacey147
                              last edited by

                              Completely borked me as well, AMD-64 version

                              1 Reply Last reply Reply Quote 0
                              • G
                                GMoyse
                                last edited by

                                I see also, at pfsense boot : block on "db>  " a power off, and after, it's ok for me

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Sedorox
                                  last edited by

                                  @stephenw10:

                                  Hmm, like no static IP on the LAN interface?

                                  I just upgraded a box here and am not seeing that.

                                  Logging is working as the files were already present. There may be an issue on fresh installs from that snap.

                                  What exactly are you seeing? Anything logged?

                                  Steve

                                  For me, when it came back up, LAN and WAN both had the interfaces listed correct, but no IPs listed. Reboot did not help.
                                  I did update via the webgui. Mine is also AMD64.

                                  I blew it away (testing VM), and did a fresh install of today's build, and so far everything seems good.

                                  1 Reply Last reply Reply Quote 0
                                  • GrimsonG
                                    Grimson Banned
                                    last edited by

                                    I'll try to give as much information as possible:

                                    Box before the upgrade attempt:
                                    Mini-ITX System based on an ASUS N3150-C with an Intel 82571EB 4 port NIC (em driver) and 64GB SSD.
                                    Onboard Realtek Ethernet Controller disabled in BIOS.
                                    It was running the last 2.4RC build from yesterday (07.10.2017) using ZFS as filesystem.
                                    Note: I was originally running 2.4.1 and reverted back to 2.4.0, when it moved to FreeBSD 11.1, recovering the config during the install.

                                    Installed Packages iperf (server not active), bandwidthd and cron.

                                    em0 configured as LAN with a static IPv4 on 192.168.2.1/24 and the IPv6 from HE.net tunnel.
                                    em1 confgured as OPT with a static IPv4 on 192.168.1.1/24 to access the WebUI of the DSL modem.
                                    WAN configured as PPPoE on em1, get's a dynamic IPv4 address.

                                    I started the upgrade using the WebUI, like always, it downloaded the packages and rebootet. Booting took quite a bit longer than usual, after it was finished neither the box nor the WAN was reachable.

                                    I attached a Monitor to the box and normal output should be like this:

                                    
                                    WAN (wan) -> pppoe0 -> v4/PPPoE: x.x.x.x
                                    Lan (lan) -> em0 -> v4: 192.168.2.1/24
                                                                    v6: x:x:x:x::x/64
                                    MODEM_ACCESS (opt1) -> em1 -> v4: 192.168.1.2/24
                                    and the HE.NET Tunnel
                                    
                                    

                                    instead it was this:

                                    
                                    WAN (wan) -> pppoe0 -> 
                                    Lan (lan) -> em0 -> 
                                                                    v6: x:x:x:x::x/64
                                    MODEM_ACCESS (opt1) -> em1 -> 
                                    and the HE.NET Tunnel
                                    
                                    

                                    I attached a keyboard and used option 2 to give LAN a new IPv4 address, the process run without displaying any errors but LAN was still without an IPv4 address afterwards. I rebooted for good measure but that didn't change a thing.
                                    After that I used option 4 to reset pfSense to factory defaults, this run through without an error and after the reboot this was displayed for the interfaces:

                                    
                                    WAN (wan) -> em0 -> 
                                    Lan (lan) -> em1 -> 
                                    
                                    

                                    I tried to reassign the interfaces and manually add an IPv4 address to the LAN, but it still didn't work. So I reinstalled an older build and go the box working again.

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

                                      Same here, BUT if helps to solve i had several IP alias in LAN and they were asigned to LAN and worked to connect.

                                      Then deleted them and unable to configure the IP.

                                      Also in WAN i have static IP and even i configure it, it is not used (in console, IP (WAN and LAN) are blank (in Web cfg (when accessed with one of those aliases) appeared as configured)

                                      Also when configuring in console appears an error about "renaming interfaces", i'll try to take a photo.

                                      Downloading 20171006-1536 to reinstall if no solution given.

                                      1 Reply Last reply Reply Quote 0
                                      • GrimsonG
                                        Grimson Banned
                                        last edited by

                                        @Sedorox:

                                        I blew it away (testing VM), and did a fresh install of today's build, and so far everything seems good.

                                        Did you restore you previous config or did you reconfigure by hand?

                                        Are you using the traffic shaper, and if yes do the queues show up in Status -> Queues?

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

                                          Sorry, the error about renaming was when booting, not when configuring IP, attached 2 pictures, one with the renaming error when booting and other after configure LAN IP in console and IPs of interfaces are blank.

                                          booting.jpg
                                          booting.jpg_thumb
                                          ConfiguringLANIP.jpg
                                          ConfiguringLANIP.jpg_thumb

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            Sedorox
                                            last edited by

                                            @Grimson:

                                            @Sedorox:

                                            I blew it away (testing VM), and did a fresh install of today's build, and so far everything seems good.

                                            Did you restore you previous config or did you reconfigure by hand?

                                            Are you using the traffic shaper, and if yes do the queues show up in Status -> Queues?

                                            No, I did everything from scratch again (only installed about 9:00pm EDT). I didn't have the shaper setup, I did have a few packages (ACME, FRR, Snort, PFBlockerNG), and I believe I went through the real basic setup of Snort and PFBlockerNG. But other than that it was pretty much stock/not configured.

                                            I still have the ISOs from yesterday and I can do some testing to see if I can reproduce it and grab some more screen shots.

                                            Edit: So far I reinstalled with yesterday's build, but it isn't finding anything yet for an update. I'll leave it be for a bit and see what happens.

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