opnsense 22.1 for VMware ESXi ARM Fling on raspberry pi4B 8gb

[efetropy]

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]

url: "https://[IP]/opnsense/FreeBSD:13:aarch64/21.7.6/latest"
where IP is your webserver

[sharezone]

i configure web site repository on url https://opnsense.sharezone.cloud/ and change the file

/usr/local/etc/pkg/repos/OPNsense.conf

on

OPNsense: {
  url: "https://opnsense.sharezone.cloud/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
  signature_type: "NONE",
  mirror_type: "NONE",
  priority: 11,
  enabled: yes
}

but when i execute "pkg update" return error   "Segmentation fault"

root@OPNsense:/usr/ports/packages/opnsense/FreeBSD:13:aarch64/21.7.6/latest # 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
Child process pid=17426 terminated abnormally: Segmentation fault

 where may be the problem

i try with

OPNsense: {
  url: "pkg+https://opnsense.sharezone.cloud/opnsense/FreeBSD:13:aarch64/21.7.6/latest",
  signature_type: "NONE",
  mirror_type: "NONE",
  priority: 11,
  enabled: yes
}


but the problem is the same

i have another issue on file system but i think that the problem is on version esxi because

i read that problem is on version esxi arm with usb datastore.

i have

ESXi Version   7.0.0
Hypervisor   VMware ESXi
Build   17230755

and on Build 19025766 (https://flings.vmware.com/esxi-arm-edition#changelog)

"Improve USB stability issues, especially with RTL8153-based USB NICs (a common chipset) and especially on Raspberry Pi and Tegra Xavier"

i try and update the thread

 

[efetropy]

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.

[sharezone]

root@OPNsense:/var/log # pkg -v
1.16.3

root@OPNsense:/var/log # cat /usr/local/etc/pkg/repos/OPNsense.conf
OPNsense: {
  url: "https://opnsense.sharezone.cloud/opnsense/${ABI}/21.7.6/latest",
  signature_type: "NONE",
  mirror_type: "NONE",
  priority: 11,
  enabled: yes
}

same issue

root@OPNsense:/var/log # pkg update
Updating OPNsense repository catalogue...
Child process pid=9364 terminated abnormally: Segmentation fault
root@OPNsense:/var/log #


what do you mean "Eventually relocate that folder (or remove it alltogether) from your local disk and reset pkg.
"

delete all file and folder under /usr/ports/packages/

[efetropy]

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?

[sharezone]

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

[efetropy]

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?

[sharezone]

nothing . i try both "srv" and "http" but same issue .

Bu if you try on your version with my public repository , funtion ?

[yolocoffee]

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.

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.

[john_matrix]

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!

[daemonix]

Hi,

Thanks for the work you have done with arm64/UEFI!
I run pimox7 on pi4 adn I was hoping to test your image.

Is there an updated location or image? All links seem dead.

Thanks!

EDIT: an image for EXSI works great with pimox7, just a conversion away. It mainly need proper UEFI boot.

[efetropy]

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.

[daemonix]

Thank you! Downloading to test on my little proxmox.

[daemonix]

Anyone had a similar boot problem?
Thanks!

Code: [Select]

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


[efetropy]

Anyone had a similar boot problem?
Thanks!

Code: [Select]

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.