Date: Mon, 24 Jan 94 04:30:09 PST
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V94 #20
To: tcp-group-digest
TCP-Group Digest Mon, 24 Jan 94 Volume 94 : Issue 20
Today's Topics:
Borland compilers and BPQ
KISS ROM and Map file wanted
New 3COM cards
ping-pong convers for Linux FTP site gone ?
Reverse IP lookup, and domain name mapping. (help)
TCP MSS and TCP WIN settings (4 msgs)
TNOS Missing Function - NOT (2 msgs)
WAMPES FAQ ?
Wampes loopback (2 msgs)
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Sun, 23 Jan 1994 15:45:00 -0700 (MST)
From: Klarsen <klarsen@acca.nmsu.edu>
Subject: Borland compilers and BPQ
To: tcp-group@ucsd.edu
---------- Forwarded message ----------
Date: Sun, 23 Jan 94 15:40:53 MST
From:MAILER-DAEMON@NMSU.Edu
To: klarsen@acca.nmsu.edu
Subject: Returned mail: User unknown
----- Transcript of session follows -----
Connected to ucsd.edu:
>>> RCPT To:<tcpip-group@ucsd.edu>
<<< 550 <tcpip-group@ucsd.edu>... User unknown
550 <tcpip-group@ucsd.edu>... User unknown
----- Unsent message follows -----
Received: from acca.nmsu.edu (kazak.NMSU.Edu) by NMSU.Edu (4.1/NMSU-1.18)
id AA06518; Sun, 23 Jan 94 15:40:56 MST
Received: by acca.nmsu.edu (4.1/SMI-4.1)
id AA12326; Sun, 23 Jan 94 15:40:43 MST
Date: Sun, 23 Jan 1994 15:40:37 -0700 (MST)
From: Klarsen <klarsen@acca.nmsu.edu>
Subject: Borland compilers and BPQ
To: tcpip-group@ucsd.edu
Message-Id: <Pine.3.89.9401231512.A11611-0100000@kazak>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
I have just a little to say. Agreed there are things wrong with
Borlands C++ version 2.0 compiler and assembler but it was what I
purchased a couple years ago. I do all my C writing as a hobby and it has
never gotton so large as to be a problem for version 2.0. I reciently
compiled jnos version 1.10x15 without a single problem.
Now it seems we have Tnos which is Brian's answer to the ham
packet tcp/ip world and to enjoy it as I enjoy Johan's output, all I must
do is buy a new compiler? Forget it!
As I see how Tnos functions it looks to me it's too rich for my
blood. I have the version compiled by Brian, but it is so large I can't
run it on the computer I have...
On the wonderful G8BPQ switch. N5FAZ wrote the code that allows
nos to connect direct to the switch. It works fine! I have Jnos 1.10x15
connected to my bpq switch and it is no problem of any sort. Of course if
you don't want that function you can turn it off in config.h, provided
you have the right compiler.....but 2.0 works fine on all jnos.
73, de karl k5di@k5di.nm.usa.na
------------------------------
Date: Sun, 23 Jan 94 02:50:10 PST
From: algedi!gateway (gateway)
Subject: KISS ROM and Map file wanted
To: tcp-group@ucsd.edu
I need to find a KISS ROM image with a corresponding MAP file ( or something
similar ) so that I can patch the ROM image with new TXdelay and TXtail values.
I'm assuming that the KISS code will still have the automatic reset problem.
Also... what's the difference between the KISSS V4 and KISS V7 code on UCSD?
I've found a KISS V4 ROM image but can't determine what values to patch before
I burn the EPROM. The KISS V7 code does not contain a ROM image. Any info or
pointers to some code would be appreciated. Thanks.
73's de Jack - kf5mg
Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14
AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386
Dialup - kf5mg@tcet.unt.edu - work (looking for)
------------------------------
Date: Sun, 23 Jan 94 03:50:04 PST
From: algedi!gateway (gateway)
Subject: New 3COM cards
To: jangus@skyld.tele.com, tcp-group@ucsd.edu
The drivers are available from a number of sources but they are on my
system :
crompton.nadc.navy.mil in /pub/hamradio/packet/drivers
Files:
3c509.com - old driver (works fine here)
3c509a.com - new driver (had some problems on a system when rebooting)
pkdt11.zip - complete new drivers set
drivers.zip - complete old drivers set
Doug
------------------------------
Date: Mon, 24 Jan 94 08:09:58 CET
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: ping-pong convers for Linux FTP site gone ?
To: Fred Baumgarten <DC6IQ@INSU1.ETEC.UNI-KARLSRUHE.DE>,
Hi. Fred
Question whats happend to 129.13.109.160 the ftp site for ping-pong convers
is it closed ? its been not reachable for some time. or the ftp server
down.
Is there any new ftp site on the internet for anonymous ftp of the
ping-pong convers package. ?
Thanks..
Barry..
------------------------------
Date: Sun, 23 Jan 94 02:50:08 PST
From: algedi!gateway (gateway)
Subject: Reverse IP lookup, and domain name mapping. (help)
To: nos-bbs@hydra.carleton.ca
Hello all.
I am experience a few problems here. I use a SLIP server to gain access to
the internet. I have my own IP. (156.34.110.113) I have a problem. My
service provider (nbnet.nb.ca) does not have my IP mapped to a domain name
(ve1dln.nbnet.nb.ca, i'd assume), hence I cannot access certain telnet and
ftp sites, nor what was my alternate NNTP server.
Now for the questions. Can someone explain Reverse domain name resolution
to me? And, is there a way I can work around this with NOS? My service
provider does not seem to have it in their heart to soon map my IP, and I
am rather perturbed not being able to access some of these sites.
Any help would be appreciated.
Andy.
ve1dln@nbnet.nb.ca
------------------------------
Date: Sun, 23 Jan 94 02:50:03 PST
From: algedi!gateway (gateway)
Subject: TCP MSS and TCP WIN settings
To: kf5mg@kf5mg.ampr.org
Jack,
I don't know about the variants of my code, but I know this stuff is in
my version. Check tcpin.c, function proc_syn. Note the call to ip_mtu
with the remote IP address as argument. This function, defined in iproute.c,
returns the MTU of the interface that will be used to reach the specified
remote IP address.
Phil
------------------------------
Date: Sun, 23 Jan 94 15:50:04 PST
From: algedi!gateway (gateway)
Subject: TCP MSS and TCP WIN settings
To: kf5mg@kf5mg.ampr.org
mss is automatically lowered to mtu-40 based on the mtu of the first
hop in the routing table. For window, you would have to rely on
the congestion window I guess.
Some tcp stacks have started keeping mtu in the routing table (probably
only those that use the "new" mtu probing. Who is adding that to nos? :-)
milton
--
Milton Miller KB5TKF miltonm@austin.ibm.com
I never speak for IBM
------------------------------
Date: Sun, 23 Jan 94 05:50:03 PST
From: algedi!gateway (gateway)
Subject: TCP MSS and TCP WIN settings
To: tcp-group@ucsd.edu
Is there any way to assign a TCP WIN and TCP MSS setting per port? 9600b ports
can use larger Window's and Packets than 1200b ports. I'm sure that it's been
asked before but now that I've got a 9600b port going, I need to know what to
do to get the most out of the system. Thanks.
73's de Jack - kf5mg
Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14
AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386
Dialup - kf5mg@tcet.unt.edu - work (looking for)
------------------------------
Date: Sun, 23 Jan 94 14:50:10 PST
From: algedi!gateway (gateway)
Subject: TCP MSS and TCP WIN settings
To: tcp-group@ucsd.edu
Phil Karn writes:
> If the physical port is on the same machine as the TCP, then TCP
> already limits its MSS to avoid fragmentation out through that port.
> For example, if the other end advertises that it will accept a MSS of
> 1460 bytes but the MTU of the local interface you'll take to reach it
> is only 576 bytes, then the local TCP will use a MSS of only 536 bytes
> (576-40).
Well... that's what I thought should happen, but I tried it with JNOS
1.10x15. There's a IFCONFIG MTU command that I used to set the MTU to a
value of 256. The MSS was 1024 and the WINDOW was 4K. When I made a FTP
connect, I figured that NOS would use 256 byte packets, but it used 512
byte packets. The IFCONFIG MTU value didn't seem to have an effect.
I took a look at the TCP*.C files. There are only a couple of places
where the Tcp_mss and Tcp_window settings are assigned to a connection. It
appears that it would be easy to change this to a Tcp_mss.Interface and
Tcp_window.Interface so that you could use different Window and MSS sizes
per interface. The only problem is I don't see where in the TCP*.C code
that it references what Interface it's using. Any idea how to tell what
Interface a TCP socket is going to be using?
73's de Jack - kf5mg
Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14
AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386
Dialup - kf5mg@tcet.unt.edu - work (looking for)
------------------------------
Date: Sun, 23 Jan 94 02:50:06 PST
From: algedi!gateway (gateway)
Subject: TNOS Missing Function - NOT
To: tcp-group@ucsd.edu
j> : Why are you referring to yourself in the third person? Have you been
j> : reading "The Education of Henry Adams" or something?
j> I think Brian Lantz is talking about Brian Kantor.
j> (And I agree with Brian!)
Yes, I realized that after I woke up this morning and reread my own message
when it was sent to me by the list server. I guess it was kind of a stupid
mistake. Fortunately, all of the intricate stuff about the Borland products
was correct, but I suppose that is because I was paying attention when I was
typing that part.
-- Mike
------------------------------
Date: Sun, 23 Jan 94 14:50:05 PST
From: algedi!gateway (gateway)
Subject: TNOS Missing Function - NOT
To: tcp-group@ucsd.edu
Come on, guys! It's a little unfair to blame TNOS for not including standard
BorlandC 3.x DOS library functions in case you are running a version of the
compiler that is 2-3 years old! The before mentioned function is a part of
Borland's library for versions 3.0, 3.1, and 4.0.
Lack of memory.... Borland C 3.x and up uses EMS/XMS to permit virtually
unlimited source size. Is this file big, yep!
As for the commment about it being perfect out of the box, NOT! If you
expected that it would compile under every possible combination, your
expectations are based in the clouds! Your mileage will vary!
As for TNOS support, I suggest subscribing to TNOS-TOPICS and sending the
messages there. I don't know that Brian wants a lot of "how do you compile
this TNOS feature" stuff in this group. We don't want to abuse his
understanding.
/----------------------------------------------/
/ Brian A. Lantz/KO4KS /
/ /
/ Packet: KO4KS@KO4KS.#TPAFL.FL.USA.NA /
/ Internet: brian@lantz.cftnet.com /
/ { printf ("Hey Jude"); /
/ bad = !make; /
/ better = sad_song; } /
/----------------------------------------------/
------------------------------
Date: Sun, 23 Jan 94 16:11:26 GMT
From: paul@topsy.demon.co.uk (Paul Turvey)
Subject: WAMPES FAQ ?
To: tcp-group@ucsd.edu
Could someone please let me know where I can find an FAQ (or similar) for
Wampes (version 931106).
Many thanks
Paul
--
Paul Turvey | paul@topsy.demon.co.uk
| Amprnet: paul@g1pjj.ampr.org
| AX25: g1pjj@gb7zaa.#34.gbr.eu
------------------------------
Date: Sun, 23 Jan 94 14:50:07 PST
From: algedi!gateway (gateway)
Subject: Wampes loopback
To: tcp-group@ucsd.edu
I have ported wampes to the IBM RT (6150 & 6151) running AOS (BSD 4.3).
I seem to have run into a problem where packets send over the loopback
interface cause wampes to crash. The problem is that loopback->send
is defined as NULLFP in iface.c and ip_route() tries to call (loopback->send).
I have also compiled wampes in an RS6K (3.2.4) and the same problem exist.
Am I safe to assume that this is not a porting problem? (It still needs to
be fixed of course).
Jan PA3EFU/VK3CEX
------------------------------
Date: Sun, 23 Jan 94 05:50:06 PST
From: algedi!gateway (gateway)
Subject: Wampes loopback
To: tcp-group@ucsd.edu
Cc: JANJ@ACCIVM.acci.COM.AU
In a msg on <Jan 20 19:55>, Jan Jaeger of writes:
JJ> I have ported wampes to the IBM RT (6150 & 6151) running AOS (BSD 4.3).
Great! We have one of those dinosaurs here. Unfortunately, it is running AIX.
Still worse, it is running AIX v2, since AIX v3 needs the RS machines and will
not run on the RT machines. I think we have the native TCP/IP support, but no
one knows where the manual is, and no one at IBM seemed to care much about
locating another one even when we dangled small bills in front of them.
Is your port available at any FTP site, ideally UCSD.EDU?
-- Mike
------------------------------
Date: Mon, 24 Jan 1994 11:33:12 +1100
From: janj@acci.com.au (Jan Jaeger)
To: deyke@fc.hp.com, mikebw@bilow.uu.ids.net, tcp-group@ucsd.edu
Subject: Wampes on AOS
I have put a copy of my port to wampes on anonymous ftp.
It works, but is not to my satisfaction yet, there are
still a few things to be addressed such as the backspace
causes the screen to toggle between reverse video and normal
on an ibm6153, and the library with a few routines that AOS
does not have needs to be cleaned up.
At the moment it needs the following:
1) AOS
2) patchkit for AOS as available on various internet ftp sites
3) gnu make
4) gnu patch
5) gnu gcc 2.5.7 (other versions not tested)
6) one line 'uname' shell script that echo's AOS
The updates are on anonymous ftp at:
ftp.acci.COM.AU
in directory:
/pub/aos
as files:
wampes-aos001.patch.gz
wampes-aos001.tar.gz
In order to update wampes 931106 use the following procedure:
mkdir wampes
cd wampes
tar -xf /tmp/wampes-931106.tar
tar -xf /tmp/wampes-aos001.tar
patch -p1 < /tmp/wampes-aos001.patch
make
Dieter,
It might be better to wait until I have fixed the abovementioned
issues before integrating it in your 'ga' version. I think I will
have them fixed shortly.
Regards, Jan.
PA3EFU/VK3CEX janj@acci.com.au.
------------------------------
End of TCP-Group Digest V94 #20
******************************
******************************