I've been trying to get Konqueror to find http://127.0.0.1:18020/ and it can't. Someone suggested that I ping that address. I'm not familiar with pinging and I wasn't able to find any useful information on the subject, so I just tried it. The terminal output was:

tom@emachine:~$ ping 127.0.0.1:18020/
ping: unknown host 127.0.0.1:18020/
tom@emachine:~$

What is this telling me, if anything? Where can I find some information about ping?

Thank you.

Hey,

I've actually never used ping in a Termianl, only in Dos. I imagine that the syntax isn't any different. It should be ping xx.xxx.xx.x Don't put a back slash after the IP address. Ping is used as dianostic tool. It sends packets of information to a node (printer, computer, website) and lets it respond. If it times out, it's not on the network or you are not on the network.

Regards,

Brandon

Unless your machine is severly borked, pinging will not show you anything special (other than your loopback is correctly working). Btw, the syntax for a ping would be
(the lack of a port number is because ping uses ICMP, whereas your port number was most likely TCP)

The question I would like to ask you is: “What are you running that’s listening on port 18020?” You can see listening network connections (along with the owning processes) with ss or netstat like so:
You might even try to connect to the service manually (with either netcat or a telnet client), but that would require knowing what application-level protocol it uses (perhaps http?).

Ping actually sends an ICMP Echo Request packet (and waits for an ICMP Echo Reply). The lack of a reply usually means there is no route to the requested host. Occasionally, it means there is a route to the host, but the host has been configured to reject or drop such packets (for example, try “ping microsoft.com”).

Osor,

Thanks for the more detailed explanation. I have a question, though. It's my understanding that if ping a computer (possibly a website) enough times in a short period of time, you could freeze it up. Is this true? Would this be why a website, like microsoft.com, woud be configured to reject a ping command?

Thanks,

Brandon

Yes, it is in fact capable of even crashing servers if the ping is big enough...I know a person who was pinging the school server and crashed it using large pings. (unintentionally of course)

It's always unintentional, isn't it?

Of course... ;-)

I am trying to go to the web address http://127.0.0.1:18020 because this the last step in the installation of a Linuxant DriverLoader which will let me connect wirelessly to the Internet.

Following osor's recommendation, I tried to ping again. Here's the results:

tom@emachine:~$ ping 127.0.
ping: unknown host 127.0.
tom@emachine:~$ 0.1
bash: 0.1: command not found
tom@emachine:~$ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.023 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=10 ttl=64 time=0.026 ms
64 bytes from 127.0.0.1: icmp_seq=11 ttl=64 time=0.025 ms

--- 127.0.0.1 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10002ms
rtt min/avg/max/mdev = 0.023/0.024/0.026/0.004 ms


I guess this means that the connection is open. If so, Konqueror can't find it.

Opinions?

Thanks!

My recommendation was not to ping again (all the ping shows is that your loopback ip is setup correctly), but to determine what programs (if any) are listening on that port. To do this, use “ss -lp” or “netstat -lp”.

You also mentioned the linuxant driver loader. According to this page, it seems you need to have the dldrconfig or webconfd program running in the background. Check to see if this is running. Additionally, see this question.