Article View: dnet.ham
Article #70TCP-Group Digest 270691.1815
From: daily posting
Date: Thu, 27 Jun 1991 16:15
Date: Thu, 27 Jun 1991 16:15
310 lines
11476 bytes
11476 bytes
From: Andrew Heybey <ath@ALLSPICE.LCS.MIT.EDU>
Date: Wed, 26 Jun 91 14:06:55 -0400
Subject: NTP under NOS
I have ported xntp to run under NOS. NTP (the Network Time Protocol)
is "used to synchronize timekeeping among a set of distributed time
servers and clients" (from the NTP RFC). Xntp is a daemon for Unix
that implements NTP.
My port appears to work, so I would like to give it out to anyone who
would like to give it a try. The port is (at best) a beta release.
It is available as a set of diffs from the NOS version of 910614 and a
bunch of xntp source files. The changes to NOS are relatively minor,
so it should work with any relatively recent version of NOS.
The distribution is available from allspice.lcs.mit.edu:pub/ath/nosntp.tar.Z
andrew
----
From: Wood Tracy <TKWOOD@gordon-emh1.army.mil>
Date: Wed, 26 Jun 91 15:16:34 EDT
Subject: AX.25 Hooks To Telnet For NOS
KA9Q NOS Users:
We are currently running KA9Q NOS and are able to get AX.25 users
to log into the mailer to forward and receive e-mail. However,
we are unable to get the AX.25 users to successfully implement the
"T" Telnet option which I assume allows the AX.25 user to telnet out
of the TCP/IP host.
How do we turn this "T" option on for TCP/IP users? (The NOS
version we are running is 0528.)
Thanks
TK Wood KD0UP/4
-----------------------------------------------------------------------------
MAIL: ELECTRONIC:
US Army Signal Center DDN : woodtk@gordon-emh1.army.mil
Directorate of Combat Developments AUTOVON : 780-3782
Concepts & Studies Division COMM : (404) 791-3782
ATTN: ATZH-CDC (Studies:Tracy Wood) FAX: (404) 796-7977
Fort Gordon GA 30905-5090
------------------------------------------------------------------------------
----
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Date: Tue, 25 Jun 91 09:57:04 EDT
Subject: Re: mbox forwarding problems
I have been doing some fairly heavy bbs forwarding here with the latest
PA0GRI code (actually one back from the latest) and I have not seen this
problem. At least I have not had reports of it. From what you say it is
not possible to actually see the problem at the source end, unless you
have another system monitoring what goes out. As far as I know my mail
has gotten thru as I have had responses to most of it. I don't think I
have forwarded to an MBL bbs though as there are not that many of them
in this area.
I would not be surprized if some small bug has gotten in as Gerard found
the NETROM/Gateway I/O problem and it was a typo that apparently must have
happenned when he was making some changes to the code??
Doug
----
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Date: Tue, 25 Jun 91 8:59:08 HST
Subject: encap route to a nameserver
Is there any NOS 'encap' route to a nameserver on the net? I'd like to be
able to do lookups in the ampr.org domain from 44.x.x.x hosts so that the
entire ampr.org list doesn't have to be stored in domain.txt on each host.
Antonio Querubin
tony@mpg.phys.hawaii.edu / ah6bw@uhm.ampr.org / querubin@uhunix.bitnet
----
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Date: Tue, 25 Jun 91 8:59:08 HST
Subject: encap route to a nameserver
Is there any NOS 'encap' route to a nameserver on the net? I'd like to be
able to do lookups in the ampr.org domain from 44.x.x.x hosts so that the
entire ampr.org list doesn't have to be stored in domain.txt on each host.
Antonio Querubin
tony@mpg.phys.hawaii.edu / ah6bw@uhm.ampr.org / querubin@uhunix.bitnet
----
From: Anders Klemets <klemets@BRAHMS.CODA.CS.CMU.EDU>
Date: Tue, 25 Jun 91 17:21:25 EDT
Subject: Re: mbox forwarding problems
Ok, I just looked at the source in forward.c and found that bug. I
introduced the bug when I added support for a 'forced' explicit
destination address that would override the "To:" line information
(the optional second argument on the mailbox name lines in the
forward.bbs file.)
The buffer that holds the that 'forced' address is overwritten by the
response from the BBS. Since the forced address is not at the
beginning at the buffer, sometimes one would not notice this
problem.
It is possible to see how exactly what happens thanks to Tonys packet
trace. The forwarding code, reads forward.bbs and gets the string
"kh6gpi" from the list of mailboxes to forward. The 'forced' address,
if specified, would be at the 7th position in that string. The pointer
for the forced address is set to point at that position (which is now
null.) When the first message is being sent, the response "OK 15545\n"
is read into the same buffer. The 'forced' address pointer now points
to the string "5\n". That is why the next message is incorrectly sent
to "SP 5". This then logically continues with "SP 6", "SP 7", etc.
Sorry about that folks...
The problem is easily solved by the insertion of a strdup() and free()
call in forward.c.
Here are the diffs:
*** forward.c~ Tue Jun 25 16:28:06 1991
--- forward.c Tue Jun 25 16:44:49 1991
***************
*** 430,440 ****
--- 430,442 ----
cp = &m->line[strlen(m->line)] + 1;
while(*cp != '\0' && isspace(*cp)) /* strip blanks */
++cp;
+ cp = strdup(cp);
for(i=1; i<=m->nmsgs; i++)
if(sendmsgtobbs(m, i, cp, bulletin) == -1) {
err = 1; /* abort */
break;
}
+ free(cp);
}
fclose(m->tfile);
m->tfile = NULLFILE;
----
From: karn@thumper.bellcore.com (Phil R. Karn)
Date: Tue, 25 Jun 91 18:35:05 EDT
Subject: archives moving to ucsd.edu
As I type this, I'm copying the anonymous FTP archives under /pub/ka9q
on thumper.bellcore.com to ucsd.edu, where they will appear in
/hamradio/ka9q. When I'm done I will delete the copies on thumper and
post a notice of the change.
Before I started the copy I moved a lot of what appeared to be
obsolete versions of stuff to backup tape. This shrunk the stuff by
half, to about 12 meg. In the unlikely event anybody needs any of the
stuff I deleted, yell. Better yet, take a look at the stuff now on
ucsd.edu. If any of it appears to be obsolete and/or redundant, please
let me know so I can minimize our disk usage on Brian's machine.
Ah, if only moving one's PHYSICAL possessions across the country were
this easy...
Phil
----
From: Anders.Klemets@cs.cmu.edu
Date: Tue, 25 Jun 91 17:53:34 -0400 (EDT)
Subject: Packeteers etc in California
I'll be going to California in August and might be interested in touring
some high tech companies and universities, or maybe just talk to some
packet people.
If you think you might like to meet me, please send me mail ASAP
specifying telephone numbers, suitable days, etc. (I'll be leaving in
about 40 hours, but I might be able to read some e-mail later, at least
when I get to San Diego.)
Anders W3/SM0RGV
----
From: pnm@neptune.acc.com (Patrick N. Medved)
Date: Tue, 25 Jun 91 17:15:30 EDT
Subject: Net in windows again.
I mailed this question earlier and still haven't got a
solution. I have found a little more information out
and the problem doesn't appear to be unique to the
Ethernet but is on the COM ports as well.
I am running the net.exe code from KA9Q on an IBM PC 386 clone.
I am trying to get it working under 3.0 windows with no luck.
The code works fine when I don't use windows.
The problem I am having is that the net.exe code seems to
drop packets after a while and my sessions (FTP or Telnet)
get hung. These happens on both the Ethernet and on
a direct connection to another PC using AX25.
On the Ethernet, I turn on tracing, and I show no input
coming in even though I am using etherfind on a SUN and
can see TCP retransmissions sent from the connected host.
I am using a Western Digital Board for the Ethernet board.
an load it via the following command:
wd8003e -w 0x78 0x280 0xd000
I believe I am just not configuring something in Windows
properly since this is the first time I've used them.
I have extended memory but am not using it. I believe
Windows is getting loaded into high memory properly
since I can type a command called mapmem
and it shows over 560K free, before running net.exe.
My config.sys looks like this:
FILES=45
buffers=35
device:\himem.sys
device=c:\windows\smartdrv.sys 2048 512.
Anybody who is more familiar with Windows and
can give me any suggestions would be appreciated.
pnm@saturn.acc.com
Pat Medved
----
From: karn@thumper.bellcore.com (Phil R. Karn)
Date: Tue, 25 Jun 91 22:08:43 EDT
Subject: move to ucsd.edu completed
The move of stuff from /pub/ka9q on thumper.bellcore.com to /hamradio/ka9q
on ucsd.edu has been completed. I maintained the file modification times
on all files and kept the "incoming" directory writeable by all. Let me
know if there are any problems.
Considerable thanks to Brian Kantor for making space available on his
machine. His support is greatly appreciated!
Phil
----
From: John Gayman <wa3wbu!john@uunet.UU.NET>
Date: Wed, 26 Jun 91 18:48:29 EDT
Subject: un-subscribe
I will be loosing my current mail path soon. Please un-subscribe me
from this list. Thanks.
-- John
----
From: gvdg@cdc.com (Gerard Van Der Grinten)
Date: Thu, 27 Jun 91 5:37:55 CDT
Subject: New NOS (0618)
Hello All,
I uploaded to wb3ffv and ucsd.edu my latest works on NOS (0618)
It includes all of Phil's 0618 plus the wormhole from Anders Sm0rgv/m
The wormhole works nice BUT you realy have to look at your configuration.
The oponent station has to use your Interface's ip address not your
stations one (if they are different) Further: if one or more interfaces
have the same callsign the first one in the interface table is used.
That is the Last onde defined!!! (New interfaces are added in the front)
I dont know who wants to try a "intergalactic" wormhole but i will
setup my end here at 127.179.122.10 pa0gri-12 real call pa0gri-10.
If tomcat would setup a link it would be:
attach axip ai0 256 [129.1779.122.10] w3iwi-12
and on my side
attach axip ai0 256 [128.138.10.100] pa0gri-12
so if someone overthere wants to connect to overhere:
connect ax1 pa0??? w3iwi-12 pa0gri-10
(or make a static route in ax route fir IP)
Anders, Thanks a lot. (i hade to make some minor mods to get it working
and build in/out trace code( i had 2 ip addresses))
The mailbox fis just came in so it will be there next time.
Regards, Gerard.
PS, Phil, while on the move, can you moove it to pa0gri dir?
You cal delete all previous versions exept the 0808 or 0820 (wichever
is still there as they contain the domain server stuff)
Happy moving....
----
Technical Details
Message-ID:
<9106271615.AA18044@infoac.rmi.de>Path:
arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gatewayShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 12f11c,6a09013fb465673c,start X-Google-Attributes: gid12f11c,public X-Google-ArrivalTime: 1991-06-27 10:13:40 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gateway From: DIGEST@infoac.rmi.DE (daily posting) Newsgroups: dnet.ham Subject: TCP-Group Digest 270691.1815 Message-ID: <9106271615.AA18044@infoac.rmi.de> Date: 27 Jun 91 16:15:18 GMT Sender: daemon@infoac.rmi.de Reply-To: dl3no@infoac.rmi.de Organization: RMI Net INFO.box Systems * Aachen * Hamburg * Flensburg Lines: 310