HDTenEightyP/NetNews huggingface dataset:
From: rypma@waterloo.hp.com (Ted Rypma)
Subject: Re: Need help routing with PPP
Date: Thu, 28 Jan 1993 04:26:01 GMT
Organization: HP Panacom Div Waterloo ON Canada
X-Newsreader: TIN [version 1.1.4 PL6]

Ernest Clinton Arbaugh Jr (cea@cerc.wvu.wvnet.edu) wrote:
: 
: I've got PPP running on a pair of SPARCstations, but  I can't seem 
: to get them to route.   Here's basically what things look like:
: (Greatly simplified.)
: 
: Local Site    Remote Site 
: +----+        +----+
: |  A |--------|  D |
: +----+  PPP   +----+
:    |            |
:    |   <.   .>  |
:    |     \ /    |
: +----+    Y   +----+
: |  B |    |   |  E |
: +----+    |   +----+
:    |      |
:    |  <- Ethernet
:    |
: +----+
: |  C |
: +----+

When PPP is started up on A and D, somehow A must publish the route to 
the D/E network to hosts B and C, and D must publish the route to the A/B/C
network to E. (A and D, of course, have no problems with each other, but
have no knowledge of the other's second interface.) Routing protocols do
exist and can, I suppose, handle the situation, but I have had very little
luck dynamically adding routes when SLIP/PPP start up.

To get around this, we have added static routes for hosts on multiple
different networks to reach each other through the PPP/SLIP gateway hosts.
This works well for us.

If there is only a single remote host, the gateway host on the multi-host
network can respond to ARP's for the single remote if told to do so,
but that doesn't work very well when there are multiple remote machines.

An example gated.conf entry found on ALL our hosts on the main (25.4.0.0)
network is as follows:

    static {
	192.61.63 gateway 25.5.4.6;
	192.61.59 gateway 25.5.4.2;
	192.61.58 gateway 25.5.1.27;
	192.61.57 gateway 25.5.4.50;
	192.61.56 gateway 25.5.4.101;
	192.61.55 gateway 25.5.4.58;
	192.61.54 gateway 25.5.4.43;
	default gateway 25.5.1.1;		<== Cisco
    };

    propagate proto rip {
	proto static {
	    announce default;
	};
    };

Each line of static route lists the two interfaces on a host with a
(in this case SLIP, but PPP shouldn't differ) serial link. We subnet
the class C address so that the SLIP link itself takes two addresses
and most of the rest are available on the remote end Ethernet. In
some cases, the remote end consists of only one host and no Ethernet
and in others, there are a number of hosts and devices on the far end.

The gated protocol seems unable to deal with subnets so we simply send
everything to the gateway (on network 25.5.0.0) and allow them to route
appropriately.  (The gateway hosts also have static routes to direct all
192.61.xx.0 traffic to the remote end of the SLIP link, which then
forwards if necessary on its Ethernet interface.  Lots of routes, but
once they are set up, it all works flawlessly.

Regards,

Ted Rypma
HP Panacom Division
Waterloo, Ontario

(All opinions expressed are mine and not my employer's.)
Newsgroups: comp.protocols.ppp,comp.unix.aix
From: hewlett@nosc.mil (Edward M. Hewlett)
Subject: Re: Morningstar ppp 
Summary: Request for experience and phone numbers 
Keywords: MorningStar ppp
Organization: Naval Ocean Systems Center, San Diego
Date: Thu, 21 Jan 1993 22:46:02 GMT

I'm interested in anyone's experience with MorningStar's ppp product
on DTC 2s running OS-4.

Also I'd like to have a phone number. I've found references to the product
but no address or phone number.

Ed Hewlett




Newsgroups: comp.protocols.ppp
From: koverber@cs.ulowell.edu (Kurt Overberg)
Subject: Partial PPP success! BUT....
Originator: koverber@bigmax.ulowell.edu
Organization: University of Massachusetts at Lowell Computer Science
Date: Thu, 21 Jan 1993 21:28:06 GMT


Ok, 

	After 3 days of constant work, I finally got my Sparc I and
Sun3 to trade packets... Not very quickly, mind you, but at least
they are exchanging packets.  I am using PPP-1.1.  The two machines
are connected via a null modem cable and are running at 19200 baud.
Here is what my stats look like (colt is remote mach, pinto is local)

This is what a netstat -i on pinto (local) gave me....
Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis Queue
le0   1500 129.63.0.0    pinto          58162   0    55263   0    20     0
ppp0  1500 colt          pinto          133     0    413     1    0      0
lo0   1536 loopback      localhost      112125  0    112125  0    0      0

Here are the local ifconfigs...

root@pinto;/etc> ifconfig ppp0
ppp0: flags=51<UP,POINTOPOINT,RUNNING>
        inet 129.63.28.23 --> 129.63.28.20 netmask ffff0000

	          ^--- Does this mean that 129.63.28.23 (local) is a gateway to 
			129.63.28.20  (remote mach) Im not too sure...

I did have this problem with the local end.  These are the error messages:
Jan 21 15:52:27 pinto vmunix: ppp: unknown protocol 0xffff
Jan 21 15:52:28 pinto vmunix: ppp_async: bad protocol low byte
Jan 21 15:52:28 pinto vmunix: ppp_async: short packet
Jan 21 15:52:28 pinto vmunix: ppp_async: bad protocol low byte
Jan 21 15:52:29 pinto vmunix: ppp_async: short packet
Jan 21 15:52:29 pinto vmunix: ppp_async: bad protocol low byte
Jan 21 15:52:29 pinto vmunix: ppp_async: short packet
Jan 21 15:52:29 pinto vmunix: ppp_async: bad protocol low byte
Jan 21 15:52:29 pinto vmunix: ppp_async: short packet
Jan 21 15:52:30 pinto vmunix: ppp: unknown protocol 0xffff
(...just keep repeating this sequence...)
What could be causing these?  Improper handshaking?

One problem is that the only evidence that this is working is that i can see
the packet count go up.  ping dosen't work, etc...
I believe the problem is that my routing tables are messed up.  I 
configured them similarly to the way they say in the docs, but
I'm no networking guru.  I know just enough to be dangerous. :^)

Does anyone out there have ANY idea whats going on?  Can anyone point
me in the right direction?  How about any good info on how /etc/gateways
should be set up?  How about some info on how routing works?  Helllp!
Any info would be GREATLY appreciated!! Please help so I can go to bed!!
Thanks!


					peace out.

					   kurt
-- 
Kurt Overberg            | I honestly doubt you care about my opinions ;^)
U of Mass, Lowell        | "Poke a double-decker on a Llama taboot,       
koverber@cs.ulowell.edu  |  Llama taboot, taboot!"      -Phish
Newsgroups: comp.protocols.ppp
From: erict@ascent.com (Eric Tiffany)
Subject: dp-2.2 loadable modules don't...
Organization: Ascent
Distribution: comp
Date: 26 Jan 93 09:05:48


I posted this to the dplist, but I thought I would try here too.

After compiling and installing dp-2.2 (with the patch posted by Kirk
Smith), I tried to run startdp which loads the loadable modules using
modload.  This happened [I gave modload the -v flag to give more
"information"]:

#/etc/dp/modules/startdp
infile /etc/dp/modules/ppp_async.o, infilename /etc/dp/modules/ppp_async, outfile /etc/dp/modules/ppp_async, execfile /etc/dp/modules/postasyncload
Linking the module...
ld -o /etc/dp/modules/ppp_async -Bstatic -T 0 -A /vmunix -N -e _ppp_async_init -s /etc/dp/modules/ppp_async.o
ld cannot open load script file 0   	[**** The lossage here ****]
ld failed, status = 1
infile /etc/dp/modules/dp_if.o, infilename /etc/dp/modules/dp_if, outfile /etc/dp/modules/dp_if, execfile /etc/dp/modules/postdpload
Linking the module...
ld -o /etc/dp/modules/dp_if -Bstatic -T 0 -A /vmunix -N -e _dpmod_init -s /etc/dp/modules/dp_if.o
ld cannot open load script file 0	[**** and here ****]
ld failed, status = 1
#

Why does ld say: 

    ld cannot open load script file 0

I have checked permissions, the man pages for ld, run 'strings X |
grep script' for every X I can think of, and all to no avail.

I am running SunOS 4.1.1, with a couple of kernel additions (pppV5,
and Symbolics UX400 VME support).  

I hope this isn't something real stupid.  Do I need the jumbo ld patch
(patch # 100170-09) which also means I need the 6Mb libc patch (patch
# 100267)?  I hope not.

Thanks to anyone with a clue



--
  __/ _ _/   Eric Tiffany        Ascent Technology, West   914-944-9003
 __/   /    erict@ascent.com    312 Briarcliff Drive So.  617-225-0850
__/  _/    erict@panix.com     Ossining, NY  10562
From: peter@micromuse.co.uk (Peter Galbavy)
Newsgroups: comp.protocols.ppp
Subject: PPP for Solaris 2/SVR4 needed NOW
Date: 28 Jan 93 15:06:23 GMT
Reply-To: peter@micromuse.co.uk
Organization: MicroMuse Ltd, London

Hi kids,

I need PPP for Solaris 2, and I need it now. Commercial products are interesting
certainly, but Morningstar do not yet have a date for their version.

The reason is I am migrating our mail/news server onto a new machine with Solaris
2.1 and I need PPP to connect to Demon Systems - for Internet access.

I am also quite willing to try porting code from 386/486 UNIX's.

Thanks all,
---
Peter Galbavy
Tech Support, Micromuse Ltd
Phone: +44 71 352 7774		E-Mail: P.Galbavy@micromuse.co.uk
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: dcarr@gandalf.ca (Dave Carr)
Subject: Re: Low cost ether/isdn brouters
Organization: Gandalf Data Ltd.
Distribution: na
Date: Tue, 26 Jan 1993 18:22:02 GMT

In <1993Jan26.011730.185@informix.com> johng@informix.com (John Galloway) writes:

>In article <1993Jan25.142206.17177@gandalf.ca> dcarr@gandalf.ca (Dave Carr) writes:
>>
>>With bonding you only have one channel.  With some software running on top
>>of multilink, you can split the packet in pieces and load balance. 
>>Fragmentation in this case is not done like a router, but similar to the
>>more bit in X.25.

>These two topcis are also realated.  If running completely seperate
>B channels, then a user could leave one up all the time (and have a single
>B chanles worth of resource on the host end dedicated to this user) but
>only add the second on demand and thus have something like 1.25 B channels
>for each user at the hub, and give 2 64K channels to most folks when
>the need arises, but not have to have 2B channels dedicated to each user.
>Digiboard claims they can do this with their IMAC with each B channel going
>to a different user.  However this scheme would not allow the 2Bs to be bonded.
>In part this comes down to the question: do apps like ftp want an
>ack after every packet and hence not be able to make use of 2 64K channels
>as opposed to one 128K channel?

This isn't an issue if you run LAPB multilink over multiple (not necessarily 2)
links.  You are free to split the frame, not fragment but equivalent to the
X.25 more bit at layer 3, over the links and reassemble at the remote before
transmitting out the ethernet.  Then, you can load balance a single frame.

Alternately, if the protocol supports a tranmission window as FTP does, you
can use the links independently.  However, I believe that a bridge/router
should maintain the sequence of packets.  This is not possible without adding
the equivalent to a multilink sequence number over the links.  You don't
need LAPB for this.  I don't know what Digiboard does.  

We run LAPB with multilink.  But we do not (yet) split the frames for load
balancing.  We do it on a frame-by-frame basis.

Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: gardner@ux1.cso.uiuc.edu (Mike Gardner)
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Organization: University of Illinois at Urbana
Date: Thu, 21 Jan 1993 21:08:43 GMT

dcarr@gandalf.ca (Dave Carr) writes:

>Interesting.  Could you tell me more.  With ISDN, we are basically talking
>about a point-to-point link.  Our view is with the right software mods, you
>can get the desired performance out of a bridge.  The trickiest part is the
>handling of multicast and broadcast.  If we can eliminate these packets
>without doing the entire routing function, do we have what you need?

>There isn't that much difference in performance between a bridge and a
>router in terms of forwarding performance.  The big difference is the
>100's of Kbytes of code to support the various stacks.

Routers typically let you isolate users because it has the various
protocol stacks.  Much better tools in the bridges would let you do
the same things.  In our applications, we would like to bridge many very
small remote ISDN lans into a single, or few ethernets at a central
site.  Keeping those users from inadvertantly or maliciously affecting
other ISDN users by using the wrong IP address is difficult in a purely
bridged environ.  All of the bridge packet mask tools we have seen so
far are just too simple to work with IP.  It is a bit silly to have
eth-router-isdn-router-eth.  Eth-router-isdn-bridge-eth would be much
better, but none of the vendors I've seen support that either.

mgg
--
That's the wonderful thing  |University of Ill, Computing & Comm Services Ofc
about crayons; they can take|Michael G. Gardner, Assistant Director, 1122 DCL
you more places than a      | 1304 W Springfield, Urbana, Il 61801
starship. Guinan/Rascals/TNG|(217)244-0914 FAX (217)244-7089  EMAIL mgg@uiuc.edu
Newsgroups: comp.protocols.nfs
From: vanderwal@rc.tudelft.nl (Guus van der Wal)
Subject: MSDOS-Batch-trick doesn't work with PCNFS loaded
Organization: Delft University of Technology
Date: Tue, 26 Jan 1993 15:58:14 GMT

In a batch file I used to use the trick described in the MSDOS-5 manual on 
page 510. I used this to test whether a directory exists or not.
The command is IF EXIST c:\mydir\nul echo YES
This returns YES if mydir exists.
 
When PCNFS40a is loaded this trick returns YES all the time
Can anyone explain this?
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: scott@labtam.labtam.oz.au (Scott Colwell)
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Organization: Labtam Australia Pty. Ltd., Melbourne, Australia
Date: Fri, 22 Jan 1993 00:07:04 GMT

vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:

>Anyone who wants to run a dumb terminal over a network protocol over
>ISDN (e.g. TCP/IP/ISDN) will probably not have an ethernet at home,
>such a person either has other, unsual requirements or has more money
>and technophilia than brains and should instead just use a $300 raw
>modem (or ISDN) link.  This also applies to less dumb, X terminals,
>which should be using one of the new light weight, serial line X
>protocols instead of vanilla X/TCP/IP/ISDN.

This is somewhat misleading.  With X terminals, you have a choice of the
following:

1/ X over TCP/IP over PPP(or CSLIP etc) over ISDN

2/ Xremote over something that is not TCP/IP over ISDN

3/ Graphon X server in host communicating over something proprietry over ISDN

4/ LBX (Low Bandwidth X) over TCP/IP over PPP over ISDN

Methods 2 and 3 are both proprietry and (I believe) do not work well with
local X clients in the terminal.  They will probably fade away over time.
LBX is still under development and will not appear as a product for a while
yet but will solve most peoples problems.

So, the general solution (read non-proprietry) is method 1.  At least it
allows you to get access to the serial ports on the terminal to drive a
printer etc (i.e. terminal server style).

People who run X terminals at remote sites still want the general
facilities of TCP/IP, hence LBX's method.

Still,  Vernon's comments about routers versus bridges, I second whole
heartedly.  This becomes very important with things like 'dial on demand'.
-- 
Scott Colwell				Labtam Australia Pty. Ltd.
net:	scott@labtam.labtam.oz.au	41 Malcolm Rd., Braeside
phone:	+61-3-587-1444			Melbourne, Australia  3195
From: KDICKEY@cmsa.gmr.com
Newsgroups: comp.protocols.nfs
Subject: "Netware-like" services using NFS
Date: 23 Jan 93 03:08:40 GMT
Organization: GM Research Labs

Hello,

We're a PC/TCP site license site, and use the InterDrive NFS client with a
number of different types of Unix machines. From time to time the subject of
Novell comes up, and some people say, why aren't we running Netware. I
usually preach the benefits of IP, Unix, Standards, etc.., and that Netware
is proprietary and requires IPX. The one thing that they say is that there are
products out there running under Netware that offer software metering or
brokering, and software distribution. Does anyone know of third party
vendors that offer the same kinds of services on top of NFS?

Thanks,
Keith A. Dickey          kdickey@cmsa.gmr.com
Electronic Data Systems, Advanced Computing Center
Newsgroups: comp.protocols.nfs
From: cliff@eggneb.astro.ucla.edu (cliff UCLA Astronomy)
Subject: Re: Help to porting PCNFSD.v2 for DEC-Ultrix ??
Reply-To: cliff@eggneb.astro.ucla.edu (cliff UCLA Astronomy)
Organization: UCLA Department of Astronomy
Date: 21 Jan 93 13:18:18 PST


|>
|>Hi world,
|>
|>I can't compile original source code of pcnfs.v2 on an DEC-Uutrix
|>maschine. Have anyone already porting it ?? please help me.
|>
|>vu
|>--
|>    _/    _/  _/    _/  Tien Hung VU   _/_/_/  FORWISS Erlangen.
|>   _/    _/   _/   _/   Am Weichselgarten 7, 8520 Erlangen. Germany.
|>  _/_/_/_/    _/  _/    Email: vu@forwiss.uni-erlangen.de.
|> _/    _/     _/ _/     Tel: ++49 9131 691136
|>_/    _/      _/_/      Fax: ++49 9131 691185
|>

 I need the same information.  Can anyone help?

 cliff

 cliff@trifid.astro.ucla.edu

Xref: sparky comp.protocols.nfs:3176 comp.dcom.isdn:1194
From: sxn@eng.sun.com (Steve Nahm)
Newsgroups: comp.protocols.nfs
Subject: Re: Connectathon Coming?
Date: 23 Jan 93 05:40:33 GMT
Organization: Sun Microsystems Inc., Mountain View, CA
NNTP-Posting-Host: rand

oldera@twg.com (Ed Alcoff) writes:

>I haven't received anything on Connectathon yet?
>Is there going to be one next month?  Does
>anybody have any info?

Connectathon is in July this year.

For those who may not know, Cthon is the annual ONC/NFS and X Windows
interoperability test event, where implementors of these protocols can
see how their implementations work with others.

Here's the announcement (which was distributed in December):

CONNECTATHON '93
GREAT MINDS LINK ALIKE

SunSoft, Inc. today announced that the eighth annual Connectathon(TM)
event will be held July 22-30, 1993 at the San Jose Convention and
Cultural facilities in San Jose, California. This event enables
hardware and software developers to test portability and
interoperability of their technologies.

Over the years, Connectathon's popularity has grown and the event has
become *the* network proving ground where engineers come to test their
ONC/ONC+ and X-windows technologies. This year the event has been moved
to July and expanded to include exciting new technologies which will be
available for testing and debugging.

The event is an excellent opportunity for developers to verify that
their software interoperates on a variety of servers, window managers
and operating systems. Everything from laptops to supercomputers can be
linked together under one roof, encouraging interaction among vendors,
engineers and developers in a confidential atmosphere.

For more information and/or to continue receiving Connectathon
information, please return the attached form via email to
72571.1341@CompuServe.Com, or fax to Connectathon '93 at 415-388-7506.

NAME		____________________________________
TITLE		____________________________________
COMPANY		____________________________________
ADDRESS		____________________________________
		____________________________________
MAIL-STOP	____________________________________
CITY/STATE	____________________________________
ZIP/POSTAL CODE	____________________________________
PHONE		____________________________________
FAX		____________________________________
EMAIL ADDRESS	____________________________________


--
Steve Nahm                              sxn@sun.COM or sun!sxn
Sun RPC Project Lead
From: kaz@uni-paderborn.de (Kay Mueller)
Newsgroups: comp.protocols.nfs
Subject: Open a fixed securety-hole
Date: 28 Jan 93 12:41:28
Organization: Uni Paderborn FB 17 Informatik GERMANY
Distribution: comp
NNTP-Posting-Host: haegar2.uni-paderborn.de

Hi out there,

We are running the rpc.pcnfsd on a server with a restricted passwd.
(only those users who are in /etc/netgroup on our nisserver are allowed to
log in)
The old deamon (PCNFS 3.5) did not care aboutthis, and every user could do
his net name *
But the new pcnfsd (pcnfsd.92.11.05) checks the local /etc/passwd and returns an
"Authentication Failiure" to everyone not mentioned in /etc/netgroup.

How can I open this securety hole?

Ok, I know, I could install the deamon on a client, but I don't want to.

Thanx in advance,

Kay
From: michaelh@sevie.uk.sun.com (Michael Haines - Sun EHQ - SITKA)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS 4.0a Printing Problem!!
Date: 13 Jan 1993 10:26:22 GMT
Organization: Sun Microsystems (UK) Ltd
Distribution: world
Reply-To: michaelh@sevie.uk.sun.com
NNTP-Posting-Host: sevie.uk.sun.com


This is a summary from my problem with pc-nfs 4.0a. I'm working with
PC-NFS 4.0a between one pc and one sparcstation. I connected my printer on my
pc and i'm working on my Sun SparcStation, that means all files are created 
from my Sun and I print them from the Sun to the printer via the pc.

           This is my problem : for example, I create four files on the Sun,
these files are first in the Sun's spool directory in order of creation and
then going to the pc's spool directory in order of creation. But the problem
is these files are printed in disorder, thus between the pc's spool directory
and the printer I have a problem, this is certainly a problem with the pcnfslpd
daemon, this daemon used to print the files from the pc's spool directory.

           I don't understand why these files are in order of creation in the
pc's spool directory and between the pc and the printer, they are printed in
disorder.  

           Now, if you have a printer connected on your Sun SparcStation and
you want to print files from your PC to your printer via the SparcStation, you
have no problem regarding the order of creation, these files are printed in
order.

Does anybody know of this problem?

Many thanks for your help.

Xref: sparky comp.protocols.nfs:3193 comp.dcom.isdn:1203