Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!newsfeed.direct.ca!op.net!news.mathworks.com!news.sprintlink.net!news-peer.sprintlink.net!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!usenet
From: brian@awfulhak.demon.co.uk (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: How do I install Freebsd over Parallel or Serial Port?
Date: 2 Jan 1997 01:19:14 GMT
Organization: Coverform Ltd.
Lines: 83
Message-ID: <5af2ei$92r@awfulhak.demon.co.uk>
References: <5a1jpu$6pu@herald.concentric.net>
NNTP-Posting-Host: awfulhak.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
To: averba@eden.rutgers.edu (Andrew Verba)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33454
[Posted and mailed]
In article <5a1jpu$6pu@herald.concentric.net>,
averba@eden.rutgers.edu (Andrew Verba) writes:
> Hey,
>
> Anyone know how to install Freebsd over Parallel or Serial Port.
[.....]
If you select any standard network-type install, it eventually asks
you what interface you want to use - you'll get lp0 as an option, and
there's something in there for serial connections (can't remember exactly).
> My other question is:
>
> The question above is more important and probably easier to answer(just
> a warning).
>
> I was trying to set up communications between the pentium and 386.
> Getting a dumb terminal to work through the serial port was easy,
> by modifing /etc/ttys. However, I would like to have many terminals
> open simultaneously, and even to run the pentium as an x-server. The
> pentium currently has windows 95 and NT version 4, and has xserver
> software. The prefered method of communcations would be the parallel
> port interface, and I have a lap link cable for this.
>
> The easiest way to solve this, I suppose, would be to buy two ethernet
> cards and install them in each machine. If I was to do this, what do
> I need to do in FreeBSD to get it on the two machine network? There is
> some kind of option in windows 95 networking that allows configuring the
> network. I think windows 95 has tcpip and nfs services built in. Does
> anyone have any info on this?
Have a look in /etc/sysconfig on the FreeBSD box. You need to pick a
private subnet (see /etc/hosts) and allocate an IP from that subnet to
your machine in /etc/sysconfig.
> The other way, would be to use a lap link cable through the parallel port
> because there are only two machines, and it is cheap. However, I have
> no clue how to set up freebsd in this case, to run PLIP. There is a
> packet driver for dos, plip.com, and I might be able to run sessions
> through dos windows with plip running and NCSA telnet for dos, under
> windows 95. Does anyone know what needs to be done on the Freebsd
> machine to get it to do tcpip over the parallel port?
The FreeBSD side is easy - all you need is
ifconfig lp0 inet 10.0.1.1 10.0.1.2 netmask 0xffffffff
This is done automatically via /etc/sysconfig too.
I don't know if the PLIP that FreeBSD talks is compatible with anything
else..... surely there are timing issues ?
> Finally, what happens when you have a tcpip network, and one machine
> on the network dials out and begins runing PPP. What happens to the
> IP address of that machine, and how does it still communicate with
> other machines on the private network. I am refering to a freebsd
> machine or a windows 95 machine.
>
> If anyone needs to know where to find plip.com (the dos packet driver)
> please ask, I will look it up for you. And ofcourse, feel free to ask
> me any questions that you have:
When you have more than one network interface (say a LAN connection &
a PPP), you also have more than one hostname - IP numbers are per
interface, not per machine. So, for example, my back-end machine
is called awfulhak.demon.co.uk (158.152.17.1 - a real IP). However,
on my LAN, the machine is awfulhak.coverform.lan (10.0.1.1 - a pretend
IP). Other machines on the LAN are 10.0.1.* (netmask 0xffffff00).
When the machine talks to my ISP, it does it via tun0 (the ppp interface)
and writes packets with a source IP of 158.152.17.1. When the machine
talks to the LAN, the source IP is 10.0.1.1.
FWIW, it is possible to set two interface addresses to the same thing
as long as at least all but one of them are point-to-point protocols
(SLIP, PLIP, PPP) as the p2p protocols use the destination IP for
routing purposes.
--
Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....