[Work In Progress] OPNsense Ported into ARM Devices

[sparticle]

I have a decommissioned RPI4 that I am wanting to run OPNSense on. I have tried this build for the RPI4 but it does not boot.Blink code suggests it can't find the kernel.img.

 https://www.yrzr.tk/opnsense-22-for-aarch64/

Can anyone suggest how I get a build up and running on the RPI4? At this location, I only have a 40/10 VDSL service so the USB3 J5 Create nic should be fine.

Really would like to play with a working build. I saw earlier in the thread someone said they had a 22.7 build running.

I have tested my hardware with the standard FBSD aarch64 image and it boots first time so I know the hardware is good.

Any help is appreciated.

Cheers

[sparticle]

Talking to myself probably.

I managed to get the 22.1.10 image to boot on my RPI4 after connecting a ttl adaptor and seeing what was going on. Weirdly I think it was a corrupt write operation to the card.

I decompressed the image first then wrote it to the sd card rather than let Ubuntu disks app do it on the fly.

That worked and I had a booting image.

It is very snappy compared to my vmware OPNSense with much more resources.

Is it possible to get a build of the latest 22.7 as it has a few inclusions we need one being APCUPSD service.

But this has been a great surprise and I am a little shocked at all the negative comments regarding running OPNSense on the RPI4 I am using the native GbE adaptor as the lan adaptor and a J5Create USB3 Adaptor as the wan adaptor.

It uses the axe driver and is recognised and configed perfectly and seems to work without any issues.

As this seems to be a 'standard' aarch64 build it would be great to see this as a standard build from OPNSense ARM devices are proliferate and incredibly performant for the power footprint.

Thank you to yrzr for all the work producing these builds and the corresponding installation and configuration notes.

This is the link I followed https://www.yrzr.tk/opnsense-22-for-aarch64/ to get a working build.

Cheers
Spart

[gwurb]

I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.

Here is what I did:

Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz

Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.

I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.

Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?

Thanks

[HappyOpnSense]

Hi all, excited to join in on the fun here!

I currently have 22.7 running from yrzr.tx on an R4S. I now see from a few posts above that this version is broken  so I'll try 22.1.10 shortly. My hope is to replace my hp t730 for home use.

After enabling powerd and setting it to maximum cpu frequency scaling I am able to push around 400mbit in each direction through the unit in cursory iperf3 testing.
I have a Cisco T-Rex benchmarking setup and I plan to do more in depth testing - different packet sizes, number of flows, open states, etc.

When initially testing on openwrt I was able to pin irqs and receive queues for the two nics to the faster A72 cores which was a notable improvement.
Is this possible in opnsense/freebsd? I did a bit of googling and didn't find any definitive answers.

I also have two R4SE's (I dream of HA firewall at home) with 32gb of emmc onboard.
I have tried flashing a few different opnsense images using rkdevtool with no success yet (I didn't really expect it to justwork).
Anyone have any ideas on that? It seems the tool wants the image split into various partitions, but it does allow me to just flash the whole image starting at 0x0.
I haven't dived into the image build process but I'm sure I'll dig into that soon.
I have a 3v3 rs232 adapter on the way so I'll be able to get a console on these things soon.

Anyway, happy to test/help/etc!

Can only confirm that I always build the R4S images myself (R4S is one of the standard targets) and never had an issue with these. Recently upgraded from 22.1 to 22.7 without an hitch. Building on a Rock PI4 - which has an SSD - as that is native build which takes 1+ day.

[sparticle]

I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.

Here is what I did:

Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz

Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.

I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.

Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?

Thanks

A great investment <10$ is a USB to TTL serial adaptor. Try DSD TECH

This allows you to congfig the serial out when booting to follow the boot process and interact.

Cheers
Spart

[gmiranda]

I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.

Here is what I did:

Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz

Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.

I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.

Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?

Thanks

Same here (raspberry pi 4 8GB). Tried extracting the xz file before running dd, according to the instructions in https://yrzr.tk/opnsense-22-for-aarch64/#41-writing-the-image, but to no avail.

I can't either get the image to work under qemu, it boots and after I configure the ethernet adapters it hangs completely.

[antonio66]

Hi,

I know, older thread... Does somebody has a working port of newer opnsense for orange pi r1 plus? Or has a download link for it? Thx

antonio

[jeremy.mcmillan]

It's not clear if you got a corrupted download, or whether you were able to decompress the image, or what the flash drive layout looks like after you wrote the raw blocks to it or what.

Do you have enough troubleshooting skills to understand what can go wrong with those steps and how to verify whether it did or not?

I followed what I understood on https://yrzr.tk/opnsense-22-for-aarch64/
but can't get RPI4B system to boot. I don't have a serial adapter so unfortunately can't troubleshoot a lot.

Here is what I did:

Downloaded:
OPNsense-22.1.10-OpenSSL-arm-aarch64-RPI.img.xz
and
OPNsense-22.7.5-OpenSSL-arm-aarch64-RPI.img.xz

Used Raspberry Pi Imager to write the img to file. Renamed config_rpi4.txt to config.txt and deleted config_rpi3.txt . Put the newly flashed card into RPI4 and powered it up. It gets to the rainbow/multicolour splash screen and then nothing. This was the case for both img files, written with either Raspberry Pi Imager or Balena Etcher, unarchived first or provided as .xz to the imager. I tried this on two RPI4.

I tried booting the same card on RPI3B+ with config_rpi3.txt renamed to config.txt and it booted, showing the boot process. I set a static IP and then used config_rpi4.txt renamed to config.txt to boot rpi4. Got the rainbow screen but could still access the system. So there is something wrong with the video.

Is there something wrong with the default config_rpi4.txt? What could I try to get the console to show on hdmi output?

Thanks

Same here (raspberry pi 4 8GB). Tried extracting the xz file before running dd, according to the instructions in https://yrzr.tk/opnsense-22-for-aarch64/#41-writing-the-image, but to no avail.

I can't either get the image to work under qemu, it boots and after I configure the ethernet adapters it hangs completely.