Messages

THAT WORKS !!!

Thank you very much .... I was able to do the tests and it is very stable ...
Watchguard's XTM range of machines (in fact Lanner machines) can be started without any problem and without the need of workarounds.
I good to test on an XTM-870F and XTM-1525 with a 10G fiber connection and it seems very great ....

Thank you very much.

Yes, it is a "VGA" that I use.
But I don't want to take your time, especially since from the moment it's in the pipeline, I could do the tests even later.
In any case, thank you very much.

Thanks again for all your work and to all contributors.

Best regards.

Thank you very much for your return, and the consideration of my request.

Since the problem appears during the installation, it will be more productive if I manage to test with an installation image of 22.1.2 (or 22.1.3). In addition, it will allow me to do the tests on a machine other than the "production" one.
To download the beta images of 22.1.2 are they public for help with test ? (Because I don't have the ability to make a clean image from the sources, and we wouldn't know if the problem comes again, if it's from the code, or more probably from my lack of experience!).
Otherwise I would gladly wait for it to be online when the time comes to make some test to help.

In any case, thank you very much for all the work and cordial greetings.

Regards.

thank you for your feedback

... I am happy that it helped you.  I've just merged the patch to both FreeBSD stable/13 and stable/12 ...
https://cgit.freebsd.org/src/commit/?id=376fd49ae3b9f07e122a3479f65c9414b38d7bae

for my part it makes it possible to install OPNsense 22.1 on several Lanner or Watchguard machines, and I would gladly try to do the test, (if I succeed!)

For the record, I was on PFsense before and when they upgrade from Freebsd 11.3 to Freebsd 12.2 I found myself stuck, but I hadn't understood the exact cause. On the other hand it allowed me to discover OPNsense which was based on an earlier version of Freebsd did not pose a problem. The switch to 22.1 (and Freebsd 13) made the problem reappear, but thanks to the help of people from the community and help ho Motin, I was able to better understand the problem and bring it up, hoping that it helps other people too (anyway i hope).

Thank you

Update 22.1 having integrated version 13 of Freebsd, I discovered that my machies have a problem with this version.
I use converted machines from the Watchguard XTM 850/870/1250 series...
After a lot of research and help from several people, I found that it came from the APEI part (has write in an other post, setting in boot loader "set hint.apei.0.disabled=1" make a work around for the moment).

After having been able to make a detailed report to the person in charge of this part on Freebsd - Alexander Motin -. He made a modification of the code which now makes it possible to run correctly the new version of Freebsd 13, on machines like the one I use.

My question is to know if the transmission of the tree structure of Freebsd 13, on the future iterations of OPnsense 22.1 will be done automatically (and thus will automatically integrate the patch) or if I must submit this to the development team (unfortunately not being able to have the skills to do it myself).

I was happy that my experience was able to help you, but a little above that it did not work as hoped!

Since I have 2 boxes, I put one in the main router, and with the trick of the 1st post I was able to install a new version 22.1 which works well (for the moment, but it's been a few days already!). And with the other machine I did some tests, and I installed different versions of Freebsd ... or rather I couldn't install them!
After having exchanged with Alexander Motin (who takes care of the ACPI part of Freebsd) he modified some code from the CURRENT version and it works in my case.
And if all goes well, it should then go back to future versions of OPNsense (if I understood correctly)

If you think you can do the test with freebsd I would gladly send you the links.
On the other hand, I am not strong enough to be able to help you more in the state of things. Maybe you have logs to better understand if it's the same problem?
I hope you will be able to solve your problem. For information, I had found a lot of help here but also on the IRC

For a few years now, I have been using second-hand routers where I install a **sense in them, (first PFsense, then for some time OPNsense). It opens up possibilities for me that I could not fund otherwise. A big thank you to the whole OPNsense team and to all those who have gone before, and to the whole BSD movement for this superb software and knowledge.

My last machines are WatchGuard XTM-870 and XTM-1525 (in fact it is a derivative of the Lanner FW-8758) machines a little old, but very reliable, with very good characteristics and powerful (for my needs in all cases and it is possible to find used ones at very affordable prices, since they are a bit dated!)

The machine was updated regularly without any problems. But the last 22.1 update broke everything for me (by the way, a little reminder in passing: don't forget the backups!! I hadn't done it and it was complicated to recover the configuration file, but that's is another story and above all just my fault!)

After the crash, wanting to install a clean 22.1, I couldn't do it, while I could easily put a clean 21.7 back. This put me on the trail of changing the operating system. In fact 21 is based on a derivative of FreeBSD 11 while 22.1 is based on a much more recent true FreeBSD.
After several hours of testing, I was able to define that all FreeBSDs up to 12.1 can be installed without problem on this machine, but not the following ones (from 12.2 and all following impossible!)

After a lot of reading on the forums and IRC and especially the precious help of several people, the problem was the APEI management (part of ACPI). I also managed to inform the maintainer of this module on FreeBSD, Alexander, whom I thank very much.

By using the following variable at boot time I was able to work around the problem :

set hint.apei.0.disabled=1

I have a few questions:

1/ Have other users of WatchGuard or other machines encountered this problem? Were they able to update the BIOS (I couldn't). Where did they find another workaround?

2 / having no computer studies base, I find it difficult for me to better define the problem and to be able to solve it, but perhaps others have experience that would allow things to move forward. It is happy that I can do tests on my machine, if that can help to solve the issue and improve the product for everyone.

3/ while waiting for a more lasting solution to be found, I need to be sure that future updates will not modify my workaround (and broke all an other time). From what I have read the most consistent create a file /boot/loader.conf.local and put hint.apei.0.disabled=1 there. I can consider to do in ssh, but i prefer to make it from GUI interface if possible, to be more in the spirit of OPNsense.
I go on the page system:settings:tunables but I'm having trouble to create the file loader.conf.local. Could you give me a hand to do it as correctly as possible.

Thank you and have a nice day (and sorry for my googelized English!)

Hello,

i have a XTM-870 and works with pfsense until 2.4 than go on opnsense and was ok until 21.7 but the 22.1 can't be installed for the moment. It's a APEI probleme, but tray to found a solution.

Your machine is from LANNER FW-8758 familly (you can found intresting manual on it).

1/ i have install a vga connexion
2/ flash a CF card with OS to install
3/ go on bios to boot on it
and works for me (until the new freebsd problemes .... until 12.1 ok, but all after versions are for the moment ko e work around is to set in boot loader hint.apei.0.disabled=1)

best regards