Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!usenet.ins.cwru.edu!nerd.apk.net!sed.psrw.com!psinntp !psinntp!psinntp!howland.reston.ans.net!swrinde!newsfeed.internetmci.com!news.uoregon.edu!pagesat.net!jolt.pagesat.net!news From: Dan Busarow <dan@beach.net> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Help to setup FreeBSD as a local server Date: Fri, 28 Jun 1996 14:48:05 -0700 Organization: DPC Systems / Beach Net Lines: 61 Message-ID: <31D45315.2781E494@beach.net> References: <31D30242.1776@ns.hondunet.net> NNTP-Posting-Host: calafia.beach.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0b3 (X11; I; FreeBSD 2.1.0-RELEASE i386) To: "Samuel E. Romero" <sromero@ns.hondunet.net> Samuel E. Romero wrote: > I have FreeBSD 2.1 on CDROM > The network numbers I've used are selected at random because it will be > a local network not an internet one (it's for learning about the web > server). You should use the RFC-1597/1918 addresses, just in case. If you have less than 250 hosts, use one of the Class C's which range from 192.168.0.0 to 192.168.255.255. If you have a larger network that you will need to subnet you may want to use one of the Class B's from 172.16.0.0 to 172.31.255.255. For best real life experience you should stick with the class C's. > The configuration I currently have is: > > /etc/networks > honnet 193.5.5 # Class C network? > honmsk 255.255.255.224 # Subneting the network > > subnet1 193.5.5.32 # > subnet2 193.5.5.64 # > . > . > subnet6 193.5.5.192 # >/etc/hosts >127.0.0.1 localhost >193.5.5.33 ed0lnk.hon.hn >193.5.5.34 main.hon.hn >193.5.5.35 www.hon.hn >193.5.5.66 pc1.hon.hn >193.5.5.67 pc2.hon.hn > > /etc/sysconfig > > network-interface="lo0 ed0" > ifconfig_lo0="inet localhost" > ifconfig_ed0="inet ed0link netmask honmsk" > . > > when I do a ping pc1: > No route to host Correct. You defined the various subnets, but only installed an interface on one of them. ed0lnk is on the 32 subnet, pc1 is on the 64 subnet. If you really have these subnets, then add a default route pointing to the router that handles the subnets. If you don't really have subnets, don't define them and you should be OK. Dan -- Dan Busarow DPC Systems / BeachNet Dana Point, California