RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1206868 - targetcli presents improperly formatted ipv6 addresses over the wire
Summary: targetcli presents improperly formatted ipv6 addresses over the wire
Keywords:
Status: CLOSED DUPLICATE of bug 1136558
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Andy Grover
QA Contact: Bruno Goncalves
URL:
Whiteboard:
Depends On: 1136558
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-29 04:25 UTC by Kyle Brantley
Modified: 2021-09-06 13:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-21 16:00:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of the MS iscsi initiator displaying the portal information (7.12 KB, image/png)
2015-03-29 04:25 UTC, Kyle Brantley 		no flags Details
View All

Description Kyle Brantley 2015-03-29 04:25:20 UTC 
Created attachment 1007903 [details]
screenshot of the MS iscsi initiator displaying the portal information

(or, at a minimum, "addresses are being formatted in a way not properly interpreted by the stock windows iscsi client". Additionally, I'm not sure if the appropriate component is targetcli or kernel.)

Description of problem:

Once an IPv6 addresses is added to a portal, it's presented over the network without the appropriate square braces surrounding the address. This causes a fair bit of confusion within the windows iSCSI client, and results in being unable to connect to the target.


Version-Release number of selected component (if applicable):
kernel-3.10.0-123.20.1.el7.x86_64
targetcli-2.1.fb34-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Add a new IPv6 portal to an iSCSI target.
2. Attempt to connect to the target via the stock windows iSCSI initiator.

Actual results:
The address is parsed improperly due to address encoding ambiguity, and no connection can be established.

Expected results:
iSCSI connectivity.

Additional info:
Over the wire, the TargetAddress is being sent with a value of: 2001:470:0:0:0:0:0:1:3260,1
Note the lack of square braces around the address. This causes confusion within the MS iSCSI client, which accepts '2001' as the hostname or IP address, and '470' as the port number.

To remove this ambiguity, the TargetAddress likely should be sent across the wire with a value of: [2001:470:0:0:0:0:0:1]:3260,1
Comment 2 Kyle Brantley 2015-03-29 20:33:51 UTC 
Simple case guaranteeing ambiguity:

/iscsi/iqn.20.../tpg1/portals> create ip_address=2001:470::1
Using default IP port 3260
Created network portal 2001:470::1:3260.

Over the wire, this is sent as "2001:470::1:3260" -- which could be interpreted as an IP address of 2001:470::1 and port 3260, or as IP address 2001:470::1:3260 without a port number.
Comment 3 Andy Grover 2015-03-31 22:07:28 UTC 
fix created and posted upstream
Comment 4 Andy Grover 2015-04-01 19:36:31 UTC 
fix accepted. We'll pull this in in the lio rebase for 7.2, see bug 1136558.
Comment 5 Andy Grover 2015-07-21 16:00:33 UTC 

*** This bug has been marked as a duplicate of bug 1136558 ***
Note You need to log in before you can comment on or make changes to this bug.