Date: Sun, 23 Jan 94 04:30:06 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 #19
To: tcp-group-digest
TCP-Group Digest Sun, 23 Jan 94 Volume 94 : Issue 19
Today's Topics:
JNOS, TNOS, and other DOS'isms
NO TNOS sample files
Reverse IP lookup, and domain name mapping. (help) (2 msgs)
TCP MSS and TCP WIN settings
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: Sat, 22 Jan 1994 09:53:59 -0500
From: "Brandon S. Allbery" <bsa@kf8nh.wariat.org>
Subject: JNOS, TNOS, and other DOS'isms
To: tcp-group@ucsd.edu
In your message of Fri, 21 Jan 1994 20:56:00 GMT, you write:
+---------------
|people were not arguing over it. No one knows what the future is going to look
|like, but I personally hope it looks a lot more like Unix or OS/2 than Windows.
| My own view is that it is up to the people who write the source code.
+------------->8
Only in part; but as always, the final decision is up to the people who *use*
the code. There are several choices for Unix "NOS" (in quotes because I
include kernel-based solutions that don't involve dedticated NOS executables)
already; OS/2 NOS development seems to be lagging, and I'm not sure what there
is (native) for MS-Windows, if anything; but, should those environments have
NOS versions available, which one will be "the" future NOS environment will
depend on how many people choose which environments.
(Nor is this specific to NOS. The same considerations apply to the choice of
environment for any other application, whether it be amateur radio networking
or databases.)
What the developers do is enable that decision to be made; they don't make the
decision for you.
++Brandon
--
Brandon S. Allbery kf8nh@kf8nh.ampr.org bsa@kf8nh.wariat.org
"MSDOS didn't get as bad as it is overnight -- it took over ten years
of careful development." ---dmeggins@aix1.uottawa.ca
------------------------------
Date: Sun, 23 Jan 94 01:50:03 PST
From: algedi!gateway (gateway)
Subject: NO TNOS sample files
To: tcp-group@ucsd.edu
Caveat: I have not found any sample autoexec or cfg files for TNOS at ucsd or lantz's
location. Anyone not familiar with creating such will be stuck for a while.
-Mike
------------------------------
Date: Sun, 23 Jan 94 17:49:40 -0400
From: "Andy Silliker" <ve1dln@jupiter.sun.csd.unb.ca>
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: Sat, 22 Jan 1994 16:58:56 -0800
From: Phil Karn <karn@qualcomm.com>
Subject: Reverse IP lookup, and domain name mapping. (help)
To: ve1dln@jupiter.sun.csd.unb.ca
Andy,
You're basically stuck. The only quick workaround is to log into
another machine on the Internet that does have a reverse DNS entry and
issue your FTPs from there.
The policy of denying anonymous FTP access to sites that don't have
reverse DNS entries has irritated me for some time. Not only because
of the egregious violation of the Internet Principle (be conservative
in what you send, liberal in what you accept) but also because of the
hostility to personal privacy that seems to underly this policy.
A few years ago there was a big outcry against the government
(specifically the FBI) attempting to find out what books people
checked out from libraries. The librarians quite properly resisted
this intrusion into their patrons' personal privacy. I'm appalled by
the opposite trend by those who run anonymous FTP sites -- the closest
Internet equivalent to public libraries. Keeping statistics on how
often a file is accessed in order to better manage the space allocated
to anonymous FTP is one thing, but keeping detailed logs of who
obtains what file is unnecessary once a server has been debugged.
I've had a few ideas on how one might use NOS to build anonymity into
IP along the lines of the existing "cypherpunk" anonymous
remailers. This would let you pull files from an anonymous FTP site
without having to use your real IP address. And of course, the IP
address that the FTP site sees could have an inverse DNS entry.
Phil
------------------------------
Date: Sat, 22 Jan 1994 20:57:31 -0800
From: Phil Karn <karn@qualcomm.com>
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
------------------------------
End of TCP-Group Digest V94 #19
******************************
******************************