If both sides can mutually `ping`; they must both 'be a server & client'. As I previously said, it's like using the BundesBahn to fetch a glass of water from the kitchen. The 3Gdongle works like a rocket! == Thanks.
If both sides can mutually `ping`; they must both 'be a server & client'. As I previously said, it's like using the BundesBahn to fetch a glass of water from the kitchen. The 3Gdongle works like a rocket! == Thanks.
3GDongles connect you to the internet, not just the intranet. So you are not only using the BundesBahn, but the whole gobalBahn or whatever.
Your Pi can ping google.com. Your slackcomputer should be able to ping your pi on the external IP (if your provider doesn't NAT you)
ping-as-a-server/reflector is built into every TCP/IP stack I have ever come across, by default.
You have to go to a lot of lengths to turn it OFF, usually.
ping clients are less common, but even micrsoft WFG had one somewhere buried in the command line tools.
a telnet server is NOT something that tends to come by default these days however.
I think the raspian package would be 'telnetd' or some such.
They are both *ping servers* and both have a ping client (the ping command line utility), but this says nothing about whether they are running clients or servers for any other protocol.
You can't infer anything else from successfully pinging a computer other than it is powered up, running, has a ping server active on it and there's a working network path between the machines.
Using information about ping, as you seem to be doing, to make assumptions about any other protocol is unfounded bollocks.
rasbpian is debian based It's so there's probably a choice of atleast three telnet servers.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required