My recent experiences with ftp.ietf.org:
EPSV doesn't work - it gives a port which it then isn't listening on
(or, more likely since we get no response at all, a firewall blocks
connections to):
ftp ls
--- EPSV
229 Entering Extended Passive Mode (|||42065|)
ftp: connect for data channel:
PROTECTED]; ietf Mailing List
Subject: Re: IETF IPv6 platform configuration
My recent experiences with ftp.ietf.org:
EPSV doesn't work - it gives a port which it then isn't listening on
(or, more likely since we get no response at all, a firewall blocks
connections to):
ftp ls
--- EPSV
229 Entering
On Thursday, July 06, 2006 10:45:52 AM -0400 Bill Fenner
[EMAIL PROTECTED] wrote:
It looks like 3 out of 4 data channel establishment mechanisms
are broken with this FTP server software and configuration for
IPv4. I didn't test with IPv6.
I did, inadvertently. PASV worked, as did at
Just for completeness, I configured 6to4 to get IPv6 working.
Both EPSV and EPRT work with IPv6.
ftp ls
--- EPSV
229 Entering Extended Passive Mode (|||10283|)
--- LIST
150 Here comes the directory listing.
drwxrwxr-x 265 6060 48 8192 May 05 15:12
concluded-wg-ietf-mail-archive
On Jun 11, 2006, at 20:00, IETF Secretariat wrote:
All,
As you’re all aware, on 06/06/06 NSS successfully launched IPv6
services for
IETF Web, Mail, and FTP.
Has anyone had FTP work for them when not in passive mode since
this configuration change was made?
My site's got a clunky old
List ietf@ietf.org
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 05, 2006 3:55 PM
Subject: Re: IETF IPv6 platform configuration
On Jun 11, 2006, at 20:00, IETF Secretariat wrote:
All,
As you’re all aware, on 06/06/06 NSS successfully launched IPv6
services for
IETF Web, Mail, and FTP.
Has
Mailing List
Cc: [EMAIL PROTECTED]
Subject: Re: IETF IPv6 platform configuration
On Jun 11, 2006, at 20:00, IETF Secretariat wrote:
All,
As you’re all aware, on 06/06/06 NSS successfully launched IPv6
services for IETF Web, Mail, and FTP.
Has anyone had FTP work for them when
PROTECTED]
Subject: RE: IETF IPv6 platform configuration
If memory serves me right there is a subway terminal built
into the foundation of the Delta International. Where the
other end of the subway goes is another matter.
-Original Message-
From: Ken Raeburn [mailto:[EMAIL PROTECTED
Sent: Wednesday, July 05, 2006 3:52 PM
To: 'Ken Raeburn'; ietf Mailing List
Cc: [EMAIL PROTECTED]
Subject: RE: IETF IPv6 platform configuration
If memory serves me right there is a subway terminal built
into the foundation of the Delta International. Where the
other end of the subway goes
Secretariat.
-Original Message-
From: Joe Touch [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 15, 2006 11:56 AM
To: Iljitsch van Beijnum
Cc: [EMAIL PROTECTED]; Mark Andrews; ietf@ietf.org
Subject: Re: IETF IPv6 platform
On 15-jun-2006, at 1:51, Mark Andrews wrote:
* Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6
Native firewall (pings, traceroutes etc. are dropped)
Why? Shouldn't we be prompting good firewall practices?
Droping ICMP was a knee jerk
Iljitsch van Beijnum wrote:
On 15-jun-2006, at 1:51, Mark Andrews wrote:
*Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6
Native firewall (pings, traceroutes etc. are dropped)
Why? Shouldn't we be prompting good firewall practices?
Droping
. In addition,
NSS is in the process of providing statistics on IPv4 vs. IPv6 that will be
posted on the IETF website.
IETF IPv6 platform configuration
* The IPv6 access to and from IETF is tunneled from a local edge router
over IPv4 to a global Internet2 backbone.
* All
* Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6
Native firewall (pings, traceroutes etc. are dropped)
Why? Shouldn't we be prompting good firewall practices?
Droping ICMP was a knee jerk reaction to ICMP echo to
directed broadcast
secIETF == IETF Secretariat [EMAIL PROTECTED] writes:
secIETF * Only HTTP, SMTP, FTP, and DNS traffic are permitted through an
IPv6
secIETF Native firewall (pings, traceroutes etc. are dropped)
Please make sure that ICMP messages needed for path MTU discovery are
not
Sam Hartman wrote:
secIETF == IETF Secretariat [EMAIL PROTECTED] writes:
secIETF * Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6
secIETF Native firewall (pings, traceroutes etc. are dropped)
Please make sure that ICMP messages needed for path MTU
On Mon, 12 Jun 2006, Kevin Loch wrote:
Sam Hartman wrote:
secIETF == IETF Secretariat [EMAIL PROTECTED] writes:
secIETF * Only HTTP, SMTP, FTP, and DNS traffic are permitted
through an IPv6 secIETF Native firewall (pings, traceroutes
etc. are dropped)
Please make sure that
Kevin Loch wrote:
Sam Hartman wrote:
secIETF == IETF Secretariat [EMAIL PROTECTED] writes:
secIETF *Only HTTP, SMTP, FTP, and DNS traffic are permitted
through an IPv6 secIETF Native firewall (pings,
traceroutes etc. are dropped)
Please make sure that ICMP messages
18 matches
Mail list logo
