*BSD News Article 85013


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!ddsw1!news.mcs.net!www.nntp.primenet.com!nntp.primenet.com!uwm.edu!lll-winken.llnl.gov!decwrl!purdue!mozo.cc.purdue.edu!hopf.math.purdue.edu!wilker
From: wilker@hopf.math.purdue.edu (Clarence Wilkerson)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: ip aliases, routing, tinnels
Date: 16 Dec 1996 02:09:36 GMT
Organization: "Purdue University Department of Mathematics"
Lines: 46
Message-ID: <592b10$81u@mozo.cc.purdue.edu>
Reply-To: wilker@math.purdue.edu
NNTP-Posting-Host: hopf.math.purdue.edu
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32672

I have a trial ASDN installation at my home. It gives me a white box
on the wall connected to my home system by an  ethernet connection  
and to the world ( 1.5Mbits from the world inward, 
90kbits outward). The setup has a fixed ip number and apparently won't
route any other number in to my box. But it's still FUN....

There are a couple of problems that  make it not perfect:

1) the ip number has no symbolic name recognized by any DNS or routing 
tables. This means that it is hard to get mail at home directly, and
connections to sites that do reverse ip lookups are sometimes
rejected.  Also, not having a Purdue ip number means I'm locked out of 
certain services like News and some data bases. I'm beating on Purdue
and GTE on these issues, but no luck so far.

2) I used to use PPP with a fixed ip number for the home box and this 
had an official name. Routing, DNS, Mail, etc all worked under the 
old slow system. I'd like to get this functionality back (with better 
speed of course )

There are of course workarounds to most of these problems. However, I'm 
compulsive enough to want a global solution to restore all the
things that a PPP link did for me.

I have control of a machine in office at work ( running Netbsd-current also).

Here's the functionality I would like:

Office machine = ROLLE
Home machine = ASDN
Old home IP = HOPF2

I'd like to use the fact that I can make an tcpip connection from
ROLLE <--> ASDN  to route traffic intended for HOPF2  to ASDN.

If I just alias the ethernet port on ASDN to the old HOPF2 ip number
I cannot get the gateway upstream to ASDN to route packets for 
HOPF2 to ASDN.

But it seems like there should be a combination of IP-aliasing
and IP-tunneling ( IP within IP) that would do what I want.
However, I could find no documentation for the /dev/tun0 device
and I wasn't sure what the tunneling mentioned in the
MROUTED man page was all about.

Clarence Wilkerson