Messages

1

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: May 28, 2022, 05:37:40 am »

Here is a RockPro64 image for anyone interested. It includes a few additions in the image - vim, wireguard, ddclient, and mdns-repeater.
https://opnsense.one8three.xyz/opnsense/FreeBSD%3A13%3Aaarch64/22.1/images/

Also, a repo for pkg updates is hosted at https://opnsense.one8three.xyz/opnsense/
Not sure how often it'll get updated...maybe once a month or so.

More info here: https://one8three.xyz/2022/05/25/OPNsense-on-RockPro64.html

2

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: May 16, 2022, 02:30:03 am »

Figured out the problem with the RockPro64 PCI slot!

With FreeBSD, there are a bunch of .dtb files (device tree blobs) on the MSDOSBOOT partition that are not present when making OPNsense for ARM. Sure enough, there is one for the RockPro64.

Copying that dtb folder over resolved the problem. The PCI slot and the 4 port NIC are both detected immediately upon boot.

I can't do anymore testing today, but I'll definitely be doing more testing in the days to come. Exciting!

3

Hardware and Performance / Re: OPNSense & NanoPi R4S (RK3399)

« on: May 09, 2022, 05:29:12 am »

Hello

I've tested OPNSense on my NanoPi R4S. As I can see there is the same problem with speed as in OpenWRT when it's doesn't use IRQ to correct CPU Core pinning (cpu affinity). When I tested my board with Iperf3 I got CPU utilization on A53 cores insted of A72. That is why it is not possible to utilize full gigabit speed in OPNSense. I know that it's possible to do the same trick with IRQ to CPU pinning in FreeBSD, but nothing that I've tried worked. Does anybody knows how to correctly do this in FreeBSD? It would be a great home router, if it will work on full gigabit and OPNSense.

I don't really have anything good to add in terms of actual help but, I've been using a RockPro64 with FreeBSD as my router for about a year now. I just checked iperf, and it used all cores.

I built OPNsense for the RockPro64 and the PCI slot doesn't seem to work. It seems hardware support isn't a direct match with FreeBSD 13. I had to add relevant device tree binaries to the MSDOSBOOT partition and everything works well on the RockPro64 now.

I'm not saying this is the issue in your case, but something to consider.

4

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: May 04, 2022, 03:32:29 am »

Ok, tried a few different things, and still no luck with getting the PCI slot recognized in OPNsense with my RockPro64. Would anyone more familiar with what the differences are between FreeBSD 13 and OPNsense 22.1 be able to chime in with some thoughts?

With the 4 port NIC on OPNsense 22.1, dmesg shows:

Code: [Select]

pcib0: <Rockchip PCIe controller> mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0
pcib0: Cannot get 'pcie-phy-0' phy
device_attach: pcib0 attach returned 6
With the 4 port PCI NIC on FreeBSD 13 shows:

Code: [Select]

pcib0: <Rockchip PCIe controller> mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 0.0 on pci0
pcib0: failed to reserve resource for pcib1
pcib1: failed to allocate initial memory window: 0-0xfffff
pci1: <PCI bus> on pcib1
pcib0: route pin 1 for device 0.0 to 78
pcib0: route pin 2 for device 0.0 to 79
pcib0: route pin 3 for device 0.0 to 80
pcib0: route pin 4 for device 0.0 to 81
Running "pciconf -lv" returns nothing on OPNsense while FreeBSD 13 shows my pci devices... 


::EDIT::
So I switched the kernel to one downloaded straight from FreeBSD but still had the same problem...this is about as far as my troubleshooting goes I think...Not sure where the problem lies.

5

Hardware and Performance / Re: [Work In Progress] OPNsense Ported into ARM Devices

« on: May 01, 2022, 02:55:15 am »

Hi,

struggling for some days now to create a working x-build for a AMD64 host to a NanoPI R4S. Has someone this really working as I continue to run into error messages with the package build (base and kernel build seem to run fine).

I guess it's related to the cc target not being right because when I do a chroot in the build directory (make chroot DEVICE=R4S) and check the cc output I get the following

>>> chroot'ing into /usr/obj/usr/tools/config/22.1/OpenSSL:aarch64/...
root@freebsd-13-0-1:/ # cc --version
FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
Target: x86_64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin

Where I would expect an aarch64 target. Not sure where this is going wrong.

Thnx for your support

I'm having this same problem. Did you ever find a solution?

::EDIT::
I was able to build using a FreeBSD VM on my M1 MacBook. The image boots up just fine on my RockPro64 but the PCI slot doesn't seem to work while it does on FreeBSD 13.