Messages

@efetropy ok. I would be grateful if you could send me the correct file or help me how I can do it.

You can try building an image yourself, but I guess that would take a long time. If you are interested in the current beta (based on FreeBSD 13 which has support for RPi4), have a look in this thread:
https://forum.opnsense.org/index.php?topic=25705.0

You will find a VMDK image there with some other instructions. You can of course convert the VMDK image to whatever format you want (qcow2, raw, etc.)

[UPDATE:]

thank .. great

today i execute a revert snapshot and now i hve this problem. i prupose insert in next vmdk image check FS auomatically

Unfortunately, I am not really sure about the cause of the issue. Looks like a limitation of running opnsense inside a virtual machine. I am no expert in this regards. Although, with the right configuration and hypervisor, you can almost reach bare metal performance – there is always some drawbacks (I could write a wiki article about it  ;D ).

Your best bet would be taking snapshots through ESXi instead of opnsense and revert to an older snapshot through ESXi.

Regarding the next (most likely final) image. I am not adding any configuration in particular that would break the boot. Keep in mind that the opnsense initialization is also adding configs. Technically speaking you shouldn't have boot issues with a sane "loader.conf" and "rc.conf" – for a VM you most likely want to delete a few things in those manually. One in particular which you also figured out would be deleting the line with "hw.uart.console" or just setting it to hw.uart.console=""

As I a said in the previous post, I will add the packages folder to the image. You can adjust the the repo file manually (I will write down the instructions once I create the image). You can of course also add the official FreeBSD repo, but I won't take any responsibility for any dependency hell :)

UPDATE: Here is the final image: https://we.tl/t-6zrzXJYDkM

To add the local repo, edit the /usr/local/etc/pkg/repos/OPNsense.conf file:

Code Select Expand


OPNsense: {
  url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
  signature_type: "NONE",
  mirror_type: "NONE",
  priority: 11,
  enabled: yes
}



Perform a pkg update and you are set to go

That sounds like a plan!  8)

open-vm-tools-nox11 is actually available in the packages archive. I haven't tried to include certain packages in the image, but what I can do is to simply add these packages to a certain folder (/usr/ports/packages) within the image and create a local repo for you. You can then install the required packages on demand (even without internet access).

So for the next vmdk image, I will just adjust the quirks and add the repo :)

Hey @efetropy, I used this one - https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.1/images/dirty/ but VM didn't boot

Ahh that's not a VM image actually. If you like to, I can try to create a qcow2 or raw image for you. Maybe that will help

I am glad to hear it worked out in the end. It would be great if you tell me more about overall stability.

Well, updating is not possible which is why I provided you the packages archive. The image I created for you is from the development branch and arm64 is not "officially" supported by opnsense yet. In other words, an official opnsense repo for aarch64 does not exist. The provided image itself is experimental, so you can expect bugs, stability issues etc.

22.1 is scheduled for release in January, but I can't tell how soon official arm64 images will be available. Nevertheless, community builds for different arm devices will for sure be available either on the same day or shortly after.

The packages I uploaded are all up to date (I have compiled them yesterday). If you want to use a small repo to install packages, you can also create your own with the archive I provided you.

For more info and details, feel free to follow this thread:
https://forum.opnsense.org/index.php?topic=12186.0


EDIT: Yeah, I expected you to face these issues (that's my fault actually, I have commented out  something inside the code which most likely caused it, but I can easily fix that).

I'm trying to create a OPNSense VM on Proxmox with diry image from @yrzr without success. Anyone have tried it and successfully installed it ?

What do you mean by dirty image? I recall there being a 21.7 version with the kernel from FreeBSD 13 for the RPi 4. Is that the one you are talking about?

Would be great if you provide more information. I can probably help you out :)

I managed to solve the build issues. The GUI should be available now. Let me know if this image works for you. If it doesn't, I might have to add a few quirks (wouldn't take long). You can also use the packages as local repo (:

VMDK image: https://we.tl/t-yMPVbYgqnt
Packages: https://we.tl/t-X0K01nBY1V

Congratulations! You and your family have all my blessings :)

I am glad to hear that the image works for you. As mentioned in my previous post, the image only contains the base and kernel. It was just to see whether it's gonna boot up on your device or not. Since it boots up, we can proceed with the next steps.

Did some research and found out that with open-vm-tools 11.3.0 they added support for arm64 (vmci is not working). You can read more about it here https://github.com/vmware/open-vm-tools/pull/474 and https://vincerants.com/open-vm-tools-on-freebsd-under-vmware-esxi-arm-fling/

As you are not using a graphical desktop, I recommend you to use "open-vm-tools-nox11".

The reason why you don't have a GUI for opnsense is that I haven't built it. There is good news though. I finally managed to build the packages, but ran into some issues (as expected). Apparently some packages required to build the opnsense core depend on "go" where the latter is not build as per settings. I will try to build go and the remaining packages and eventually provide you a final vmdk image.

If you have time and want to get your hands dirty, you can have a look at this repo:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A12%3Aaarch64/21.7/latest/All/?C=N&O=A

Most of the packages are available here (my one is missing around 15 of them due to build errors).

[UPDATE:]

[...]
pkg: No package files have been found
Cannot create repository catalogue
*** Error code 1

Stop.
[...]

I am using a similar setup but cross compiling for aarch64 on a FreeBSD 13 host. Ran into the same issue twice.

My guess is that pkg 1.17 installed in your build system breaks this. You can see the failing command with VERBOSE=yes and I suspect that pkg-repo looks for *.pkg files but we still have *.txz files.

That's good to know. In that case, maybe pkg 1.16.3 is worth a try. I will give it a shot and am hoping for a successful build this time  ::)

BR,
efe

UPDATE: Franco's guess turned out to be the case here. In fact, the newer pkg version breaks the build. Using 1.16.3 worked out for me. Although some packages were not built (some of them require go as build dependency and we are not building go for arm, arm64 as per aux.conf). Will have a look later and see if I can build them separately.

Code Select Expand


[7/9] Deleting files for pkg-1.16.3: 100%
[8/9] Deinstalling pkgconf-1.8.0,1...
[8/9] Deleting files for pkgconf-1.8.0,1: 100%
[9/9] Deinstalling png-1.6.37_1...
[9/9] Deleting files for png-1.6.37_1: 100%
Creating repository in /usr/obj/usr/tools/config/22.1/OpenSSL:aarch64/.pkg-new/: 100%
Packing files for repository: 100%
>>> Running build step: clean
>>> Passing arguments: packages
>>> Removing packages set
>>> Creating package mirror set for 21.7.6_87-OpenSSL-aarch64... done
-rw-r--r--  1 root  wheel   338M Dec  2 12:32 packages-21.7.6_87-OpenSSL-aarch64.tar
>>> ERROR: The build encountered fatal issues!
>>> Aborted version 2.0.45 for dns/dnscrypt-proxy2
>>> Aborted version 1.31.0_1 for net-mgmt/netdata
>>> Aborted version 1.20.4 for net-mgmt/telegraf
>>> Aborted version 196.04 for net/realtek-re-kmod
>>> Aborted version 4.36.2 for net/v2ray
>>> Aborted version 2,1 for net/wireguard
>>> Aborted version 0.0.20211016,1 for net/wireguard-go
>>> Aborted version 0.0.20211105 for net/wireguard-kmod
>>> Aborted version 1.8.2 for security/vault
>>> Aborted version 4.1.1 for security/yara
>>> Aborted version 4.7.0 for sysutils/ansible@py38
>>> Aborted version 7.15.2 for sysutils/beats7
>>> Aborted version 1.10.3 for sysutils/consul
>>> Aborted version 1.2.2 for sysutils/node_exporter
*** Error code 1

Stop.
make: stopped in /usr/tools


UPDATE 2: Looks like cross compiling go doesn't work. Will try to build the remaining packages natively on the device

[UPDATE:]

I can provide space for repository and available for testing. have you then installed opnsense on arm fling pi4 8gb?
did you also manage to get openvmtools or vmware tools to work?
I remain at your disposal

In that case, let me setup the packages first (compiling takes a long time). I gave away my RPi 4 and currently own a RPi CM4.
Booting from an sd card works without issues. The image both for the RPi4 and RPi CM4 is essentially the same where the latter just requires an additional line in /etc/rc.conf to boot.

Afaik ESXi-Arm Fling doesn't work on the CM4 (or maybe it does? haven't seen it in the supported devices list). I could test it, but would take some time. Maybe it's easier if I just provide a vmdk image for the RPi4 and you can tell me whether it works or not on ESXi-Arm Fling. I can't say much about open-vm-tools. Technically speaking, it should work and it's also available as FreeBSD port. We won't know unless we try :)

I will let you know once I am done creating the image (should't take too long, I have everything ready more or less).
Can't give you a time for the ports though (might have to face compiling errors etc.). Will get there eventually :)

By the way, do you have any requirements for the image and swap size? The standard is 20G and 1G for swap.
For testing we can just go for smaller values I guess.

UPDATE:
For starters I created a vmdk image for you. It boots up fine on my host (amd64) with qemu.
I turned off swap and the image size is 5 GB. Here is the link: https://we.tl/t-QawChIcscD
(Don't get surprised about the small archive size, it's just compressed)

i have VMware ESXi ARM Fling on raspberry pi4B 8gb , exist ther vmdk or ova for this device ?

I don't know if any exists, but you can to create your own image using the opnsense tools.
A good starting point would be here https://github.com/opnsense/tools

You will need some adjustments though, e.g. a slightly modified device config file for you RPi 4B,
adjust some build scripts and so on. I can already tell you that cross compiling the development version 22.1 (based on FreeBSD 13) works for me.

If you don't mind helping me out with some testing (just some basic stuff like stability, booting process, ...) I can provide an image. I won't be able to offer you any repo as I have no means to host one right now, but if the packages are not too large, I could upload them somewhere so that you can download and install them on demand.

PM me if you're interested so that we can talk about further details.

BR

I am trying to built an arm64 image with the stable/22.1 source on a native arm64 (RPi CM4) FreeBSD 13 STABLE host, but keep running into the same issue as stated here:

https://github.com/opnsense/tools/pull/222#issuecomment-948657705

Has anyone tried the same or actually knows a solution for that?

If someone has a working image, I would be happy to have a look at it.

EDIT: After another run, I managed to build the world and kernel successfully. Currently compiling packages – stay tuned for further updates.
Packages also compiled (and took quite a long time) and required a lot of space.
With some little changes, I managed to make an image. Booting worked on my CM4. I won't provide an image here as this was just to see whether compilation works or not