If this truly is the time needed for packets to come back from the server, your response time is 5x faster than mine.

Quote:

traceroute :

Code:

1 192.168.1.3 (192.168.1.3) 4.776 ms 75.448 ms 15.882 ms

daemonfowl, it would be good if you showed the next shell's prompt. As it is, it is unclear if this is the complete output or merely cherry-picked output.

Outside of not being able to reconcile why an external ftp server would have an private non-routable address, you are presenting data which indicates that the server may be across the street. Somehow, this seems a bit too fantastic to be true...

Yes it is .. just learning by trying .. not a business or something :-)
(Router is 192.168.1.1)
The IP address of the ftp server is 192.168.1.3 and I can access it and get data .. simply it's unbelievably slow responding .

Looool !!
well it's somehacker@ocicat@daemoforums@Gaia@MilkyWay@soon-comingBlackHole@Ragnarok .. hopefully you'll be vitharr :-) .. I do have a login named vitharr@ragnarok lol .. on a flash running puffy ..

Is there anything wrong with this :
bridge0 :
add wpi0
add bce0
up
and
bce0 set :
up media 10base2

You will be doing everyone(including yourself...) a great service if you would provide a diagram of your network. This is discussed in the "perfect newbies" thread you should know better than your name at this point. We certainly have pointed you to it for guidance countless times. We do so for a reason.

Your network topology is a complete unknown at this time. No one has any clue as to what you have connected to what, why it is done as it is, & whether any decisions made here adversely affects transmission rates.

I have the suspicion that to both understand & solve this problem you need to simplify the network -- just connect the "server" to a "client" using Ethernet. As it is, there are too many unknowns involved, & you have a very bad habit of not disclosing vital information until we have beaten the problem senseless. Wasting time might be minimized if you would simply state necessary details up front. Again, the thread referenced above can serve as a guide.

One of the things you should take away from this message is that one proven technique to problem solving & troubleshooting is to simplify the problem down to the simplest configuration which still exhibits the problem. This eliminates variables which have no effect early on, so time is not wasted chasing irrelevant details. Anything you do at this point which eliminates clutter & unnecessary details will make this process go much quicker.

I removed bridge0 and related bce0 .. It's now a simple home network :

Router : 192.168.1.1
5 Machines :
Acer is using wpi0 or bce0 for wired connection (as FTP server )
As Clients : Dell/iBook/iMac/CompaqMini .. I have to use either wired connection or that Dlink Wireless Adapter ..
Yesterday I tried to ftp connect to Acer from CompaqMini using Dlink Adapter.

...& since you have never supplied a network diagram, there is nothing anyone can do for you.

In case this has not been clear enough, your network toplogy is a complete mystery. No one knows what is connected to what, or can trace packets from any arbitrary computer/laptop/device to any or all other computers/laptops/devices on your network.