Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!in-news.erinet.com!newsfeeder.sdsu.edu!news.sgi.com!uhog.mit.edu!news.mathworks.com!newsfeed.internetmci.com!realtime.net!not-for-mail From: chip@unicom.com (Chip Rosenthal) Newsgroups: comp.unix.bsd.bsdi.misc,comp.infosystems.www.servers.unix Subject: Re: Virtual Host Problems Date: 24 Jul 1996 04:32:09 GMT Organization: Unicom Systems Development, Austin, TX Lines: 43 Message-ID: <4t4909$vg4@news3.realtime.net> References: <31F091E6.2C1D@peacenet.com> NNTP-Posting-Host: garcon.unicom.com X-RTcode: 3d30ea8e31496d10baf5a79f Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:4368 comp.infosystems.www.servers.unix:16966 In article <31F091E6.2C1D@peacenet.com>, Stan Golob <sgolob@peacenet.com> wrote: >This is what I have done: > > Added the ifconfig lo0 alias `ipaddress` > > (Additionally all the DNS configuration has been done, but > doesn't have anything to do with the problem I'm having.) If you are going to bind the alias address to lo0, then you need to proxy arp that address. Probably something like: arp -s (aliasaddress) `/etc/netscripts/myether` pub I also think it's a good idea to: route add (aliasaddress) localhost Some systems require this to keep packets off the wire. Others do not. I can't recall offhand what BSD/OS does. (I *think* it detects this in the Ethernet driver, and the localhost route saves a trivial and insignificant amount of processing.) In any case, rather than remembering which hosts need what, I just always do it. You can avoid some of this complexity by binding aliases to the Ethernet address. I think that introduces a whole other set of problems, so I prefer to use the loopback, as you are doing. > Ping to virtual ip works from anywhere in local domain. > Ping to virtual ip doesn't work from anywhere out of local. > Ping to hosts within local domain works. > (all pings are being done with IP addresses) I'm going to guess that you've got some sort of routing happing on your local host ... either through gated or static routes or something similar ... that causes this scenario. -- Chip Rosenthal * Unicom Systems Development * <chip@unicom.com> Unix system programming/support * Internet * test/ctrl/comm systems URL: http://www.unicom.com/ * 48 68 D8 BE 10 C8 6B DE 60 17 00 0B A7 83 99 8E CHAG email spam? SEC complaints to <http://www.sec.gov/enforce/con-form.htm>