I have a bit of a unique setup. I have two pfsense firewalls using CARP with a NAT entry for iSCSI port 3260 pointing to the NAS server. To make use of the BACKUP router, I set DNS for nasmydomaincom to point to the BACKUP router real IP address. This has worked for a long time to my old FreeNAS server, I can discover the NAS targets and all traffic goes through that router. However, when I update the NAT entry pointing to the TrueNAS scale I have setup now will not discover. If I also add a rule to allow or come from a trusted source where all ports are open, it works, but all traffic goes through the MASTER and not the BACKUP router.
I did some poking around with iscsiadm connecting from a Linux server and found what I believe is the issue. The TrueNAS server is returning the IP address of the hostname instead of the hostname I connect to. The hostname of the FreeNAS server is nas1mydomaincom and the hostname of the TrueNAS server is nas3mydomaincom.
If I discover the FreeNAS server…
# iscsiadm --mode discovery --type sendtargets --portal nas<dot>mydomain<dot>com --discover
nas<dot>mydomain<dot>com:3260,-1 iqn.2018-06.com<dot>mydomain<dot>nas1:mytarget
However, if I connect to the TrueNAS scale server…
# iscsiadm --mode discovery --type sendtargets --portal nas<dot>mydomain<dot>com --discover
<IP address>:3260,1 iqn.2005-01.com<dot>mydomain<dot>nas3:mytarget
Since it returns the IP address, that routes all back to the MASTER CARP router. Is there a way I can configure the TrueNAS server to discover targets in the same way as the FreeNAS? I don’t recall doing anything to the FreeNAS server to accomplish this, but it has been a very long time working.
P.S. - seems I need to use in my post for it thinks I have links in the post and produces an error.