Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jul 1996 22:17:36 -0700 (PDT)
From:      Doug White <dwhite@riley-net170-164.uoregon.edu>
To:        Blaine Minazzi <bminazzi@w3page.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: networking Linux <--> FreeBSD
Message-ID:  <Pine.BSI.3.94.960717221134.230K-100000@gdi.uoregon.edu>
In-Reply-To: <31EBB63D.630E51FF@w3page.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Jul 1996, Blaine Minazzi wrote:

> Congratulations to the FreeBSD crowd. You managed to reduce me to
> a quivering mass of nerves.  After looking through the massive
> ( lack ) of documentation :-(   , I have to do the one thing
> all grown men hate to do the most. Ask for help... 

Well, you know, you can do something about that...:-)

> Here is something that should be rather simple. 
> Connect a Linux and FreeBSD box using TCP/IP.
> I have done this with Linux <--> Linux, but,
> for the life of me, I cannot talk to the BSD machine.

First timer?  

> My /etc/hosts files are 
> 
> 127.0.0.1  localhost
> 172.16.0.10  orion.whatever.com  orion 
> 172.16.0.20  xenu.whatever.com  xenu

Is this a private net or what?  The 0 net number is odd, I don't usually
see that.  Are you sure that's right?

> my networks file is 
> 172.16.0.0  what-net

> I ifconfig 172.16.0.10 ( and .20 ) to the devices eth0 and ed1
> on the 2 machines respectively.
> 
> Now on the linux box, I route add orion, 
> and route add what-net
> 
> I am not so clear on the BSD side of things.
> 
> There is a slight syntax differnece, and have read the man pages,
> etc... 
> 
> 
> Also, could someone be so kind as to give me some info
> on the /etc/sysconfig file...  How is yours set up?

The relevant sections from my 2.1.5 /etc/sysconfig.  You probably need to
edit the sections with *********'s. 

######################### Start Of Netconfig Section #######################

# Set to the name of your host - this is pretty important!
hostname=gdi.uoregon.edu

# Set to the NIS domainname of your host, or NO if none
defaultdomainname=NO

#
# Some broken implementations can't handle the RFC 1323 and RFC 1644
# TCP options.  If TCP connections randomly hang, try disabling this,
# and bug the vendor of the losing equipment.
#
tcp_extensions=YES

# If you're running PCNFSD or anything else which requires mountd to allow
# non-root requests for NFS mounts, set this to YES.
weak_mountd_authentication=YES

#
# Set to the list of network devices on this host.  You must have an
# ifconfig_${network_interface} line for each interface listed here.
# for example:
#
#       network_interfaces="ed0 sl0 lo0"
#
#       ifconfig_ed0="inet 10.0.0.1 netmask 0xffffff00"
#       ifconfig_sl0="inet 10.0.1.0 netmask 0xffffff00"
#       ifconfig_lo0="inet localhost"
#
# *********  do your network device config here! (uncomment first)
#network_interfaces="lo0 ed0"
#ifconfig_lo0="inet localhost"
#ifconfig_ed0="inet 128.223.186.250 netmask 255.255.254.0"

#No-network config
#
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 (unless
# static_routes is set to "" - do NOT use ``NO'' to denote a lack of
static
# routes!).
#
#static_routes="foo multicast"
#route_foo="woofo woofo-gw"
#route_multicast="224.0.0.0 -netmask 0xf0000000 -interface 10.0..0.1"

#static_routes="multicast loopback"
#route_loopback="gdi localhost"
#route_multicast="224.0.0.0 -netmask 0xf0000000 -interface gdi"

static_routes="loopback"
route_loopback="gdi localhost"

# Set to the host you'd like set as your default router, or NO for none.
# This is the same as adding a ``default'' entry to static_routes.
# ******** set this to your gateway.
#defaultrouter=128.223.170.1
defaultrouter=NO

# This is the routing daemon you want to use.  Possible options are
# currently NO (for none), `routed' and `gated'.  Also see `routerflags'
# for startup flags.
router=NO

All you really need is the default route and everything else will be
handled. 

BSD doesn't really make use of the /etc/networks or associated files.  Or
at least I don't.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.960717221134.230K-100000>