SlackwareThis Forum is for the discussion of Slackware Linux.
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 have a LAN consisting of two hosts. Lets call one the server (or remote host) and the other the local host. Both are connected to internet through a router and modem. Running ifconfig in the server I get:
If, in the local host I do 'ping 192.168.0.101', I get:
Code:
................................................
64 bytes from 192.168.0.101: icmp_seq=1 ttl=64 time=1.77 ms
.................................................
That is, the local host is talking to someone. The question is: whom is it talking?
In the first code block, you see it says: 'inet 192.168.0.101'. And as I ran ifconfig in the server, it is some IP associated with the server, not with the local host. So when I do ping 192.168.0.101 from the local host, how can I be talking to the the local host? No, I do not say it's an error. I want to know what is 192.168.0.101.
You ran `ifconfig` on the "server", and it says that the server is 192.168.0.101.
Then you ran `ping 192.168.0.101` from the "local host".
So given that both "server" and "local host" are on the same network (192.168.0.0/24), ping is talking to "server", who is 192.168.0.101.
/etc/hosts contains whatever you put in it (the defaults that comes with the etc-package only lists 127.0.0.1). Just about all computers see themselves as 127.0.0.1, it's the loopback interface (as you can see in the lo: section of the ifconfig output: "inet 127.0.0.1 netmask 255.0.0.0").
SERVER_HOST sees itself as 127.0.0.1, as does your other computer. It's eth0 with ip 192.168.0.101 on SERVER_HOST that your other computer can connect to SERVER_HOST through.
I wanted to set the hostname and the domainname and could not do it. So I used netconfig and gave it those names. What it did I do not know, but after I ran it, /etc/hosts was as you see it. About VPN, honestly I don't know what it is.
If you used netconfig to configure for the static ip 192.168.0.101 then /etc/hosts should contain a corresponding line. The setting you have seems to be what you get when setting up the network for dhcp with netconfig.
/etc/hosts contains whatever you put in it (the defaults that comes with the etc-package only lists 127.0.0.1). Just about all computers see themselves as 127.0.0.1, it's the loopback interface (as you can see in the lo: section of the ifconfig output: "inet 127.0.0.1 netmask 255.0.0.0").
SERVER_HOST sees itself as 127.0.0.1, as does your other computer. It's eth0 with ip 192.168.0.101 on SERVER_HOST that your other computer can connect to SERVER_HOST through.
But who should SERVER_HOST.DN1 be for the local host. If I do rcp SERVER_HOST.DN1:some_file some_directory, on the local host (LOCAL_HOST.DN2), rcp must address some IP. What IP is that?
but who should server_host.dn1 be for the local host. If i do rcp server_host.dn1:some_file some_directory, on the local host (local_host.dn2), rcp must address some ip. What ip is that?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.