Messages

I'll close up this topic as solved. System is running for almost 7 days without any problem. Was it update (from F2) to BIOS F3 or manually configuring OPNSense? I'll never know but never the less I'm happy.

Currently system is running 24hours. I've updated system with latest BIOS F3 from Changwang website (link above). Also reconfigured entire system through GUI. VLAN with IPS in Promiscious mode works. Only can't get Acme Client to work but it's offtopic. So far so good...

I'm wondering the same. Can't find info on how to add DNS-provider, which is available on Acme Github, to OPNsense. I would like to add DNSExit https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_dnsexit.sh

I believe I found a link to BIOS which isn't dead (as we speak); https://pan.x86pi.cn/BIOS%E6%9B%B4%E6%96%B0/1.Intel%E8%BF%B7%E4%BD%A0%E4%B8%BB%E6%9C%BA%E7%B3%BB%E5%88%97BIOS

Before you download X86-XP2 be aware of different versions. J4125 seems to be other file than N4000/J4105. I'm going to try if this BIOS solves something.

Nope! Next try (when summer conditions will disappear) will be reconfiguring new system from GUI 1 by 1 instead of copy-pasting XML.

Helllloooo... anybody....heeerreee? :)

@pmhausen do you think it would be that simple? Would be nice one. I'm using a quality Seasonic Power supply. Used it for years without any problems because I wouldn't have problems. Also did the stress testing CPU with it in Manjaro system hit 70 degrees temp max. I believe it's than throttled by Firmware.

I'll search for some other PSU laying around but think that one is an El Cheapo though. See if thermal throttling can be upped or disabled. Passive radiator casing doesn't get really warm though.
EDIT

El Cheapo PSU and original Seasonic PSU no difference. Only booting is now new issue;

All buffer synced...
Uptime XYZ

Did it crash?

Hi,

Few months ago I bought a X86-P2 mini system at Loksing https://www.loksing.com.cn/products/x86-p2-software-route-n4000-j4105-j4125-mini-host-6w-low-power-consumption-quad-core-quad-thread-intelligent-hardware-fanless-energy-saving-microcomputer-computer. I believe this thing is sold by various other companies under different names. Anyways....


This piece of equipment keeps shutting down. It shows script "beep" and script "freebsd" out of the blue and shuts down. Initially I manually changed NIC's in config.xml from old system to correspond to new igc driver and installed with installer. Shut down within dozen minutes or so. Then new install and started to modify config.xml functionality by functionality. So first vlan, then dhcp, then firewall rules and NAT and so on. Also updated system to latest 23.1.8 version but systems shuts down after 1.5hours to 4 hours.

Because I read various topics about I226-V problems I also created a loader.conf.local;

Code Select Expand


hw.acpi.cpu.cx_lowest="C1"
hw.ibrs_disable="1"
hw.igc.rx_process_limit="-1"
hw.igc.max_interrupt_rate="8000"
hw.igc.eee_setting="1"
hw.igc.sbp="1"
hw.igc.smart_pwr_down="0"
hw.igc.rx_abs_int_delay="66"
hw.igc.tx_abs_int_delay="66"
hw.igc.rx_int_delay="0"
hw.igc.tx_int_delay="66"
hw.igc.disable_crc_stripping="0"


The piece of @#%#$ keeps shutting down. And Yep all settings related to hardware offloading and VLAN filtering have been disabled through GUI. System runs ZFS file system without swap. I've tested Memory with Memtest 86+=4 days 0 errors, used Stress for CPU, Mem and IO through Manjaro USB stick= 2 days no problems. So seems to me not hardware related.

How can I log or see what the culprit is?

I've got same problem. I bought a Loksing X86-P2 mini PC 5; CPU Intel J4125 with NICS Intel I226-V with Samsung NVME running (latest) OPNsense 23.1.5_4. I've configured VLAN, IPS in Promiscious Mode.

Monitor just goes blank or see a shutdown with various services shutting down and even speaker beep. It happens after 10 minutes, 3 hours or within couple of seconds.

As suggested I've done a rollback to previous kernel. It doesn't make any difference.

Thanks a lot for your edit. It took me several hours to figure out. Your comments got it up and running within 1 minute. Thanks!

@stefanpf Thanks a lot! It works great  :)

Maybe for someone else comes in handy; Add to field "Custom options";

Code Select Expand


#Access control for remote IP Range
access-control-view: 192.168.130.128/25 bridgelan
access-control-view: 192.168.131.128/29 wirelessguest
access-control-view: 192.168.132.1/24 bridgeiot
access-control-view: 192.168.133.128/29 dmz

#View to return for external range only defined ip for firewall, assumed 192.168.100.254 is the IP of opnsense
view:
    name: "bridgelan"
    local-zone: "myradon.net" transparent
    local-data: "opnsense.myradon.net A 192.168.130.129"
    local-data: "opnsense A 192.168.130.129"
    #view-first Unbound will try to use the view's local-zone tree, and if there is no match it will search the global tree.
    view-first: yes

view:
    name: "wirelessguest"
    local-zone: "myradon.net" transparent
    local-data: "opnsense.myradon.net A 192.168.131.129"
    local-data: "opnsense A 192.168.131.129"
    #view-first Unbound will try to use the view's local-zone tree, and if there is no match it will search the global tree.
    view-first: yes

view:
    name: "bridgeiot"
    local-zone: "myradon.net" transparent
    local-data: "opnsense.myradon.net A 192.168.132.1"
    local-data: "opnsense A 192.168.132.1"
    #view-first Unbound will try to use the view's local-zone tree, and if there is no match it will search the global tree.
    view-first: yes

view:
    name: "dmz"
    local-zone: "myradon.net" transparent
    local-data: "opnsense.myradon.net A 192.168.133.129"
    local-data: "opnsense A 192.168.133.129"
    #view-first Unbound will try to use the view's local-zone tree, and if there is no match it will search the global tree.
    view-first: yes


Hi guys,

I moved from pfSense to OPNsense. Was on my list forever and now was the time cause there is a huge bug in pfSense 2.4.5 since several weeks that makes it totally unresponsive. That said;

I have setup Unbound and it works But have a big problem with the returned results for querying OPNsense itself. My system has 4 different subnets. When a client queries FQDN of OPNsense it returns all records of all interfaces. Now first record is other subnet so it doesn't work/ is very slow. When I configure Unbound to only listen on interface the client-computer is one it off course works.

The results;

Code Select Expand

mercury:~ raymond$ sudo killall -HUP mDNSResponder
mercury:~ raymond$ nslookup opnsense
Server: 192.168.130.129
Address: 192.168.130.129#53
Name: opnsense.myradon.net
Address: 192.168.132.1
Name: opnsense.myradon.net
Address: 192.168.130.129
Name: opnsense.myradon.net
Address: 192.168.133.129
Name: opnsense.myradon.net
Address: 192.168.131.129


How can I configure Unbound it returns only the A-record on the interface query is coming from?