unable to select specific IP address for iSCSI portal
Description
Problem/Justification
None
Impact
None
Activity
Show:

Stuart Espey March 4, 2025 at 5:23 AM
thankyou, I can confirm that was the issue.
I was using a static dhcp assignment, rather than an IP Alias.

Bug Clerk March 3, 2025 at 10:21 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Bug Clerk March 3, 2025 at 10:21 PM
An interface with a DHCP address is not a suitable candidate here. If you wish to restrict to a specific address please set a static IP (and ensure alias is set).

Bonnie Follweiler March 3, 2025 at 9:49 PM
Hello
I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.
Not Applicable
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee

Reporter

Components
Fix versions
Affects versions
Priority

More fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created March 3, 2025 at 5:47 AM
Updated March 4, 2025 at 5:23 AM
Resolved March 3, 2025 at 10:21 PM
In the Portal setting I am unable to select any specific IP address, other than "0.0.0.0" or "::",
This means that I can't set a Portal to a specific IP address, and instead the iSCSI daemon will bind to all adresses.
Here is an example iscsiadm discovery session illustrating that iscsi is being served on both the primary interface (192.168.0.32) and the internal incus network
```
stux@incusdev:~/git/truenas_incus_ctl$ sudo iscsiadm -m discovery -t st -p fangtooth
192.168.0.32:3260,1 iqn.2005-10.org.freenas.ctl::target1
10.52.191.1:3260,1 iqn.2005-10.org.freenas.ctl:target1
```
ie, 10.52.191.1 is the "IPv4 Network" configured in the Global Settings for Instances.
Session ID: 82068ea4-64e9-2edf-b650-a19bdbe4140d