Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.cais.net!bofh.dot!news.mathworks.com!newsfeed.internetmci.com!news.ac.net!news.serv.net!not-for-mail From: zeno@serv.net (Sean T. Lamont) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Can't traceroute to virtual hosts Date: 17 May 1996 05:08:51 -0700 Organization: ServNet Internet Services, Seattle, WA Lines: 20 Message-ID: <4nhq8j$f5p@itchy.serv.net> References: <4mhaeg$f8@venus.os.com> <4mjnl4$hgn@paperboy.livenet.net> <4mkakq$51s@uriah.heep.sax.de> <4nd1nv$1cn@anorak.coverform.lan> NNTP-Posting-Host: itchy.serv.net >The mask should be 0xffffffff - meaning that anything on this network can >be reached down this interface.... ie. only that machine. From a TCP/IP standpoint, this makes little sense. All bits are significant for the network, none for the host? What about IP broadcast for that subnetwork? Besides, what's the fundamental difference between a virtual host using (as you say) ffffffff and a 'real' host using ffffff00? I'd been using ffffff00 for virtual IP's and adding a static local route to 127.0.0.1. Works fine, except for some minor initial complaints. -- Sean T. Lamont, President / CEO, Abstract Software (ServNet) - Internet access * WWW hosting * TCP/IP * UNIX * NEXTSTEP * WWW Development - email: lamont@abstractsoft.com WWW: http://www.serv.net "...There's no moral, it's just a lot of stuff that happens". - H. Simpson