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

Grimson

Keep your hands away from x86 CE build 2.4.0.r.20171008.0625 IPv4 is broken in it you can't even assign an IPv4 address to an interface with it.

Aerowinder

Hosed my setup as well. Please pull this update immediately.

denningsrogue

Mine too.

Sedorox

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_thumb

perlenbacher

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

Sedorox

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?

bimmerdriver

Same for AMD64. No LAN.

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

bimmerdriver

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.

vukomir

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

Raul Ramos

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

bimmerdriver

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

GMoyse

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

Go back

jgiannakas

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

dstacey147

Completely borked me as well, AMD-64 version

GMoyse

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

Sedorox

@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.

Grimson

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.

josemaX

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.

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?