FTP Slow responce maybe routing problem?

BinaryBob · 12-05-2004, 07:13 PM

Quick description of my network:

Code:

Netgear router        Windows                  Linux Router
192.168.0.1    =>     192.168.0.10   =>    eth0:192.168.0.12             Linux  FTP
<= Inet                                     eth1:192.168.1.2        =>    192.168.1.3

windows route output:

Code:

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1    192.168.0.10       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0     192.168.0.10    192.168.0.10       20
     192.168.0.10  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.0.255  255.255.255.255     192.168.0.10    192.168.0.10       20
      192.168.1.0    255.255.255.0     192.168.0.12    192.168.0.10       20
        224.0.0.0        240.0.0.0     192.168.0.10    192.168.0.10       20
  255.255.255.255  255.255.255.255     192.168.0.10    192.168.0.10       1

Linux route output:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
localnet        *               255.255.255.0   U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

Linux FTP route output:

Code:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
<<THERE IS AN APROX 9 second DELAY BEFORE SHOWING NEXT LINE>>
default         192.168.1.2     0.0.0.0         UG    0      0        0 eth0

Heres the ethereal output running capture on the windows box when i connect to the FTP on 192.168.1.3

Code:

No.     Time        Source                Destination           Protocol Info
      1 0.000000    192.168.0.10          192.168.1.3           TCP      1424 > ftp [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460
      2 0.000533    192.168.1.3           192.168.0.10          TCP      ftp > 1424 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
      3 0.000549    192.168.0.10          192.168.1.3           TCP      1424 > ftp [ACK] Seq=1 Ack=1 Win=65535 Len=0
      4 4.999810    192.168.0.12          192.168.0.10          ARP      Who has 192.168.0.10?  Tell 192.168.0.12
      5 4.999822    192.168.0.10          192.168.0.12          ARP      192.168.0.10 is at 00:0d:61:04:cf:72
      6 8.375845    192.168.0.1           192.168.0.255         RIPv1    Response
      7 10.014616   192.168.1.3           192.168.0.10          TCP      32777 > auth [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=44385 TSER=0 WS=0
      8 10.014645   192.168.0.10          192.168.1.3           TCP      auth > 32777 [RST, ACK] Seq=0 Ack=0 Win=0 Len=0
      9 10.015426   192.168.1.3           192.168.0.10          FTP      Response: 220 ProFTPD 1.2.9 Server (ProFTPD Default Installation) [astphone.lth.com]
     10 10.015500   192.168.0.10          192.168.1.3           FTP      Request: USER plcmspip
     11 10.015835   192.168.1.3           192.168.0.10          TCP      ftp > 1424 [ACK] Seq=77 Ack=16 Win=5840 Len=0
     12 10.016243   192.168.1.3           192.168.0.10          FTP      Response: 331 Password required for plcmspip.

Ok so as you can see between 3 and 4 on the ethereal output there is a significant differnce in time, also between 5 and 6. I don;t know why the netgear router is participating in this, but its replay seems very slow. I think this is whatrs slowing it down. But I'm not sure.

If i ping 192.168.1.3 from my windwos box, the relpys are nice and fast and everything is fine. But If I use any FTP client, it takes a while to connect

if I try to connect to 192.168.1.3 from the linux router, it doesnt connect.

If I try to connect to localhsot on the ftp itself it doent connect.
netstat -ln on the ftp shows:

Code:

Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:37              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:113             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN

so it is listening...

Any help would be appriciated, thank you!

Draygo · 12-06-2004, 02:33 AM

If it just takes a while to connect and after that everything is fine....looks to me like your ftp server is trying to reverse look up the ip of the box connecting to it. Try putting the ip and a hostname for your windows box in your ftp server's /etc/hosts file.

As for your linux router not being able to connect to the ftp server, do you have any kind of iptable rules?

BinaryBob · 12-06-2004, 03:00 AM

I forced proftpd not to do Reverse DNS. That fixed the speed issue.

How ever when i run "ncftp localhost" on the FTP server, it can't connect to itself, which I think is odd.

Linux Router also won't login to the FTP server, but all other clients on either subnet seem to be ok.

'iptables -L -nv' on Linux Router shows:

Code:

Chain INPUT (policy ACCEPT 261 packets, 26292 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 10623 packets, 7058K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 128 packets, 7818 bytes)
 pkts bytes target     prot opt in     out     source               destination

As you can see I have the policys all set to default ACCEPT so it should allow routing of everything to everywhere correct?