Messages

Hi,

Which image did you use?

Would you mind sharing?

Are you referring to the ROCKPro64 image? You can simply get the R4S image from https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/

All you gotta do is write the bootloader files and you're set

Anyone had a similar boot problem?
Thanks!

Code Select Expand

Consoles: EFI console 
    Reading loader env vars from /efi/freebsd/loader.env
Setting currdev to disk0p1:
FreeBSD/arm64 EFI loader, Revision 1.1

   Command line arguments: loader.efi
   Image base: 0xb82ff000
   EFI version: 2.70
   EFI Firmware: EDK II (rev 1.00)
   Console: efi (0x20000000)
\
             ______  _____  _____                         
            /  __  |/ ___ |/ __  |                       
            | |  | | |__/ | |  | |___  ___ _ __  ___  ___
            | |  | |  ___/| |  | / __|/ _ \ '_ \/ __|/ _ \
            | |__| | |    | |  | \__ \  __/ | | \__ \  __/
            |_____/|_|    |_| /__|___/\___|_| |_|___/\___|

/-----------------------------------------\     @@@@@@@@@@@@@@@@@@@@@@@@@@@@
|                                         |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|  1. Boot Multi user [Enter]             |   @@@@@                    @@@@@
|  2. Boot Single user                    |       @@@@@            @@@@@   
|  3. Escape to loader prompt             |    @@@@@@@@@@@       @@@@@@@@@@@
| Autoboot in 0 seconds. [Space] to pause |         \\\\\         /////     
|  5. Cons: Dual (Video primary)          |   ))))))))))))       (((((((((((
Loading kernel...                          |         /////         \\\\\     
/boot/kernel/kernel text=0x2a8 text=0x924830 text=0x219e64 data=0x1b21c8 data=0x0+0x36a000 syms=[0x8+0x1312e0+0x8+0x156774]
Loading configured modules... (1 of 1)     |       @@@@@            @@@@@   
/boot/kernel/if_enc.ko text=0x15ca text=0x934 data=0x750 syms=[0x8+0xca8+0x8+0xb71]
/boot/kernel/if_bridge.ko text=0x3677 text=0x7168 data=0xd38+0x8 syms=[0x8+0x1b90+0x8+0x15b5]
loading required module 'bridgestp'        |   @@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
/boot/kernel/bridgestp.ko text=0x12e4 text=0x4acc data=0x2c8+0x28 syms=[0x8+0xb88+0x8+0x6e9]
/etc/hostid size=0x25nds. [Space] to pause
/boot/kernel/pf.ko text=0xe344 text=0x3dc7c data=0x59c0+0x39c syms=[0x8+0x5910+0x8+0x46ec]
/boot/kernel/pflog.ko text=0xf78 text=0x898 data=0x430 syms=[0x8+0x9f0+0x8+0x712]
/boot/kernel/if_gre.ko text=0x2736 text=0x4938 data=0x8c8+0x40 syms=[0x8+0x16f8+0x8+0xfaf]
/boot/kernel/if_lagg.ko text=0x3c93 text=0xa41c data=0xd08+0x8 syms=[0x8+0x1c80+0x8+0x15a6]
loading required module 'if_infiniband'
/boot/kernel/if_infiniband.ko text=0x1102 text=0x10fc data=0x300+0x8 syms=[0x8+0x8d0+0x8+0x59a]
/boot/entropy size=0x1000
/boot/kernel/carp.ko text=0x33ec text=0x6e54 data=0xc60+0x48 syms=[0x8+0x1980+0x8+0x1225]
/boot/kernel/pfsync.ko text=0x2f1c text=0x7b24 data=0xb30+0x8 syms=[0x8+0x1800+0x8+0x117d]
No valid device tree blob found!
WARNING! Trying to fire up the kernel, but no device tree blob found!
EFI framebuffer information:
addr, size     0x0, 0x0
dimensions     0 x 0
stride         0
masks          0x00000000, 0x00000000, 0x00000000, 0x00000000


Do you have hw.uart.console="" in loader.conf.local under /boot? If not create the file and add that line.

Up and running on my ROCKPro 64

Sorry for the late reply!
Was busy with other stuff lately, had little to no time and to totally forgot to reply.

Hello @efetropy,

Can you share the patches required to build opnsense 22.1 for a Raspberry Pi 4? I'd like to help with this.

I'm just getting started and have finally understood how to build it but missing the specific configuration for RPI4.

Dear all,

Currently, I have a CM4 (with 4GB RAM and 8GB eMMC and no Wifi) and the DFRobot IoT Router Carrier Board (https://www.dfrobot.com/product-2242.html).

I am interested to compile an OPNsense build for this hardware but I am a little bit lost about it's potential compatibility.

Can someone confirm me that's this will be good or not?

Many thanks in advance!

There is already an image built by @yrzr for the RPi which can be found here:
https://ftp.yrzr.tk/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/

A generic aarch64 vmdk image is also available (for e.g. for proxmox, esxi fling or whatever you're using).

The RPi 4B should work without problems (if not, just get some different boot files).

CM4 is a different case. It does work with the official I/O board albeit PCIe issues (see bugzilla).
Your carrier board states ETH2: PCI Express 1000BASE-T NIC (based on RTL8111). RTL8111 drivers are in fact available, but
it will be a hit or miss and you might not be able to the use the 2nd ethernet port due to the mentioned PCIe issues.
Furthermore, you have to figure out how to deal with the dtb file. Worst case scenario, you might have to make it compatible with freebsd.

Now that 22.1 is out, how is the status of this?

Building base and kernel for generic ARM64 works without problems. We just ran into some issues trying to build the packages.
I kinda sorted out the latter and am currently building the packages. If all goes well and works on my devices, I will do some PR.

With 22.1 more devices can be supported (theoretically) since the new release is based on FreeBSD 13.
Even though the device configs are not upstreamed yet, writing them should only take a few minutes.
Just to mention, PINE 64, PINE 64 LTS, ROCK64, ROCKPRO64 and RPI 4B should work now.

NanoPI R4S vs R2S were already supported in the previous release, so it's just a matter of building the packages and creating the images :)

it is feasible to port OPNsense to an ARM Cortex-A72 (Marvell® ARMADA® 7040)?
There is a OpenWrt SNAPSHOT available for the Globalscale MOCHAbin (I do have dev board).
Moreover I have Debian and Ubuntu image.

What would be the way to go to port it?


thank you
stefan

Afaik the Armada 7k SoC is already supported by FreeBSD (see https://www.freebsd.org/status/report-2021-01-2021-03/marvell/)
The report is from early 2021 so can't tell whether they mean HEAD as in FreeBSD 14 or 13. Nevertheless, you are probably one of the few people who own a MOCHAbin dev board. Aren't the latter supposed to get shipped around Q2 2022?

If you have access to the datasheet, and maybe also the kernel source code (besides the image, so that you have an idea about how the drivers etc. work) you can start porting to FreeBSD. Don't know if OPNsense is the right place for it, but I guess you can get more help in the FreeBSD forums / mailing lists.

i rename the folder opnsense under /usr/ports/packages on opnsenseold

execute

root@OPNsense:~ # pkg upgrade
Updating OPNsense repository catalogue...
Child process pid=68697 terminated abnormally: Segmentation fault

same issue .

I have not done any operation. I also tried to put back the original vmdk but same error.

i resubmint the original confiuration

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

but nothing .

i can't figure out where the problem is

Can you change the mirror type to "srv" or "http" and try again?

Indeed either delete the files or move the folder with its contents to some other place.
Did you also try pkg upgrade followed by pkg update? It's weird that you're getting a segmentation fault.
With the local repo, you didn't have this issue. It looks like the ports database is corrupted for whatever reason.

Did you try anything else before changing to the repo to your webserver?

Did you by any chance update the pkg? Would be interesting to see which version you have. Just type "pkg -v" in the console. Maybe there is some sort of incompatibility (there were some recent changes). We can eventually debug and backtrace the problem. I have also hardcoded the ABI in the url, can you also try the following:

https://opnsense.sharezone.cloud/opnsense/${ABI}/21.7.6/latest"


Eventually relocate that folder (or remove it alltogether) from your local disk and reset pkg.

Regarding your USB problem. I guess you're trying to use a USB to Ethernet adapter with RTL8153 chip. What do you mean by filesystem issue? If you elaborate, maybe we can figure out something.

I have server web ,private and public  , but i don't know configure the repository. Can you help me ?
Thanks

The local repo I created for you has the same folder structure as https://ftp.yrzr.tk/ and is available under /usr/ports/packages/
All you gotta do is serve these folders/files in your webserver. In the end the url would be something like

Code Select Expand

url: "https://[IP]/opnsense/FreeBSD:13:aarch64/21.7.6/latest"

where IP is your webserver

on firmware >> packages i see packet

That's how it should be. Under packages you see the installed packages. That means no issues with the GUI.
Looks like the local repo is causing problems. As mentioned earlier, just try to setup a webserver and create your own repo.
Should work that way :-)

i replaced

root@OPNsense:~ # cat /usr/local/etc/pkg/repos/OPNsense.conf
OPNsense: {
  url: "file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
  signature_type: "NONE",
  mirror_type: "NONE",
  priority: 11,
  enabled: yes
}
root@OPNsense:~ # pkg update
Updating OPNsense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.txz: 100%  192 KiB 196.4kB/s    00:01
Processing entries: 100%
OPNsense repository update completed. 647 packages processed.
All repositories are up to date.
root@OPNsense:~ #

now why not see plugin ??

I can see that the local repo is initialized. You should be able to install packages from the command line.

Why the plugins tab doesn't work in the GUI, is something I have no answer to. Can you see packages in the "packages" tab?
If yes, maybe I messed up something with the plugins (which I doubt). If the answer is no, maybe the core package does not support local repos in general. I haven't tested it, so can't tell. Someone else with experience might be able to help you better in that case.

There is one other thing you could try though. Just use a local webserver either within opnsense itself or since you are using ESXi, use a second VM (FreeBSD, Linux, or whatever you prefer). Make sure the webserver is reachable from opnsense. You already have the folder structure, so it should be easy. One you're set, just adjust the url of the repo config.

Btw., can you just change the url to

Code Select Expand

url: "pkg+file:///usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest"
and see if it works?

Just replace it :-)
This repo

Code Select Expand

url: "pkg+https://pkg.opnsense.org/${ABI}/22.1/latest",
doesn't actually exist

i think that this vmdk is corrupted because when i execute the command show this messages

[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense] vmkfstools -i last_update.vmdk last_update_1.vmdk
DiskLib_Check() failed for source disk The file specified is not a virtual disk (15).
[root@shrarm01:/vmfs/volumes/3679591e-7f04ccfd/Firewall/OPNsense]

on the tree folder i see

GNUSparseFile.0

i suppose missing descriptor file or *-flat.vmdk file

I reacreated the image: https://sendgb.com/5xMlT13Xcpq (VMDK, this time no other compression)

you installed proxmox or esxi ARM fling ?

I tried both and i could only boot with esxi but didn't had network interfaces working even with manually configured interfaces.

Which kind of network interface are you using?

@efetropy, I downloaded your vmdk image, converted it to qcow2 then I imported to my Raspberry Pi 4 with Proxmox and run it on my new VM, it stops on "Hit [Enter] to boot immediately, or any other key for command prompt". Any guess what could beeing happen ?

Do you mean getting a black screen (no output) after you hit enter or does the VM completely crash? If it's a complete crash, let me create a qcow2 image for you directly and we can proceed from there. If there is simply not output I suspect something related to the vm configuration in proxmox. If you have a chance to share some logs, the proxmox vm config etc., I would appreciate it :)