![](https://seccdn.libravatar.org/avatar/5a94d2f8a5845d5f1c1ea1556fc0cb72.jpg?s=120&d=mm&r=g)
Brian Durant wrote:
On Thursday 21 March 2002 17:26, you wrote:
DHCP is a way to dynamically assign all the variables needed to connect to a network, such as IP, netmask, gateway, etc. DNS is the service that translates names that makes sense to people, to IP numbers that make sense to computers. The protocol and service doesn't vary between SuSE and anyone else on the internet. ;-) Maybe the programs used do, but that is the freedom of Linux, standards compliant software that works everywhere.
OK, but if DHCP is administered dynamically, then there is nothing to fill in, but you need to fill in something to get an Internet connection with SuSE.
You only need to install the Nic, assign it a number, enable it, and set it to dhclient. You can either go with the default config or you CAN modify it.
In the Win or Mac world, if your access to the Internet is administered dynamically, then there is nothing to fill in or see, unless you want to enforce a static IP.
That is not entirely true, though dhcp client is the default config in Windows, and their defaults, which a lot of DHCP servers are configured for, will usually work (but not always).
In this case (and only this case), I find the DNS confusing for the following reasons:
I thought we were talking about DHCP. DNS is a seperate service. It is usually configured on your computer by DHCP in that environment for name resolution (otherwise you would need to know all IP numbers for everything).
1) The dynamic administration of DHCP that I mentioned above, which usually includes not needing to include a domain, unless the individual is serving their own domain directly to the Internet. Albeit, there are some ISP's that require filling out this info such as cb.net.id.
The fact that some do and some don't is EXACTLY why things are configurable in Linux. It will work (maybe some configuring) everywhere. Microsoft tries to create a proprietary everything that they can control, so it is not surprising theirs usually works by default since most ISPs have to assume the majority of clients that connect to them will run M$.
2) The issue of hostname-computer name and domain-workgroup Linux-Win. Isn't there a clean cut way of applying this in SuSE? There are two options that I have spotted. One in KDE control center, which is called "user" and "workgroup". The other in YAST2, where "hostname" and "domain name" can be filled out. "User" is not necessarily "computer name". These are concepts that are hard to wrap my head around compared to past experience in other OS's
That is probably because you used a non networking OS. User is not the same as the computer name, even in Windows. The confusion in the terms is a result of M$ attempt to proprietize the computer software industry. User = user, the one using the computer at any given moment. Hostname=computer name, domain name is almost the same as workgroup.
3) Where does my LAN start and my WAN end? If I want to have a computer called "x" and a workgroup that I want to call "y", but log onto an ISP domain called cbn.net.id and have a "username" on that ISP of "z", where do the different blanks need to be filled in in SuSE to complete this?
This sounds like a dialup, so whatever program is used to interface with your ISP would take 'z' with the appropriate password. Remember, each server you connect to (not pass through) will authenticate you to make sure you are a valid user, so you may have many usernames/passwords, one each for each server. This is different than your computer name/domain name. This your ISP may be using to make an entry in their DNS server (maybe you are confusing the dynamic updating of DNS with DHCP), though I doubt it unless you are web hosting or something.
OK, I have an eth0 that connects to my router. I do have an eth1 that I haven't configured yet, but I haven't done that yet as it is not connected to anything at this time. The diference between your configuration and mine seems to be that my LAN is connected to a hardware router that is connected to the cable modem (i.e. WAN). Why would I add IPs of my LAN to "/etc/hosts AND /etc/lmhosts"? I am not hosting anything. I just want to be able to log on to the other computers. The other computers on my LAN do not have static IP addresses anyway. Everything is assigned automagically.
I can only assume your ISP does dynamic DNS updating through DHCP, which makes an entry in their DNS server that would be able to translate your hostnames to IP addresses. If that assumption is correct, you should be able to connect to them through their name assuming nothing is being blocked by a firewall. If your other machines are Win98 (if I remember), are you sharing your drives to the internet? What do you mean by 'log on to the other computers'. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871