To the lengthening list of files on my server, I have added the output of
strace -o strace.out -e trace=network ftp -u -n ftp.iglu.org.il
Upon an off-list suggestion. In this session, IGLU's reply to PASV has been
227 Entering Passive Mode (192,117,122,34,46,28)
Which indicates port
Well, it was solved very simply by installing the alternative kernel
that comes with Mandrake PPC (it's supposed to be a vanilla PPC tree
kernel). Now ftp works - in both PASV and PORT modes, with the
firewall up, and from both the gateway and the NAT.
I suspect a problem in the RELATED state
Quoting Shachar Shemesh [EMAIL PROTECTED]:
I'm afraid that this command line does not leave enough info in the
parsed output to say anything about the result. Can you please add a -w
filename to the command line, and then send (at least me) the file? In
the case of FTP, the content of the
On Tue, Jun 24, 2003 at 11:14:09AM +0300, Herouth Maoz wrote:
As a last resort you might consider doing some chroot installation of
Mandrake or some other Linux distribution. The intention is to get a
minimal Linux installation that would use the ADSL and have passive ftp
working without
On Tuesday 24 June 2003 11:14, Herouth Maoz wrote:
Quoting Shachar Shemesh [EMAIL PROTECTED]:
I'm afraid that this command line does not leave enough info in the
parsed output to say anything about the result. Can you please add a -w
filename to the command line, and then send (at least me)
At 18:35 +0300 on 24/6/2003, [EMAIL PROTECTED] wrote:
Hmm, it's a bit hard to see the sequence of commands in the packets - did you
use -s to increase the part of the packets which gets snapped? (-s 0
should capture the entire packet).
OK, I recreated the files. First, I added -s 0 to
Herouth Maoz wrote:
At 18:35 +0300 on 24/6/2003, [EMAIL PROTECTED] wrote:
OK, I recreated the files. First, I added -s 0 to tcpdump. Second, I
ran ftp with -u and -n. It appears the authentication information is
disabled by -u, and automatic login is disabled by -n. So it should
now be
At 22:43 +0300 on 24/6/2003, Shachar Shemesh wrote:
May I inquire what FTP client this is? It seems to be severely broken.
Your transcript says:
That's the basic ftp client, that comes with every unix system since
ftp was invented... Judging by the man page, it's based on the BSD4.2
client,
Herouth Maoz wrote:
At 22:43 +0300 on 24/6/2003, Shachar Shemesh wrote:
May I inquire what FTP client this is? It seems to be severely broken.
Your transcript says:
That's the basic ftp client, that comes with every unix system since
ftp was invented... Judging by the man page, it's based
Shachar Shemesh wrote:
I am without an explanation. The dump, as taken FROM THE MACHINE
ITSELF already shows no reason of working. Whatever the problem is, it
happens before the packets go out on the network.
On the other hand, the applications you use are well standard
applications, and
At 00:07 +0300 on 25/6/2003, Shachar Shemesh wrote:
Can you please try iptables -L -t nat?
Well, with the firewall up, it's:
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source
On Mon, 23 Jun 2003 00:42:01 +0300
Herouth Maoz [EMAIL PROTECTED] wrote:
I have a Linux machine with two network cards, which serves as the
NAT gateway. eth0 is connected to the hub, eth1 to the modem.
eth0 is set up static, 192.168.1.1.
eth1 is set up to use DHCP (to get the real IP from
First, thanks for all the suggestions
At 08:12 +0300 on 23/6/2003, Oron Peled wrote:
æ
æÝNo, the external interface should not have an IP! (it is documented
æÝsomewhere, forgot where). I have the same setup with the same ISP
æÝand modem (The following is from RedHat):
Oh, I wished that this would
Thanks, guys. Apparently the problem isn't with Actcom. My other
OS, using the same hardware, connects and allows passive ftp without
a problem.
So now I'm left with the question - what could cause PASV to fail? I
am not a networking expert, mind you. I tried replacing shorewall
with
On Sunday 22 June 2003 23:21, Herouth Maoz wrote:
Thanks, guys. Apparently the problem isn't with Actcom. My other
OS, using the same hardware, connects and allows passive ftp without
a problem.
So now I'm left with the question - what could cause PASV to fail?
I'm using a Samsung modem.
At 23:41 +0300 on 22/6/2003, Aviram Jenik wrote:
There's still not enough info about your network to really help you
out. Could
you explain your set up exactly? Are you using a NAT gateway machine or
connecting directly from the Linux? Did you make any MTU changes on your
other OS that you
On Mon, Jun 23, 2003 at 12:42:01AM +0300, Herouth Maoz wrote:
The part I got stuck in
was attempting to access security updates - that's done in passive
FTP.
Have you explicitly tried the passive command from within the ftp
program and got
At 02:07 +0300 on 23/6/2003, Shaul Karl wrote:
Have you explicitly tried the passive command from within the ftp
program and got stuck? Have you tried to access other ftp servers in
passive mode?
Yes, indeed. I used set passive in ncftp, and examined the
transcript later to be sure that
On Monday 23 June 2003 07:22, Herouth Maoz wrote:
Yes, indeed. I used set passive in ncftp, and examined the
transcript later to be sure that indeed it was sending the PASV or
the PORT command as indicated. And I tried with every Mandrake PPC
mirror - copied and pasted the URL to ncftp. With
Herouth Maoz wrote:
At 02:07 +0300 on 23/6/2003, Shaul Karl wrote:
Have you explicitly tried the passive command from within the ftp
program and got stuck? Have you tried to access other ftp servers in
passive mode?
Yes, indeed. I used set passive in ncftp, and examined the
transcript
Has anybody here suffered from problems with passive FTP?
Particularly, Actcom ADSL clients?
Any outgoing connection I make in passive mode times out. I suspected
my firewall at first, but since nothing in the kernel logs indicates
a drop, I'm beginning to suspect Actcom. I may be wrong about
Herouth Maoz wrote:
Has anybody here suffered from problems with passive FTP?
Particularly, Actcom ADSL clients?
Any outgoing connection I make in passive mode times out. I suspected
my firewall at first, but since nothing in the kernel logs indicates a
drop, I'm beginning to suspect Actcom.
On Saturday 21 June 2003 23:54, Herouth Maoz wrote:
Has anybody here suffered from problems with passive FTP?
Particularly, Actcom ADSL clients?
Are you behind a NAT? (i.e. are you trying to FTP from the firewall, or from a
machine behind it?)
If you are, don't forget to load the relevant FTP
Aviram Jenik wrote:
On Saturday 21 June 2003 23:54, Herouth Maoz wrote:
Has anybody here suffered from problems with passive FTP?
Particularly, Actcom ADSL clients?
Are you behind a NAT? (i.e. are you trying to FTP from the firewall, or from a
machine behind it?)
If you are, don't
24 matches
Mail list logo
