Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Netapp: toasters

Netapp SDK -- HTTP Port 1023

 

 

Netapp toasters RSS feed   Index | Next | Previous | View Threaded


Jochen.Willeke at wincor-nixdorf

Jun 22, 2009, 5:59 AM

Post #1 of 4 (1232 views)
Permalink
Netapp SDK -- HTTP Port 1023

Hi toasters,

we are in the need to use the netapp SDK through a firewall. While
trying this we found out, that the SDK uses TCP Port 1023 as the source
port. Sadly our firewall defines HTTP source-ports from 1024-upward and
therefore denies the transit :(

Has anybody came across this issue and has an idea if this behavior can
be changed?

Best Regards and thanks in advance

Jochen Willeke

--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Stefan.Funke at netapp

Jun 23, 2009, 1:57 AM

Post #2 of 4 (1124 views)
Permalink
RE: Netapp SDK -- HTTP Port 1023 [In reply to]

Hi Jochen!

I've been playing with manage-ontap-SDK-3.5P1 to test that. I used modified perl samples (manage-ontap-sdk-3.5P1/src/sample/perl) to monitor ports used while connecting to the storage controller and never got a source port <1023.

However, if you look at the libraries you'll find something like:

#
# If we are being asked to use a reserved port (we
# are doing hosts.equiv authentication), then we search to
# find an available port number below 1024.
#
if ( $self->get_style() eq "HOSTS" ) {
my $lowport;
for ($lowport=1023; $lowport > 0; $lowport--) {
$thisport=pack($sockaddr, &AF_INET,$lowport);
if (bind(S,$thisport)) {
last;
}

So I guess you are using hosts.equiv based authentication against the storage controller. To ensure that only root can authenticate as a 'host', ports <1024 are a good way to enforce that. Switching to a user/password authentication model could be a fast workaround. Changing the background functions of the API could be another way.

-Stefan





-----Original Message-----
From: Willeke, Jochen [mailto:Jochen.Willeke[at]wincor-nixdorf.com]
Sent: 22 June 2009 14:59
To: toasters[at]mathworks.com
Subject: Netapp SDK -- HTTP Port 1023

Hi toasters,

we are in the need to use the netapp SDK through a firewall. While
trying this we found out, that the SDK uses TCP Port 1023 as the source
port. Sadly our firewall defines HTTP source-ports from 1024-upward and
therefore denies the transit :(

Has anybody came across this issue and has an idea if this behavior can
be changed?

Best Regards and thanks in advance

Jochen Willeke

--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Stefan.Funke at netapp

Jun 23, 2009, 4:24 AM

Post #3 of 4 (1119 views)
Permalink
RE: Netapp SDK -- HTTP Port 1023 [In reply to]

Jochen,

I see that this has been discussed before. Maybe you want to follow/re-open this thread on NetApp Communities:
http://communities.netapp.com/message/4679


-Stefan

-----Original Message-----
From: Funke, Stefan
Sent: 23 June 2009 10:58
To: Willeke, Jochen; toasters[at]mathworks.com
Subject: RE: Netapp SDK -- HTTP Port 1023

Hi Jochen!

I've been playing with manage-ontap-SDK-3.5P1 to test that. I used modified perl samples (manage-ontap-sdk-3.5P1/src/sample/perl) to monitor ports used while connecting to the storage controller and never got a source port <1023.

However, if you look at the libraries you'll find something like:

#
# If we are being asked to use a reserved port (we
# are doing hosts.equiv authentication), then we search to
# find an available port number below 1024.
#
if ( $self->get_style() eq "HOSTS" ) {
my $lowport;
for ($lowport=1023; $lowport > 0; $lowport--) {
$thisport=pack($sockaddr, &AF_INET,$lowport);
if (bind(S,$thisport)) {
last;
}

So I guess you are using hosts.equiv based authentication against the storage controller. To ensure that only root can authenticate as a 'host', ports <1024 are a good way to enforce that. Switching to a user/password authentication model could be a fast workaround. Changing the background functions of the API could be another way.

-Stefan





-----Original Message-----
From: Willeke, Jochen [mailto:Jochen.Willeke[at]wincor-nixdorf.com]
Sent: 22 June 2009 14:59
To: toasters[at]mathworks.com
Subject: Netapp SDK -- HTTP Port 1023

Hi toasters,

we are in the need to use the netapp SDK through a firewall. While
trying this we found out, that the SDK uses TCP Port 1023 as the source
port. Sadly our firewall defines HTTP source-ports from 1024-upward and
therefore denies the transit :(

Has anybody came across this issue and has an idea if this behavior can
be changed?

Best Regards and thanks in advance

Jochen Willeke

--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


Jochen.Willeke at wincor-nixdorf

Jul 2, 2009, 12:11 AM

Post #4 of 4 (1005 views)
Permalink
RE: Netapp SDK -- HTTP Port 1023 [In reply to]

Hi,

sorry for the late reply. But that was the point.

When using hosts.equiv-security-style the sourceport will be from 1023 - downwards.

Regards and thanks

Jochen

-----Original Message-----
From: Funke, Stefan [mailto:Stefan.Funke[at]netapp.com]
Sent: Tuesday, June 23, 2009 10:58 AM
To: Willeke, Jochen; toasters[at]mathworks.com
Subject: RE: Netapp SDK -- HTTP Port 1023

Hi Jochen!

I've been playing with manage-ontap-SDK-3.5P1 to test that. I used modified perl samples (manage-ontap-sdk-3.5P1/src/sample/perl) to monitor ports used while connecting to the storage controller and never got a source port <1023.

However, if you look at the libraries you'll find something like:

#
# If we are being asked to use a reserved port (we
# are doing hosts.equiv authentication), then we search to
# find an available port number below 1024.
#
if ( $self->get_style() eq "HOSTS" ) {
my $lowport;
for ($lowport=1023; $lowport > 0; $lowport--) {
$thisport=pack($sockaddr, &AF_INET,$lowport);
if (bind(S,$thisport)) {
last;
}

So I guess you are using hosts.equiv based authentication against the storage controller. To ensure that only root can authenticate as a 'host', ports <1024 are a good way to enforce that. Switching to a user/password authentication model could be a fast workaround. Changing the background functions of the API could be another way.

-Stefan





-----Original Message-----
From: Willeke, Jochen [mailto:Jochen.Willeke[at]wincor-nixdorf.com]
Sent: 22 June 2009 14:59
To: toasters[at]mathworks.com
Subject: Netapp SDK -- HTTP Port 1023

Hi toasters,

we are in the need to use the netapp SDK through a firewall. While
trying this we found out, that the SDK uses TCP Port 1023 as the source
port. Sadly our firewall defines HTTP source-ports from 1024-upward and
therefore denies the transit :(

Has anybody came across this issue and has an idea if this behavior can
be changed?

Best Regards and thanks in advance

Jochen Willeke

--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.



--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193

Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Netapp toasters RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.