On Wed, 28 May 2014, Bowie Bailey wrote: > On 5/28/2014 1:29 AM, Michael Hennebry wrote: >> On Tue, 27 May 2014, John R Pierce wrote: >> >>> On 5/27/2014 5:38 PM, Michael Hennebry wrote: >>>> Until recently, I had a 32-bit machine with one monitor running fedora. >>>> The later editions of fedora didn't like it, so I switched to CentOS. >>>> Now I have two 64-bit machines and two monitors and a CenturyLink router. >>>> Also a KVM switch that I have not taken out of the package. >>>> My main machine has two video connections >>>> and two ethernet connections, eth0 and eth1 . >>>> My secondary machine sometimes runs Windows, >>>> so I'd like it not to have its own global IP address. >>>> My first thought would be to connect it directly >>>> to one of the ethernet ports on my main machine. >>>> >>>> How do I go about this? >>>> The answer I am expecting is one or more links to tutorials or the like. > It can get fairly "interesting" depending on what you are trying to do. > You may need a special crossover cable to connect the two computers > directly. The newer network cards may be able to handle doing this with > a standard cable, but I haven't tried it. > > Why do you want to connect the two computers like this? It is usually > more trouble than it's worth unless you want to use the first computer > as a firewall or something. Just connect both of them to your router > and everything should work fine. I don't know that I do. I've not done anything with a router since connecting my old computer to CenturyLink's router/modem. I want the second computer to not have its own global IP address. It will at least occasionally run Windows. I'd prefer not to assume that Windows will not try to fetch an IP address behind my back. -- Michael hennebry at web.cs.ndsu.NoDak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods