The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sms@moe.2bsd.com (Steven M. Schultz)
Subject: [pups] Networking With 2.11 BSD and Begemot Emulator
Date: Thu, 5 Oct 2000 09:42:05 -0700 (PDT)	[thread overview]
Message-ID: <200010051642.JAA03467@moe.2bsd.com> (raw)

Hi -

> From: Greg Lehey <grog at lemis.com>
> > revision 1.1
> > date: 2000/07/20 17:01:10;  author: nsayer;  state: Exp;
> > Add the tap driver.
> 
> Ah well, I still haven't used it.

	Neither have I ;)   I thought (for 30 seconds or less) about 
	porting it to BSD/OS - it's not that big and didn't appear to be
	overly tricky.

	Only reason I knew about 'tap' was that P11 has support for it and
	a pointer where to fetch 'tap' from.

> > 	The reason for publishing an ARP entry on the hosting system is...
> 
> I did that with a static route entry.

	Publishing an ARP entry has the benefit of not needing to wander
	around to all the systems on the LAN (I've several) and add a static 
	route.   In my case I don't own/run the local router so I couldn't 
	add a static route if I wanted to.   Having the host system 
	'arp ... pub' works was the simplest way to deal with the situation.

> As I say, it's not that simple.  I used it without trouble for years.

	Well, i'd have to see it working or have it explained in a bit more
	detail.  Having been thru the DEQNA driver and IP stack in 2.11 I
	can't see how an 11 will communicate with anything over an ethernet
	if it can't perform the IP<->ethernet address mapping.

> Recently something broke, and I suspect it trashed my root file
> system, and I haven't had time to go back and fix it.  Since others

	Ouch!  On the 11 side?  Or on the hosting system's side?

	Steven

Received: (from major at localhost)
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA53881
	for pups-liszt; Fri, 6 Oct 2000 16:12:11 +1100 (EST)
	(envelope-from owner-pups at minnie.cs.adfa.edu.au)
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA53877
	for <pups at minnie.cs.adfa.edu.au>; Fri, 6 Oct 2000 16:12:09 +1100 (EST)
	(envelope-from wkt at henry.cs.adfa.edu.au)
Received: (from wkt at localhost)
	by henry.cs.adfa.edu.au (8.9.3/8.9.3) id QAA66088
	for pups at minnie.cs.adfa.edu.au; Fri, 6 Oct 2000 16:13:45 +1100 (EST)
	(envelope-from wkt)
Received: from mail1.rdc1.il.home.com (mail1.rdc1.il.home.com [24.2.1.76])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id NAA53111
	for <pups at minnie.cs.adfa.edu.au>; Fri, 6 Oct 2000 13:42:43 +1100 (EST)
	(envelope-from cube1 at home.com)
Received: from ddjay.home.com ([24.10.213.208]) by mail1.rdc1.il.home.com
          (InterMail vM.4.01.03.00 201-229-121) with ESMTP
          id <20001006024207.JBOT7359.mail1.rdc1.il.home.com at ddjay.home.com>
          for <pups at minnie.cs.adfa.edu.au>; Thu, 5 Oct 2000 19:42:07 -0700
Message-Id: <4.3.2.7.2.20001005212349.06086580 at cirithi>
X-Sender: cube1 at cirithi
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 05 Oct 2000 21:25:17 -0500
To: pups at minnie.cs.adfa.edu.au (UNIX Heritage Society Digest)
From: Jay Jaeger <cube1@home.com>
Subject: [pups] Re: UNIX Heritage Society Digest V1 #137
In-Reply-To: <200009241945.GAA72267 at minnie.cs.adfa.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk

I had to replace the RS 423 drives on my PDP-11/24 and in the connected 
VT-100 terminal after a problem on a PC clobbered the 11/24 console ports 
which in turn clobbered the VT-100 some time ago.

---	
Jay R. Jaeger					The Computer Collection
cube1 at home.com			visit http://members.home.net/thecomputercollection


Received: (from major at localhost)
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA53897
	for pups-liszt; Fri, 6 Oct 2000 16:14:08 +1100 (EST)
	(envelope-from owner-pups at minnie.cs.adfa.edu.au)
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA53893
	for <pups at minnie.cs.adfa.edu.au>; Fri, 6 Oct 2000 16:14:06 +1100 (EST)
	(envelope-from wkt at henry.cs.adfa.edu.au)
Received: (from wkt at localhost)
	by henry.cs.adfa.edu.au (8.9.3/8.9.3) id QAA66113
	for pups at minnie.cs.adfa.edu.au; Fri, 6 Oct 2000 16:15:42 +1100 (EST)
	(envelope-from wkt)
Received: from wantadilla.lemis.com (root at wantadilla.lemis.com [192.109.197.80])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id OAA53333
	for <pups at minnie.cs.adfa.edu.au>; Fri, 6 Oct 2000 14:35:53 +1100 (EST)
	(envelope-from grog at wantadilla.lemis.com)
Received: (from grog at localhost)
	by wantadilla.lemis.com (8.11.0/8.9.3) id e963Z3N21875;
	Fri, 6 Oct 2000 13:05:03 +0930 (CST)
	(envelope-from grog)
Date: Fri, 6 Oct 2000 13:05:03 +0930
From: Greg Lehey <grog@lemis.com>
To: "Steven M. Schultz" <sms at moe.2bsd.com>
Cc: pups at minnie.cs.adfa.edu.au
Subject: Re: [pups] Networking With 2.11 BSD and Begemot Emulator
Message-ID: <20001006130503.A21828 at wantadilla.lemis.com>
References: <200010051642.JAA03467 at moe.2bsd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200010051642.JAA03467 at moe.2bsd.com>; from sms at moe.2bsd.com on Thu, Oct 05, 2000 at 09:42:05AM -0700
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-418-838-708
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk

On Thursday,  5 October 2000 at  9:42:05 -0700, Steven M. Schultz wrote:
>>> 	The reason for publishing an ARP entry on the hosting system is...
>> I did that with a static route entry.
>
> 	Publishing an ARP entry has the benefit of not needing to wander
> 	around to all the systems on the LAN (I've several) and add a static
> 	route.   In my case I don't own/run the local router so I couldn't
> 	add a static route if I wanted to.   Having the host system
> 	'arp ... pub' works was the simplest way to deal with the situation.
>
>> As I say, it's not that simple.  I used it without trouble for years.
>
> 	Well, i'd have to see it working or have it explained in a bit more
> 	detail.  Having been thru the DEQNA driver and IP stack in 2.11 I
> 	can't see how an 11 will communicate with anything over an ethernet
> 	if it can't perform the IP<->ethernet address mapping.

I don't know the details either, unfortunately.  I really need to find
some time to get the thing running again.

>> Recently something broke, and I suspect it trashed my root file
>> system, and I haven't had time to go back and fix it.  Since others
>
> 	Ouch!  On the 11 side?  Or on the hosting system's side?

On the 11 side.  I'm not sure what happened, but it looks like it.
It's not a big deal, since I have backups somewhere.

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers



             reply	other threads:[~2000-10-05 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-05 16:42 Steven M. Schultz [this message]
     [not found] <200010041528.IAA19574@moe.2bsd.com>
2000-10-04 15:57 ` Frank Wortner
  -- strict thread matches above, loose matches on Subject: below --
2000-10-03 20:02 Frank Wortner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200010051642.JAA03467@moe.2bsd.com \
    --to=sms@moe.2bsd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).