🚀 go-pugleaf

From: Denis DeLaRoca (213) 825-4580 <CSP1DWD@MVS.OAC.UCLA.EDU>
Date:  Thu, 18 Jul 91 09:07 PDT
Subject: ka9qnos.ps.Z

I retrieved and uncompressed ka9qnos.ps.Z from hamradio/ka9q/nos
but after printing on an Apple Laserwriter I end up only with 18
pages... I believe the document is more like 38 pages, where are
the other 20 pages?

-- Denis


----
From: Ben Thornton <val!ben@cs.utexas.edu>
Date: Thu, 18 Jul 91 11:13:54 -0500
Subject: Re: Before you do that release...

In message <9107180821.AA04216@vela.acs.oakland.edu> you write:
>> 
>>   I'm not sure if anyone else has caught it (am I the only one running
>> the PPP code?), but the function userlookup() was deleted from files.c
>> some time back for some reason.  This function is referenced when you 
>> enamble the PPP conditionals.  I had to dig out a previous version of
>> NOS to correct the problem.  It is called from a module in PPPPAP.C.
>> 
>> Ben Thornton
>> WD5HLS
>> 
>What ?!?  I run PPP code every day!   PPP is compiled into the "official"
>NOS, found in the ka9q/nos directory.  If you are having problems with
>someone else's modification of nos, please make this clear in the message.
>
>Bill Simpson

You are right, I negected to mention which version I was referring to.  However
the message was written as a reply to a message of Gerard's in which he
discussed finalizing a "release" version of NOS.  I was attempting to point out
one area of *his* version of the code that needed attention.  Sorry for the
confusion.

BTW, I have been having difficulties with the PPP code in interoperability
with a Sun 3/60.  I am running Karl Fox's <karl@MorningStar.Com> version of
of PPP under SunOS 4.1.  I have been able to make the two machines communicate
but I have been unable to get them to properly negotiate the address and
TCP header compression protocol.  I am running PA0GRI's most recent version
of NOS.  I suspect that it is simply a configuration problem on one or both
ends, but I have been unable to find the winning combination of paramters
to make it work.  Any ideas?


----
Ben Thornton             packet:  wd5hls@wd5hls.ampr.org
Video Associates       Internet:  ben@val.com
Austin, TX                 uucp:  ...!cs.utexas.edu!val!ben



----
From: bsimpson@vela.acs.oakland.edu (Bill Simpson)
Date: Thu, 18 Jul 91 15:30:32 EDT
Subject: Re: Before you do that release...

I don't have the slightest idea how close his version is to the base KA9Q.

The problem with IP header compression negotiation is that many versions
(including the early Katie Stevens version for KA9Q) used the wrong protocol
number for the negotiation, and arent' smart enough to stop asking
when they've been NAK'ed several times with a different number.
The only solution is don't ask for header compression.  In the base KA9Q,
this means:
  ppp <iface> quick                                     # set everything on
  ppp <iface> ipcp local compress none                  # don't ask for it
  ppp <iface> ipcp remote compress allow off            # don't let remote ask
  ppp <iface> lcp open

Bill_Simpson@um.cc.umich.edu
    bsimpson@vela.acs.oakland.edu

Mail to you bounces, Ben.....


----
From: bsimpson@vela.acs.oakland.edu (Bill Simpson)
Date: Thu, 18 Jul 91 15:30:32 EDT
Subject: Re: Before you do that release...

I don't have the slightest idea how close his version is to the base KA9Q.

The problem with IP header compression negotiation is that many versions
(including the early Katie Stevens version for KA9Q) used the wrong protocol
number for the negotiation, and arent' smart enough to stop asking
when they've been NAK'ed several times with a different number.
The only solution is don't ask for header compression.  In the base KA9Q,
this means:
  ppp <iface> quick                                     # set everything on
  ppp <iface> ipcp local compress none                  # don't ask for it
  ppp <iface> ipcp remote compress allow off            # don't let remote ask
  ppp <iface> lcp open

Bill_Simpson@um.cc.umich.edu
    bsimpson@vela.acs.oakland.edu

Mail to you bounces, Ben.....


----
From: "SCFE::BARGLOWSKI" <barglowski%scfe.decnet@scfb.nwc.navy.mil>
Date: 18 Jul 91 16:30:00 PDT
Subject: 9600 baud packet for J. Blow

Hello to all:

I just got into packet a few months ago after I found NET/Mac on the
internet.  TCP is great over the radio (I did have to learn ax25, too!)
but I would like to go faster than 1200 baud.  Since I'm not too adept
at modifying tranceivers and I haven't seen any high-speed packet cards
for my Mac I was looking at the Kantronics Data Engine/DVR2-2 combo
with a 9600 baud modem in the Data Engine.  Has anybody had any experience
with either of these machines?  I'm also worried about whether this modem
will exchange data with another 9600 baud modem of a different type. Is
9600 baud *9600 baud*???  What about upgrade paths for higher speed modems?

Thanks in advance...........

jan.

--------------------------------------------------------------------------------
Jan Anthony Barglowski			EMail:  BARGLOWSKI@SCFB.NWC.NAVY.MIL
Visualization Lab, Code 2724			jan@suncad.vislab.nwc.navy.mil
Naval Weapons Center			Packet: kc6uth@wa6ybn.#socal.ca.us.na
China Lake, CA 93555			IP:	[44.17.0.6]
--------------------------------------------------------------------------------


----
From: wkt@csadfa.cs.adfa.oz.au (Warren Toomey)
Date: Fri, 19 Jul 91 12:50:56 EST
Subject: Will rip broadcast my address??

A quick question on rip. If I turn rip on, will it broadcast my IP address,
or just the routes I know. If the latter, this means nobody will learn how
to reach me - this is assuming I'm using rip over ax25 and not everybody
on my subnet can hear me (which is true).

Can I get around this by doing:

	route add my.address loopback

[just checked, nos won't let me do this]

Any other ideas?

Ta,
	Warren.


----