[opensuse] NFS & Host Configuration Problem
(OpenSuSE 11.0, DHCP) When I try to set up an NFS client, YaST can't find my server. The result of a LAN browse is (unknown). If you have experienced this problem, I'd appreciate hearing about it and how you solved it. One thing that looks wrong to me is the host configuration. There is no host name for IP address 127.0.0.1. I have host names for: 127.0.0.2 Earth-svr.site 127.0.0.3 Venus-ws.site 127.0.0.4 Marslaptop.site I was going to experiment with 127.0.0.1 but when I attempt to edit it, I get this dire warning: The host 127.0.0.1 is a system host. Really change it? Can someone tell me what this means? I'm not strong in networking so please use newbie words. -- Don Henson
On 07/23/2008 10:24 PM, Donald D Henson wrote:
One thing that looks wrong to me is the host configuration. There is no host name for IP address 127.0.0.1. I have host names for:
127.0.0.2 Earth-svr.site 127.0.0.3 Venus-ws.site 127.0.0.4 Marslaptop.site
I was going to experiment with 127.0.0.1 but when I attempt to edit it, I get this dire warning:
The host 127.0.0.1 is a system host. Really change it?
Can someone tell me what this means? I'm not strong in networking so please use newbie words.
127.0.0.1 is localhost. It should not be changed. It equals to "me" in networking, i.e. 127.0.0.1 is my local computer. HTH. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
On 07/23/2008 10:24 PM, Donald D Henson wrote:
One thing that looks wrong to me is the host configuration. There is no host name for IP address 127.0.0.1. I have host names for:
127.0.0.2 Earth-svr.site 127.0.0.3 Venus-ws.site 127.0.0.4 Marslaptop.site
I was going to experiment with 127.0.0.1 but when I attempt to edit it, I get this dire warning:
The host 127.0.0.1 is a system host. Really change it?
Can someone tell me what this means? I'm not strong in networking so please use newbie words.
127.0.0.1 is localhost. It should not be changed. It equals to "me" in networking, i.e. 127.0.0.1 is my local computer. HTH.
It helps a lot. Thanks. -- Don Henson
On Wed, 23 Jul 2008, Donald D Henson wrote:-
One thing that looks wrong to me is the host configuration. There is no host name for IP address 127.0.0.1. I have host names for:
127.0.0.2 Earth-svr.site 127.0.0.3 Venus-ws.site 127.0.0.4 Marslaptop.site
From the names, I'm guessing that these are different systems. If so, you need to move them from 127.0.0.x addresses to another address block. Suitable addresses for local networks are the ranges:
10.0.0.1 to 10.255.255.254; 172.16.0.1 to 176.31.255.254; 192.168.0.0 to 192.168.255.254; These addresses are specifically set aside for local networks and traffic to or from them shouldn't be passed on across the Internet. As for the 127.0.0.1 to 127.255.255.254 address block, all traffic to any address in that block is sent to the loop-back interface, and so never leaves the local system. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32 | | openSUSE 10.3 32bit | openSUSE 11.0 32bit | openSUSE 10.2 64bit | openSUSE 10.3 64bit | openSUSE 11.0 64bit RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David Bolt wrote:
On Wed, 23 Jul 2008, Donald D Henson wrote:-
One thing that looks wrong to me is the host configuration. There is no host name for IP address 127.0.0.1. I have host names for:
127.0.0.2 Earth-svr.site 127.0.0.3 Venus-ws.site 127.0.0.4 Marslaptop.site
From the names, I'm guessing that these are different systems. If so, you need to move them from 127.0.0.x addresses to another address block. Suitable addresses for local networks are the ranges:
10.0.0.1 to 10.255.255.254; 172.16.0.1 to 176.31.255.254; 192.168.0.0 to 192.168.255.254;
These addresses are specifically set aside for local networks and traffic to or from them shouldn't be passed on across the Internet. As for the 127.0.0.1 to 127.255.255.254 address block, all traffic to any address in that block is sent to the loop-back interface, and so never leaves the local system.
Regards, David Bolt
I had a reason for using the 127 addresses but I forget what it was. Shouldn't DHCP take care of all that? My DHCP server is set to assign IP addresses starting with 192.168.1.100 and a maximum of 27 addresses. (subnet mask 255.255.255.128) How does DHCP deal with host names? -- Don Henson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-07-23 at 16:26 -0600, Donald D Henson wrote:
I had a reason for using the 127 addresses but I forget what it was. Shouldn't DHCP take care of all that? My DHCP server is set to assign IP addresses starting with 192.168.1.100 and a maximum of 27 addresses. (subnet mask 255.255.255.128) How does DHCP deal with host names?
No, dhcp sets the IPs, and it can communicate with the name server to tell it the changes. It is not trivial. It is easier to give your machines fixed IPs and names. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIh8QatTMYHG2NR9URAuxXAJ4t0NvwqQ+iOPiNiYi7KSu8lBCsXQCdG9Hj 3rg4fqwYk+lW8G5fclcIbIE= =HytP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Wednesday 2008-07-23 at 16:26 -0600, Donald D Henson wrote:
I had a reason for using the 127 addresses but I forget what it was. Shouldn't DHCP take care of all that? My DHCP server is set to assign IP addresses starting with 192.168.1.100 and a maximum of 27 addresses. (subnet mask 255.255.255.128) How does DHCP deal with host names?
No, dhcp sets the IPs, and it can communicate with the name server to tell it the changes. It is not trivial.
It is easier to give your machines fixed IPs and names.
-- Cheers, Carlos E. R.
Let me see if I have this straight. I can set most of my hosts to static IP addresses by using /etc/hosts to define them. Then, those few mobile assets that move from LAN to LAN can still use DHCP, both on the same LAN. Right? -- Don Henson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-07-24 at 06:29 -0600, Donald D Henson wrote:
It is easier to give your machines fixed IPs and names.
Let me see if I have this straight. I can set most of my hosts to static IP addresses by using /etc/hosts to define them. Then, those few mobile assets that move from LAN to LAN can still use DHCP, both on the same LAN. Right?
More or less. .-) In the dhcp server you define a range for dhcp, and leave some aside to use as fixed. Even a cheap ADSL router from the telco has this facility. They are ranges inside the same LAN. In each machine that is going to act as a server of some kind, you edit the network settings (yast) to give it a fixed IP instead of getting an automatic one via dhcp. You will also have to assign the dns to use and default gateway (they were assigned via dhcp previously). On all machines that are going to use those servers you edit the /etc/hosts file to give names to those IPs you are going to access. This file does not define IPs, but arbitrary names to be used by that machine only to access the given IP numbers. On another machine the same IP may have a different name: not an error, but an inconsistency and a nuisance, which is usually overcome by creating your own local DNS server, for example. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIiJ1dtTMYHG2NR9URAn7bAJ9LL15yUCoUHOmTVSCkKMbz/BBRCQCdGkY5 kmNSN92/t/V4t6VB8q4KmC0= =9j+r -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Thursday 2008-07-24 at 06:29 -0600, Donald D Henson wrote:
It is easier to give your machines fixed IPs and names.
Let me see if I have this straight. I can set most of my hosts to static IP addresses by using /etc/hosts to define them. Then, those few mobile assets that move from LAN to LAN can still use DHCP, both on the same LAN. Right?
More or less. .-)
In the dhcp server you define a range for dhcp, and leave some aside to use as fixed. Even a cheap ADSL router from the telco has this facility. They are ranges inside the same LAN.
In each machine that is going to act as a server of some kind, you edit the network settings (yast) to give it a fixed IP instead of getting an automatic one via dhcp. You will also have to assign the dns to use and default gateway (they were assigned via dhcp previously).
On all machines that are going to use those servers you edit the /etc/hosts file to give names to those IPs you are going to access. This file does not define IPs, but arbitrary names to be used by that machine only to access the given IP numbers. On another machine the same IP may have a different name: not an error, but an inconsistency and a nuisance, which is usually overcome by creating your own local DNS server, for example.
-- Cheers, Carlos E. R.
Thanks. That tidbit cleared up several misunderstandings on my part. -- Don Henson
On Wed, 23 Jul 2008, Donald D Henson wrote:-
I had a reason for using the 127 addresses but I forget what it was. Shouldn't DHCP take care of all that?
If you haven't set them up as static IP addresses, then it should do.
My DHCP server is set to assign IP addresses starting with 192.168.1.100 and a maximum of 27 addresses. (subnet mask 255.255.255.128) How does DHCP deal with host names?
If you're running a DNS server, it's possible to have the DHCP server update the local zone file. Alternatively, if you've only have a few hosts on your network, assign them static IPs outside the dynamic pool and set up the hosts files with a list of them. On my network, I have a DHCP server[0] which will provide "static" IPs to the known hosts. For other hosts, usually virtual machines used for testing out development versions or guest machines on my network, it assigns IP addresses from its dynamic pool. Finally, there's also another dynamic pool used for network booting[1]. As for the DNS for the various hosts, those are all set up in a static DNS zone file that is synchronised between the three DNS servers on my little network. All this was set up years ago and has been [0] Well, two actually. I have a secondary one that has a mirror of the configuration and so could be activated if the primary server goes down[2]. [1] Although I gave up with that after a very short time without actually making it work. I really must get back to that and sort it out so it works properly. [2] This also applies to my web server as well. If it goes down for any reason, one quick change to the routeing table in my ADSL router and nobody would know anything had happened. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32 | | openSUSE 10.3 32bit | openSUSE 11.0 32bit | openSUSE 10.2 64bit | openSUSE 10.3 64bit | openSUSE 11.0 64bit RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
David Bolt -
Donald D Henson -
Joe Morris