With that caution, let me offer a guess about what is going on -- DNS problems.
When you say ftp "will tell me I have connected and then just sit there" ... how long do you wait? In your tests, have you waited out the 3-minute timeout for unsuccessful reverse lookups? Or have you tried adding an entry for the other machine's IP address to /etc/hosts on the LEAF system, so a reverse-lookup can resolve quickly?
What do the logs on the LEAF system say about the connection attempt?
Can you ssh (or, perhaps, telnet, if it really is an ancient LRP version) into the LEAF host successfully? (If you see the same sort of delay, that strengthens the plausibility of the DNS guess.)
It is all only a guess though ... if that's not it, please try sending a more complete description of the problem (refer to the SR FAQ for help with this, as well as my questions and comments above).
At 08:04 AM 2/13/2004 -0700, David Bonfoey wrote:
I am using the LRP as a standalone embedded system. I have it running on a small advantech sbc board with a simple web server, ftp server, and a small network program. I am only using eth0 and I am not using eth1.
My problem is that when I am on a small network (my laptop, the LRP box, and a switch connecting the two) I can view the web page and I can ping the LRP box. I cannot use FTP in this configuration though. It will tell me I have connected and then just sit there (no I am not using passive ftp). I am not sure why this would hang when there is nothing stopping the traffic between us. FTP will work fine if the gateway I have specified exists in the network.
The second problem (most likely directly related) is that when I change the ip address and do a "svi networking restart" I get "RTNETLINK answers: No such process done" error if I change the gateway to something that is not there. By this I mean if I change the gateway from 10.0.0.1 to 90.0.0.1 it will squack at me. It still works, but it complains about it (most likely because I have not put the device behind the new gateway). This is an issue for me because I have to set an ip address up from the web page in order to configure the device... I can't use a monitor and keyboard when I am actually in the network.
Thanks, David
Kernel 2.4.20
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:0b:ab:02:46:f4 brd ff:ff:ff:ff:ff:ff inet 90.0.0.11/24 scope global eth0 3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
90.0.0.0/24 dev eth0 proto kernel scope link src 90.0.0.11 default via 90.0.0.30 dev eth0
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
