



Quote from: Patrick M. Hausen on December 27, 2025, 05:26:26 PMTrueNAS does not support policy routing so if you have network interfaces in different networks it will always answer any client fromWhat is TrueNAS based on these days ?!
- the directly connected one, if present
- the one with the default gateway, otherwise
Specifically there is no separation of the UI and the file sharing services. Not possible, don't try it, you will fail.
Quote from: Patrick M. Hausen on December 28, 2025, 10:30:30 AMYou can bind different services to different interfaces, of course. But if your management desktop and TN share a common network and you define "management" to be a different one to be accessed through a firewall, TN will send the replies through the common network bypassing the firewall, because that's how routing works.I had that issue (A-Symmetrical Routing blocked by the OPNsense Default Block Rule) after switching from my old Ubiquiti USG 3P Router to OPNsense and solved it via SystemD Network Configuration for :
QuoteA separate storage network for e.g. iSCSI assumes that all clients and the TN server share that network, so no asymmetric routing occurs. That of course is perfectly reasonable. Same for e.g. NFS for VMware.As long as you keep things 1:1 connected in the same subnet there are no issues indeed :)
QuoteBut placing mangement in a separate network does not work unless the management station is in that same network. Just like with the storage examples.Unless you can manipulate the Routing Table on the device you are accessing ofcourse!
Quote from: OPNenthu on December 29, 2025, 11:27:32 PMit seems I may have misjudged the AQC113 NIC earlier.I hope so too for you, because I have just read your other topic about the NIC and I am really disappointed that the driver support is not all that great/how it should be or could have been...
Look like the AQC113 is so far not falling down :)
Hope this keeps up.
Quote from: franco on December 22, 2025, 08:10:28 AMYou're not posting your update attempt logs here either. I'm not sure how to help in that case other than give moral rubber duck support. ;)
Cheers,
Franco
Type opnsense
Version 25.7.10
Architecture amd64
Commit c2f076f30
Mirror https://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:14:amd64/25.7
Repositories OPNsense (Priority: 11)
Updated on Fri Dec 19 17:20:40 AEST 2025
Checked on Tue Dec 30 08:22:05 AEST 2025
Version Date
25.7.10 (installed) 2025-12-18
25.7.9 2025-12-04
***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 25.7.10 (amd64) at Tue Dec 30 09:00:56 AEST 2025
Fetching changelog information, please wait... fetch: transfer timed out
fetch: /usr/local/opnsense/changelog/changelog.txz appears to be truncated: 0/195380 bytes
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 928 packages processed.
All repositories are up to date.
Checking for upgrades (82 candidates): .......... done
Processing candidates (82 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Package name Current version New version Required action Repository
base 25.7.8 25.7.10 upgrade OPNsense
kernel 25.7.8 25.7.10 upgrade OPNsense