Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Jul 1995 10:13:17 -0400 (EDT)
From:      jan@bagend.atl.ga.us (Jan Isley)
To:        msmith@atrad.adelaide.edu.au (Michael Smith)
Cc:        freebsd-questions@freebsd.org (FreeBSD Questions)
Subject:   Re: basic no network setup question
Message-ID:  <m0sXqv8-0004qlC@bagend.atl.ga.us>
In-Reply-To: <199507170615.PAA02563@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 17, 95 03:45:37 pm

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for you help, Michael.  I know this is a simple RTFM question
for the network enabled.  I am network challenged.  Once I figure this
out I promise to answer the next 25 similar questions in the newsgroup.
:)  I need to get a networking 101 book.  Which one is in vogue right
now?  The man pages are like all unix man pages, they tell you what
you need to know if you already know what to look for.  That was the
basis of my question, I did not know what a "normal" startup was
supposed to look like.

Michael Smith wrote:
> Ok; can we have a look at /etc/hosts, /etc/host.conf, /etc/resolv.conf
> please?  What does the 'interfaces' line in /etc/sysconfig look like,
> and the lines immediately following it?
> 
> It looks like you don't have a default route.
 
I have no /etc/resolv.conf, nor a man page for it.  I installed the
etc source distribution and there was not one there either.  I thought
that I knew enough about networking that if I were uucp only I should
comment bind out of host.conf.  I know, assumptions get me in trouble.

# $Id: host.conf,v 1.2 1993/11/07 01:02:57 wollman Exp $
# Default is to use the nameserver first
# bind
# If that doesn't work, then try the /etc/hosts file
hosts
# If you have YP/NIS configured, uncomment the next line
# nis


#	$Id: sysconfig,v 1.14 1995/05/17 04:46:57 rgrimes Exp $
...
hostname=bagend.atl.ga.us
...
network_interfaces="lo0"
ifconfig_lo0="inet localhost"
#
# Set to the list of route add lines for this host.  You must have a
# route_${static_routes} line for each static route listed here.
#
static_routes="multicast loopback"
route_multicast="224.0.0.0 -netmask 0xf0000000 -interface ${hostname}"
route_loopback="${hostname} localhost"


Ah, hosts.  That is confusing.  The manpage is not illuminating.
The only non commented line in hosts is the 127.0.0.1 line.
"localhost" is every where in /etc.  At first I thought I should do:

127.0.0.1		bagend bagend.atl.ga.us

that gave a whole screen full of error messages, as does leaving it:

127.0.0.1		localhost localhost.my.domain

I tried this and got obvious error messages:

127.0.0.1		localhost bagend.atl.ga.us

What I posted was a result of this:

127.0.0.1		localhost

Last night I tried this again:

127.0.0.1		localhost bagend.atl.ga.us

and the boot messages, to me, looked more normal:

lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384
	inet 127.0.0.1 netmask 0xff000000 
add net 224.0.0.0: gateway bagend.atl.ga.us: File exists
add host bagend.atl.ga.us: gateway localhost: File exists
starting routing daemons: routed.

If that is right, the example is ... not good.  Actually the example
"127.0.0.1  localhost localhost.my.domain" is not good anyway.  If it
should be editited something other than "localhost" would help.
Or, should 127.0.0.1 be something else altogether and should I then
edit the imaginary network?

# Imaginary network.
#10.0.0.2		myname.my.domain myname
#10.0.0.3		myfriend.my.domain myfriend

What "exactly" should be in /etc/hosts for a standalone system?  I
appreciate your patience, really.
-- 
Jan Isley              Heroes have the shelf life of cottage cheese,
jan@bagend.atl.ga.us   and public memory is shorter than Dudley Moore.
                       -- Rheta Grimsley Johnson



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0sXqv8-0004qlC>