Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I believe you're mixing up the HTTP (website) protocol and the FTP (file transfer) protocol.
If you want to download from a website, ie http://something.somewhere, then you're using the HTTP protocol
(note the "http://" at the beginning).
This means that the computer you're trying to reach is reachable via a browser, on port 80 (HTTP port).
However, if you do "ftp IP-address", then you're using the FTP protocol (ports 20/21, not port 80). You're actually trying to reach "ftp://something.somewhere". The remote site may prevent such ftp access, for instance
if they don't have an ftp server on the same machine, if they don't allow incoming ftp connections on their firewall, etc.
So, you should stick to the protocol that is suggested. HTTP in this case. Try downloading the file in a browser.
If however, you want to download loads of files from a site and you don't want to click on each of them to download them manually, I suggest that you use the "wget" utility.
It's very handy for downloading a bunch of files, either via http or ftp (it supports both).
But I must say that the URLs in this case are a bit confusing. They seem to be FTP URLs (ie "pub" directory, "ftp4", etc), but they are HTTP addresses (http://). Those guys probably need to clarify their configuration and/or set up a proper FTP (or SFTP) server. lol
bash-2.05$ ping -sa 134.76.11.100
PING 134.76.11.100: 56 data bytes
64 bytes from 134.76.11.100: icmp_seq=0. time=440. ms
64 bytes from 134.76.11.100: icmp_seq=1. time=399. ms
64 bytes from 134.76.11.100: icmp_seq=2. time=397. ms
64 bytes from 134.76.11.100: icmp_seq=3. time=396. ms
64 bytes from 134.76.11.100: icmp_seq=4. time=398. ms
64 bytes from 134.76.11.100: icmp_seq=5. time=404. ms
64 bytes from 134.76.11.100: icmp_seq=6. time=413. ms
^C
----134.76.11.100 PING Statistics----
8 packets transmitted, 7 packets received, 12% packet loss
round-trip (ms) min/avg/max = 396/406/440
Should my alter any other because which works for local ftp connection.
bash-2.05$ ftp 10.255.240.230
Connected to 10.255.240.230.
220 (vsFTPd 2.0.1)
Name (10.255.240.230:user6):
looks like working But could not reach the website You gave or whatever.
Here is a list i got.
bash-2.05$ traceroute -I 134.76.11.100
traceroute: Warning: Multiple interfaces found; using 10.2.1.99 @ eri0
traceroute to 134.76.11.100 (134.76.11.100), 30 hops max, 40 byte packets
1 202.141.29.33 (202.141.29.33) 1.207 ms 0.969 ms 1.057 ms
2 202.141.31.25 (202.141.31.25) 4.833 ms 4.757 ms 5.015 ms
3 202.141.30.3 (202.141.30.3) 4.943 ms 5.924 ms 7.142 ms
4 61.95.191.133 (61.95.191.133) 78.933 ms 13.247 ms 89.226 ms
5 61.95.180.7 (61.95.180.7) 163.318 ms 118.849 ms 66.709 ms
6 61.95.180.90 (61.95.180.90) 65.389 ms 98.663 ms 15.715 ms
7 203.208.147.81 (203.208.147.81) 295.331 ms 302.891 ms 322.265 ms
8 208.50.13.165 (208.50.13.165) 259.911 ms 208.50.13.185 (208.50.13.185) 251.319 ms 208.50.13.165 (208.50.13.165) 261.630 ms
9 * 67.17.65.78 (67.17.65.78) 435.963 ms 415.855 ms
10 208.48.23.142 (208.48.23.142) 410.652 ms 422.583 ms 392.269 ms
11 188.1.18.2 (188.1.18.2) 403.562 ms 395.605 ms 410.469 ms
12 188.1.18.6 (188.1.18.6) 395.625 ms 395.991 ms 405.229 ms
13 * * 188.1.18.10 (188.1.18.10) 396.650 ms
14 188.1.18.58 (188.1.18.58) 408.768 ms 461.997 ms 456.968 ms
15 188.1.19.14 (188.1.19.14) 433.041 ms 575.735 ms 410.922 ms
16 188.1.46.202 (188.1.46.202) 400.229 ms 400.810 ms 417.139 ms
17 134.76.11.100 (134.76.11.100) 425.885 ms 390.072 ms 434.422 ms
bash-2.05$
On my RH8 box, both ftp4.de.freesbie.org and ftp.gwdg.de indeed have IP
134.76.11.100
Ftp to this address works just fine. It gives me the FTP welcome message from the "Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH Goettingen" (which means something like the "organisation for scientific data processing in Goettingen" (if my German is still any good after a few years).
When you open the 2 links in gilead's post (adding "pub/" at the end of the second), in a browser, it gives the index of the pub directory. You can download the program from there.
However, what worries me a bit is "Warning: Multiple interfaces found" in your traceroute. Do you have multiple network interfaces? If so, it could be normal. If not, you may have another computer using your IP on the same network (duplicate IP).
If your ftp doesn't work, you should check your firewall settings.
The speed of a download is affected by many causes:
-speed and load of the downloading machine
-speed and load of the server from which you download it
-speed of the interconnection (speed of your internet link, speed of internet path that's followed,etc).
So, there's nothing much you can do, except:
-Choose a server as close to you as possible ("the longer the path, the slower").
-If possible, choose a server (or a mirror) that's interconnected to your network/computer via the fastest link. For instance, our network is connected via a very fast multi-gigabit link with several other networks of research facilities in the surrounding countries. Whenever I can, I download from a mirror that's on that same research "backbone", simple because it's very fast.
-Limit the load on your computer (don't do anything except downloading).
-Limit the number of interfering soft- and hardware (like firewalls, antivirus, etc) as much as possible, without comprimising security, of course.
-As for the speed and load of the server, that's just "trial-and-error". If one server seems to busy, use another...
-Use automatic download programs/ftp clients. They are often slightly faster then you typing in the commands with the ftp command line tool. Personnally, I've often used "wget" on Linux/Unix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.