topic Re: Fake Loopback /etc/hosts in Operating System - HP-UX

Fake Loopback /etc/hosts

Nobody's Hero — Wed, 02 Feb 2005 10:10:56 GMT

OK I've done this many times and I can't remember how to do it. I did a fresh install and the box is not on the network yet, so SAM takes forever.

You can fake it out with a /etc/hosts entry, something like:

xxx.xx.xx.x loopback 'hostname'
or
xxx.xx.xx.x 'hostname' loopback

something like that, I know it works because I've done it before. Then SAM will run much faster until I get it on the network...

Re: Fake Loopback /etc/hosts

Gary L. Paveza, Jr. — Wed, 02 Feb 2005 10:13:12 GMT

Try 127.0.0.1

Re: Fake Loopback /etc/hosts

Robert-Jan Goossens — Wed, 02 Feb 2005 10:14:52 GMT

127.0.0.1 localhost loopback

Regards,
Robert-Jan

Re: Fake Loopback /etc/hosts

Nobody's Hero — Wed, 02 Feb 2005 10:15:07 GMT

Yes, I understand that. but you put the hostname in as the loopback address or something like that. like

127.0.0.1 ltcrss loopback

I cant remember the sequence....

Re: Fake Loopback /etc/hosts

Nobody's Hero — Wed, 02 Feb 2005 10:18:50 GMT

OK...

127.0.0.1 localhost loopback is the valid entry. I am trying to fake the box out. HP showed me this a long while ago. I know it works.

I'll try
127.0.0.1 ltcrss

Re: Fake Loopback /etc/hosts

Nobody's Hero — Wed, 02 Feb 2005 10:43:58 GMT

You mean to tell me that all the experts out there have not done this. The box will think it is on the network, and SAM will run fast.

Re: Fake Loopback /etc/hosts

harry d brown jr — Wed, 02 Feb 2005 11:21:00 GMT

I think you mean if itcrss has an ip of 192.168.1.2 and you want the loopback to use something other than 127.0.0.1 ?

/etc/hosts:
192.168.1.2 ltcrss loopback

The ORDER does NOT matter. The issue is that some software products have 127.0.0.1 hardcoded instead of looking up "loopback" or "localhost"

live free or die
harry d brown jr

Re: Fake Loopback /etc/hosts

Victor BERRIDGE — Wed, 02 Feb 2005 11:53:24 GMT

Hi,
When you say not on the network yet, you mean configured for already? And not as standalone.

So I wonder if you are not having issues because you have /etc/resolv.conf and /etc/nsswitch.conf already active with maybe in nsswitch hosts: DNS [NOTFOUND=CONTINUE] files, or something of the sort...

I usually stop all inet services and at the console type set_parms saying no for DNS NIS etc so that it just updates the IP and /etc/hosts for hostname and later when connected I configure/update the files that deal with network by hand...

Just thoughts....

All the best
Victor