2006-07-23 strange FTP problem - Revision history

Woozle: catg: tech notes

2007-04-17T01:44:19Z

catg: tech notes

← Older revision		Revision as of 01:44, 17 April 2007
Line 1:		Line 1:
	==Introduction==		==Introduction==
	[[Category:dated items]][[category:hypertwins network]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.		[[category:tech notes]][[Category:dated items]][[category:hypertwins network]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.
	==Status==		==Status==
	'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?		'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?

Woozle: catg: hypertwins net

2006-09-30T13:09:29Z

catg: hypertwins net

← Older revision		Revision as of 13:09, 30 September 2006
Line 1:		Line 1:
	==Introduction==		==Introduction==
	[[Category:dated items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.		[[Category:dated items]][[category:hypertwins network]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.
	==Status==		==Status==
	'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?		'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?

Woozle: Dated Items -> dated items

2006-08-15T14:23:27Z

Dated Items -> dated items

← Older revision		Revision as of 14:23, 15 August 2006
Line 1:		Line 1:
	==Introduction==		==Introduction==
	[[Category:~~Dated Items~~]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.		[[Category:dated items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.
	==Status==		==Status==
	'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?		'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?

Woozle: /* Status */ more questions

2006-07-25T18:53:02Z

Status: more questions

← Older revision		Revision as of 18:53, 25 July 2006
Line 2:		Line 2:
	[[Category:Dated Items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.		[[Category:Dated Items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.
	==Status==		==Status==
	'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router?		'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router? What is the difference between the way kio_ftp does ftp and the way everybody else seems to do it, which causes kio_ftp to fail under circumstances where other ftp clients seem to work fine? What is different about the one site which kio_ftp is totally unable to work with?

	==Description==		==Description==

Woozle: /* Introduction */ status: 7/25

2006-07-25T18:48:14Z

Introduction: status: 7/25

← Older revision		Revision as of 18:48, 25 July 2006
Line 1:		Line 1:
	==Introduction==		==Introduction==
	[[Category:Dated Items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.		[[Category:Dated Items]]I'm documenting this problem so that (a) if we manage to fix it, others with a similar problem may be able to benefit, and (b) if we don't manage to fix it, maybe someone else will be able to figure out what's going on.
			==Status==
			'''2006-07-25''' It's looking very much like some kind of network problem over on the host's side; awaiting resolution from the web hosting people. A few mysteries remain, like why does non-PASV mode work ''at all'', when we're operating from behind a NAT router?

	==Description==		==Description==
	Some [[file transfer protocol\|FTP]] clients can connect to a particular server, while others can't. Specifically, [[Konqueror]]'s ftp, which seems to use the kio_ftp [[kioslave]], cannot; [[CLI]]-based ftp can, and so can [[gFTP]].		Some [[file transfer protocol\|FTP]] clients can connect to a particular server, while others can't. Specifically, [[Konqueror]]'s ftp, which seems to use the kio_ftp [[kioslave]], cannot; [[CLI]]-based ftp can, and so can [[gFTP]].

Woozle: /* gFTP successful connect to proftp */ different servers - truth table

2006-07-25T15:37:44Z

gFTP successful connect to proftp: different servers - truth table

← Older revision		Revision as of 15:37, 25 July 2006
Line 220:		Line 220:
	405 8.383772 192.168.0.103 81.223.20.36 TCP 55520 > ftp [ACK] Seq=71 Ack=389 Win=5840 Len=0 TSV=61998062 TSER=179972435		405 8.383772 192.168.0.103 81.223.20.36 TCP 55520 > ftp [ACK] Seq=71 Ack=389 Win=5840 Len=0 TSV=61998062 TSER=179972435
	{{quoteoff}}		{{quoteoff}}
			==Different Servers==
			Comparison of web1 versus two other servers, trying 3 different FTP programs:
			{\|
			\|-
			\| \|\| colspan=2 \| web1 \|\| colspan=2 \| "fitness" \|\| colspan=2 \| "coachsucks"
			\|-
			\| '''FTP app''' \|\| PASV \|\| non \|\| PASV \|\| non \|\| PASV \|\| non
			\|-
			\| [[Konqueror]] \|\| n \|\| n \|\| {{hilite\|Y}} \|\| n \|\| {{hilite\|Y}} \|\| n
			\|-
			\| [[gFTP]] \|\| n \|\| {{hilite\|Y}} \|\| {{hilite\|Y}} \|\| n \|\| {{hilite\|Y}} \|\| {{hilite\|Y}}
			\|-
			\| {{linuxcmd\|ftp}} \|\| n \|\| {{hilite\|Y}} \|\| {{hilite\|Y}} \|\| n \|\| {{hilite\|Y}} \|\| {{hilite\|Y}}
			\|}

Woozle: /* Konq PASV successful connect to proftp */ gFTP successful connect to proftp

2006-07-23T18:26:22Z

Konq PASV successful connect to proftp: gFTP successful connect to proftp

@@ Line 183: / Line 183: @@
 6.259314    81.223.20.36          192.168.0.103         FTP      Response: 226 Transfer complete.
 6.263031    192.168.0.103         81.223.20.36          TCP      52636 > ftp [ACK] Seq=16 Ack=129 Win=1460 Len=0 TSV=59575189 TSER=177550671
 {{quoteoff}}

Woozle: /* Konq PASV successful connect to proftp */ highlight

2006-07-23T15:51:04Z

Konq PASV successful connect to proftp: highlight

← Older revision		Revision as of 15:51, 23 July 2006
Line 168:		Line 168:
	# Time Source Destination Protocol Info		# Time Source Destination Protocol Info
	346 5.404721 192.168.0.103 81.223.20.36 FTP Request: PASV		346 5.404721 192.168.0.103 81.223.20.36 FTP Request: PASV
	351 5.539531 81.223.20.36 192.168.0.103 FTP Response: 227 Entering Passive Mode (81,223,20,36,183,245).		{{hilite\|351 5.539531 81.223.20.36 192.168.0.103 FTP Response: 227 Entering Passive Mode (81,223,20,36,183,245).}}
	352 5.539651 192.168.0.103 81.223.20.36 TCP 52636 > ftp [ACK] Seq=6 Ack=51 Win=1460 Len=0 TSV=59575008 TSER=177550492		352 5.539651 192.168.0.103 81.223.20.36 TCP 52636 > ftp [ACK] Seq=6 Ack=51 Win=1460 Len=0 TSV=59575008 TSER=177550492
	353 5.540226 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [SYN] Seq=0 Len=0 MSS=1460 TSV=59575008 TSER=0 WS=2		353 5.540226 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [SYN] Seq=0 Len=0 MSS=1460 TSV=59575008 TSER=0 WS=2

Woozle: /* Konq PASV unsuccessful connect to web1 */ highlight

2006-07-23T15:50:43Z

Konq PASV unsuccessful connect to web1: highlight

← Older revision		Revision as of 15:50, 23 July 2006
Line 151:		Line 151:
	404 11.603639 192.168.0.103 69.57.190.146 TCP 49724 > ftp [ACK] Seq=85 Ack=257 Win=5840 Len=0		404 11.603639 192.168.0.103 69.57.190.146 TCP 49724 > ftp [ACK] Seq=85 Ack=257 Win=5840 Len=0
	405 11.603798 192.168.0.103 69.57.190.146 FTP Request: PASV		405 11.603798 192.168.0.103 69.57.190.146 FTP Request: PASV
	407 11.642731 69.57.190.146 192.168.0.103 FTP Response: 227 Entering Passive Mode (69,57,190,146,201,26).		{{hilite\|407 11.642731 69.57.190.146 192.168.0.103 FTP Response: 227 Entering Passive Mode (69,57,190,146,201,26).}}
	408 11.643373 192.168.0.103 69.57.190.146 TCP 37038 > 51482 [SYN] Seq=0 Len=0 MSS=1460 TSV=59633711 TSER=0 WS=2		408 11.643373 192.168.0.103 69.57.190.146 TCP 37038 > 51482 [SYN] Seq=0 Len=0 MSS=1460 TSV=59633711 TSER=0 WS=2
	409 11.680245 192.168.0.103 69.57.190.146 TCP 49724 > ftp [ACK] Seq=91 Ack=308 Win=5840 Len=0		409 11.680245 192.168.0.103 69.57.190.146 TCP 49724 > ftp [ACK] Seq=91 Ack=308 Win=5840 Len=0

Woozle: /* Konq PASV unsuccessful connect to web1 */ konq pasv successful connect to proftp

2006-07-23T15:48:33Z

Konq PASV unsuccessful connect to web1: konq pasv successful connect to proftp

← Older revision		Revision as of 15:48, 23 July 2006
Line 162:		Line 162:

	It looks like the connection runs into some sort of trouble after the PASV request is acknowledged, with SYN and RST requests going back and forth...		It looks like the connection runs into some sort of trouble after the PASV request is acknowledged, with SYN and RST requests going back and forth...

			===Konq PASV successful connect to proftp===
			This shows the highlights of a network capture (using [[ethereal (application)\|ethereal]]) of a successful connection to ftp.proftpd.org using Konqueror.
			{{quoteon}}
			# Time Source Destination Protocol Info
			346 5.404721 192.168.0.103 81.223.20.36 FTP Request: PASV
			351 5.539531 81.223.20.36 192.168.0.103 FTP Response: 227 Entering Passive Mode (81,223,20,36,183,245).
			352 5.539651 192.168.0.103 81.223.20.36 TCP 52636 > ftp [ACK] Seq=6 Ack=51 Win=1460 Len=0 TSV=59575008 TSER=177550492
			353 5.540226 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [SYN] Seq=0 Len=0 MSS=1460 TSV=59575008 TSER=0 WS=2
			357 5.678703 81.223.20.36 192.168.0.103 TCP 47093 > 38204 [SYN, ACK] Seq=0 Ack=1 Win=2965504 Len=0 MSS=1460 TSV=177550526 TSER=59575008 WS=9
			358 5.678762 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSV=59575042 TSER=177550526
			359 5.678987 192.168.0.103 81.223.20.36 FTP Request: list -la
			362 5.812019 81.223.20.36 192.168.0.103 FTP Response: 150 Opening ASCII mode data connection for file list
			363 5.812673 192.168.0.103 81.223.20.36 TCP 52636 > ftp [ACK] Seq=16 Ack=105 Win=1460 Len=0 TSV=59575076 TSER=177550559
			365 5.913310 81.223.20.36 192.168.0.103 FTP-DATA FTP Data: 395 bytes
			366 5.913361 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [ACK] Seq=1 Ack=396 Win=6912 Len=0 TSV=59575101 TSER=177550585
			367 5.913378 81.223.20.36 192.168.0.103 TCP 47093 > 38204 [FIN, ACK] Seq=396 Ack=1 Win=6144 Len=0 TSV=177550585 TSER=59575042
			368 5.913805 192.168.0.103 81.223.20.36 TCP 38204 > 47093 [FIN, ACK] Seq=1 Ack=397 Win=6912 Len=0 TSV=59575101 TSER=177550585
			373 6.040581 81.223.20.36 192.168.0.103 TCP 47093 > 38204 [ACK] Seq=397 Ack=2 Win=6144 Len=0 TSV=177550617 TSER=59575101
			390 6.259314 81.223.20.36 192.168.0.103 FTP Response: 226 Transfer complete.
			391 6.263031 192.168.0.103 81.223.20.36 TCP 52636 > ftp [ACK] Seq=16 Ack=129 Win=1460 Len=0 TSV=59575189 TSER=177550671
			{{quoteoff}}