public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sivaraman Nainar" <sivaramann@amiindia.co.in>
To: "Rabeda, Maciej" <maciej.rabeda@linux.intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] TCP Port for ISCSI Connection
Date: Tue, 1 Sep 2020 14:49:15 +0000	[thread overview]
Message-ID: <B4DE137BDB63634BAC03BD9DE765F19702B4B466B5@VENUS1.in.megatrends.com> (raw)
In-Reply-To: <c716092b-8356-3f42-a5db-fc0904d00d93@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3587 bytes --]

Maciej,

Thanks for the clarification. I agree with you.

-Siva
From: Rabeda, Maciej [mailto:maciej.rabeda@linux.intel.com]
Sent: Tuesday, September 1, 2020 8:12 PM
To: Sivaraman Nainar; devel@edk2.groups.io
Subject: Re: [edk2-devel] TCP Port for ISCSI Connection

Siva,

iSCSI targets can be configured to listen on any TCP port.
Changing the UEFI iSCSI Client's TargetPort min/max will effectively prevent the user from communicating with the targets configured to listen on ports outside that range (in your example: below 1024).
I do not see a reason behind removing that flexibility. If user sets iSCSI target and client ports to values shared by other services, it is that user's mistake.

Thanks,
Maciej
On 01-Sep-20 16:31, Sivaraman Nainar wrote:
Hello Maciej:

The ports numbers from 0 to 1023 are having specific roles.

Ex: 80 for HTTTP, 443 for HTTPS.

In the case can we set Min as 1024 and Max as 65535.

Thanks
Siva
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> [mailto:devel@edk2.groups.io] On Behalf Of Maciej Rabeda
Sent: Tuesday, September 1, 2020 7:32 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Sivaraman Nainar
Subject: Re: [edk2-devel] TCP Port for ISCSI Connection

Hi Siva,

What seems to be the problem at hand? What kind of range of values for TargetPort do you propose?
TARGET_PORT_MIN/MAX_NUM refer to a range of values (0-65535) that be set in TargetPort field in iSCSI HII. 3260 is a default TCP port for iSCSI.
I see nothing wrong with that.

Thanks,
Maciej
On 31-Aug-20 11:05, Sivaraman Nainar wrote:
Rabeda:

Could you please provide your comment on this.

-Siva
From: Sivaraman Nainar
Sent: Tuesday, July 28, 2020 12:15 PM
To: jiaxin.wu@intel.com<mailto:jiaxin.wu@intel.com>
Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: TCP Port for ISCSI Connection

Jiaxin:

Can you please comment on the below query.

-Siva
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> [mailto:devel@edk2.groups.io] On Behalf Of Sivaraman Nainar
Sent: Friday, July 17, 2020 5:39 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: jiaxin.wu@intel.com<mailto:jiaxin.wu@intel.com>
Subject: [edk2-devel] Reg: TCP Port for ISCSI Connection

Hello all:

In the ISCSI driver, Target TCP Port Input shows the default port as 3260. Which can be set from 0 to 65535

As per below RFC it talks about the Default Port only. Still it not clearly said if we can use the numbers 49152-65535 which is reserved.
https://tools.ietf.org/html/rfc3720

13. IANA Considerations

This section conforms to [RFC2434].

The well-known user TCP port number for iSCSI connections assigned by
IANA is 3260 and this is the default iSCSI port. Implementations
needing a system TCP port number may use port 860, the port assigned
by IANA as the iSCSI system port; however in order to use port 860,
it MUST be explicitly specified - implementations MUST NOT default to
use of port 860, as 3260 is the only allowed default.

with my understanding, it wouid be good if we can change the below Min and  MAX port number ranges with right ranges.

#define TARGET_PORT_MIN_NUM       0
#define TARGET_PORT_MAX_NUM       65535

Thanks
Siva
This e-mail is intended for the use of the addressee only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.




[-- Attachment #2: Type: text/html, Size: 11515 bytes --]

      reply	other threads:[~2020-09-01 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16228C0E194D8DF1.2727@groups.io>
2020-07-28  6:45 ` TCP Port for ISCSI Connection Sivaraman Nainar
2020-08-31  9:05 ` Sivaraman Nainar
2020-09-01 14:01   ` [edk2-devel] " Maciej Rabeda
2020-09-01 14:31     ` Sivaraman Nainar
2020-09-01 14:41       ` Maciej Rabeda
2020-09-01 14:49         ` Sivaraman Nainar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B4DE137BDB63634BAC03BD9DE765F19702B4B466B5@VENUS1.in.megatrends.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox