@spikerguy thanks for the quick response. This looks promising, however I need to digest your answer a little bit (sorry, I’m not a linux guys, just learning it :)).
So, this means, I can install and use haproxy backend to my rockpi, but I will not be able to manage it from the opnSense UI (because of the missing opnSense plugin). Am I right?
Opnsense is bsd and not linux. 
No.
os-haproxy is the opnsense plugin of ha proxy so you can use it from the UI.
With the latest image of rockpiE you should be able to do most of the work from the UI itself.
Give it a try.
Ok at least it’s known now by everyone that I’m not a BSD guy too 
Thanks for the correction, studying all the time
Thanks for your great help, I’ve successfully updated to the latest image 21.7.5 and installed HAproxy.
That was fast. 
Please join @personalbsd group on telegram and share your use case and also ask opnsense specific questions.
Enjoy HAProxy.
Hi @spikerguy ,
Yesterday I’ve updated my router to the latest build OPNsense-22.1.6, and for some reason the WAN adapter was not connected. Previously I was using 21.7.5 and also some other earlier versions and both LAN and WAN was working fine.
This is what I saw on the UI:
And this is from the console:
What is also strange, the console is saying the dwc1 (WAN) is Gigabit, but RockPi E has only 1 gigabit ethernet, the second one is only 100 megabit.
Is there any config change on my end needed to get to work?
Thanks!
@SleepWalker do you have rockpie for testing this?
I have it in production and i cannot upgrade it yet.
Hi @abal .
Rockchip Gigabit Ethernet Conctroller - this is name of controller no a port.
Both ports use this Controller - it is true.
If the device dwc1 is defined - it should work.
Try to just make a new test installation and not upgrade.
I don’t see any reason why this wouldn’t work.
So far I have not been able to test myself.
@spikerguy Hi
One of the users has already upgraded and everything worked fine here is an example
Hi @SleepWalker,
Sorry I was not clear enough. The update meant, I did a new clean install on a different sd card, then imported the previous config. So it was not an in-place upgrade.
This is the issue. I had same problem when trying to restore from old config.
You need to look at your backup xml file and find the lan and wan port names and correct it as per the new installation.
You can also go to interface setting in opnsense and re assign it correctly.
There is a negative experience of such experiments
Hey guys,
Thanks for the quick response. The first try was wrong, I tried to assign only WAN and I think the LAN was then unassigned :). What is strange, the UI show both interfaces assigned, but the console not. Need to re-flash and will try again.
BTW: you are saying there is a wrong experience by importing the config. What is then a preferred way of update? The 2 SD cards and separate installations are very comfortable and safe for me, as anything goes wrong, I just replace the cards and all is working again.
An update here:
I started everything from scratch, I’ve flashed the card with the vanilla opnSense 22.1.6. I’ve booted my rockpi, but now I did not restore the previous config, to see if this is really breaking the interfaces. So, the first boot, was showing the same behavior, the LAN was assigned and working correctly, but the LAN not. So, I tried to re-assign the interfaces, but after the reassignment, the result was the same. Here is what I saw:
For some reason, it does not want to assign the WAN. Any idea, what could be the problem here?
I recommend using the WEB interface to configure the device.
Updating subversions is also easily done through the WEB interface.
Upgrading from version 21 to 22 is a big step as we move from HBSD to FreeBSD.
I don’t have usage statistics yet.
But I think that a simple upgrade from 21.7.6 to 22.1.6 through the WEB interface should be successful. Since you had 21.7.5 - it’s hard for me to predict the result.
The web interface shows, that WAN is assigned, but the console shows it is not. Also the dashboard shows it is not connected. What is also strange, the WAN port (on the device) is not showing any activity, the leds are not blinking, like when it would not be connected. I think, somehow the OS did not recognize it correctly.
When I check the ifconfig, it is saying no carrier.
And why you think, that the update will work if the vanilla install was not? I’ll try, but frankly I don’t believe … To do the update, I need to select the OpnSense for aarch64, right?
Great, the in-place upgrade worked! Thanks! Now I understand, why you thought it will work; the OS is the key as in this case was not updated.
Thanks a lot for your help guys!
Hi guys,
Should the USB port (type A) working on RockPi with the opnSense image? I’ve connected an UPS which was working on my RPI and it seems, that rockpi does not recognize the device.
@SleepWalker leepWalker @spikerguy do you have any thoughts on the above issue? Would be very good if I could use my opnsense as nuts master
Thanks!
Must work.
You can check for USB FLASH?
Hello,
I’m stuck with the new version of the ROCK PI E with the RTL8211F PHY chip.
I can’t get it work correctly, the bandwith suck and there is massive packet loss.
I updated the DTB to integrate the patch for RTL8211F timing (delay, tx and rx) (dtb missing by the way in the 22.1.9) but U-boot still use the old values and even I modify the FDT in U-boot console, the result is the same. The interface is not usable as is.
I assume I must update the bootaa64.efi file but despite my research, I don’t know how.
Could someone help me plz.
Thx.
The easiest way to substitute custom dtb is to substitute it for Mainline u-boot.
To do this, it must be written to the efi partition in the dtb/rockchip directory. For example so.
xzcat -T0 OPNsense-22.1.9-OpenSSL-aarch64-Rock-Pi-E-20220626.img.xz > rock-pi-e.img
mdconfig rock-pi-e.img
mount_msdosfs /dev/md0p1 /mnt
cp rk3328-rock-pi-e.dtb /mnt/dtb/rockchip/rk3328-rock-pi-e.dtb
sync; sync
umount /mnt
mdconfig -d -u 0
But it is better to test not on OPNsense but on FreeBSD.
You can see low Ethernet speed in OPNsense because the traffic is going through a packet filter and since it is single threaded you see low speed.
Test on FreeBSD.
