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

That specific case is harmless. We'll have a fix in 2.4.4-p1 for it.

Nevermind. Figured it out. I had IPV6 disabled.... once i renabled it, the update worked.

Hmm, it would normally show it has found the config just after the 'launching external config loader' line.

It also gives you an alert on the dashboard but I think only if you restore the config after the initial boot.

Steve

@wordo said in CVE-2018-6922 (FreeBSD crash due to TCP fragment reassembly vulnerability):

Thanks! But running HAProxy or OpenVPN on 443/TCP for hotspot compatibility would be affected?
I also don't see such a high risk, but was wondering what the reason behind not pushing a new kernel to 2.4.3 release.

Because the next release is 2.4.4. Users running 2.4.3 should update to that when it is available.

https://forum.netgate.com/topic/135395/where-to-download-old-versions

@stephenw10
thanks a lot, i boot it from another Computer with 2 Network_card, had Access to web_GUI. and changed what you said: - System > Advanced >Serial console enabled,
- System > Advanced >Miscellaneous: moved /var and /tmp to RAM
and now it works in my Hardware as well.

@stephenw10 I couldn't find the emoticon of Elon Musk holding a spliff.

@derelict Ok, so 2.4.4 definitely got me the driver. Separately, moving from my old to new was a bit clunky.

Upgraded my old from 2.4.3 to 2.4.4, backed up config. Uploaded new config to my new box, prompted me to adjust the interfaces then apply. Hit apply, it complains about the browser not supporting cookies.

I tried being smart and manually adding "cookie_test" that it was looking for but nothing. I'd enter in the correct credentials, it'd refresh but not redirect. Eventually I think it rebooted, and I couldn't access it. I then determined it applied my config but not the interfaces. I set the interfaces to the correct ones, but still not accessible. When I reset webConfigurator password, then everything kicked in. I think it had something to do with backing up on an HTTPS to an HTTP. My old box was using HTTPS on 4443. Best guess anyway.

@jimp Cool, thanks. I'll give it a shot over the weekend, hopefully it'll go ok :).

Thanks again!

-- Leif

A reinstall is probably easiest.

If your WAN is DHCP you might be able to get away with running dhclient em0 where em0 is the actual WAN interface. If it's static or something else it could be done but it would be more difficult.

When you reinstall, choose the option to recover config.xml and it will pull your current settings back in.

So you are routing the /30 to pfSense, from the the edge router?

And then routing it to the Mikrotik?

None of that is Layer 2.

We are going to need a full diagram here with all the interfaces on each device and the IPs shown. It's not at all clear what you have here.

Also a clear definition of what you trying to achieve.

Steve

That's the only file you should need.

If you had any packages installed it will try to re-install those at the first boot after uploading the config. If you don't have a valid WAN at that point it cannot do that.

How exactly did it 'brick'? Do you still have access to the console?

Steve

For refernce you need to use a FAT32 formatted USB stick for PFI or ECL. Since the installer image is UFS that generally means using a separate USB stick to hold the config.

Packages should be re-installed automatically when you restore the config. If you didn't have a valid WAN interface at that point that process would fail. The package config is retained though.

Steve

@derelict Host a web server, mail server, etc.

thank you i even searched for it, thanks man !

I just installed the latest 2.4.4 Development FreeBSD 11.2-RELEASE-p2 and its working with Apollo lake. No more HPET error.

Also restore from previous backup from 2.3.5 and everything work pretty well.
Package running on OpenVPN, Suricata and PFblockerNg.

I had a little spare time to test few things.

restore config.xml (2.3.5) with fresh install of 2.3.5 = fail restore config.xml (2.3.5) with fresh install of 2.4.3 = fail edit config.xml (2.3.5) and removed the ACME package = worked in 2.3.5 and 2.4.3 uninstalled ACME package prior upgrading from 2.3.5 to 2.4.3 = worked

So the ACME package was breaking the upgrade/restore, it should be obvious, because ACME depends on a php56 package, which is causing a conflict.

We "image" the pfsense routers once a week. As far as I remember none of the pkg commands worked - pkg-static ..etc, and thats why we werent able to install any packages either. But as said before, since I have reinstalled the server it works again. If it happens again I will try and look at the image and see what changed and maybe get an idea why it stops working.

Thanks for the help anyway.

Out of interest what version was it you needed and what reason do you have for needing it?

I can't think of anything of hand that should not on 2.3.5 at least.

Steve

@callmejacklogan
Great . Appreciate if you can share steps to do this .