Messages

Anyone here have experience on the given subject?

I've been looking for a 10G capable router and came up with a few options. My go-to pick (https://www.aliexpress.com/item/1005006152906369.html?algo_exp_id=d8421ce0-c78e-4c54-8d6f-2d89233de121-3&pdp_npi=4%40dis%21EUR%21799.00%21559.3%21%21%21799.00%21%21%402101c59116994502417361713e1abd%2112000036003683813%21sea%21FI%211621031731%21&curPageLogUid=sA62A9GurPWX, sorry for that abysmal link) for now is based on a Intel i5 1240P which has a 4P+8E-core layout. Has anyone here tested such CPUs with OPNsense? I'm mostly interested in the stability of the performance since there is quite a big performance gap between P and E cores.

This problem will probably be fixed in the future once FreeBSD updates the scheduler. There is also current "fix" to run OPNsense virtualized and point the specific higher performance cores to the VM. Third option would be to disable the E-cores, but this implementation seems a bit broken in the BIOS and results in limited performance with P-cores.

I recently changed my LAN address range from 192.168.x.x to 10.10.x.x based. After the swap I started having problems with DNS resolution in my VLANs. Before the change I did not need any firewall rules or DHCP DNS settings to get resolution on other VLANs, but now I need to set DNS server on VLAN DHCP settings to get any resolution.

This ofcourse is not a huge problem, but I just find it odd and figured that there is maybe something misconfigured in my setup. There is probably some setting that is causing this but I can't find it. Any advice on where to look?

E: I'm using Adguard and routing DNS over TLS with Unbound. The setup is basically the same as in here https://forum.opnsense.org/index.php?topic=22162.msg106715#msg106715

E2: Solved, I forgot to select all VLANs in DNS Listen Interfaces dropdown. Reconfigured and seems to be working as earlier now.