| |
PA2AGA > TCPDIG 20.07.97 01:11l 106 Lines 3477 Bytes #-10286 (0) @ EU
BID : TCP_97_48
Read: GUEST
Subj: TCP-Group Digest 97/48
Path: DB0RGB<DB0MAK<DB0SON<DB0ERF<DB0HSK<PI8DRS<PI8DAZ<PI8APD<PI8WNO<PI8GCB<
PI8WFL<PI8VNW
Sent: 970719/1735Z @:PI8VNW.#ZH2.NLD.EU #:17679 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA38506 ; Sat, 19 Jul 97 17:21:17 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.64/7.1) with SMTP
id AA00003409 ; Sat, 19 Jul 97 15:21:47 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00003295 ; Sat, 19 Jul 97 14:52:20 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.64/7.6.1) with SMTP
id AA00009615 ; Sat, 19 Jul 97 14:52:19 MET
Date: Sat, 19 Jul 97 14:30:30 MET
Message-Id: <tcp_97_48>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 97/48
X-BBS-Msg-Type: B
TCP-Group Digest Wed, 30 Apr 97 Volume 97 : Issue 48
Today's Topics:
Unreachable code Administratively Prohibited (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 ftp.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: Tue, 29 Apr 1997 20:30:07 -0500
From: Steve Sampson <ssampson@cool.site.net>
Subject: Unreachable code Administratively Prohibited
This encap really sucks.
It seems every week some node argues with me. What's the
purpose of this message, and how can we kill the people who
run the nodes that issue them :-)
Why would 151.164.7.6 care if I'm trying to get to dfwgate.co.unt.edu?
I can get to other sites just fine. A new one today, is some gomer is
preventing me to route mail to 44.78.4/24 land from juno.com.
What's better than encap, and how do we deploy it :-)
I'm of the opinion it's too hard, and I'm going back to radio only...
Steve
------------------------------
Date: Wed, 30 Apr 97 07:14:00 -0000
From: mikebw@bilow.bilow.uu.ids.net (Mike Bilow)
Subject: Unreachable code Administratively Prohibited
Steve Sampson wrote in a message to Mike Bilow:
SS> This encap really sucks.
SS> It seems every week some node argues with me. What's the
SS> purpose of this message, and how can we kill the people who
SS> run the nodes that issue them :-)
SS> Why would 151.164.7.6 care if I'm trying to get to
SS> dfwgate.co.unt.edu? I can get to other sites just fine. A
SS> new one today, is some gomer is preventing me to route mail
SS> to 44.78.4/24 land from juno.com.
SS> What's better than encap, and how do we deploy it :-)
SS> I'm of the opinion it's too hard, and I'm going back to
SS> radio only...
An obvious -- and vicious -- kludge would be to appropriate one of the more
standard port numbers that all routers pass and use it for something other
than
its assigned purpose. Who really needs ECHO or DISCARD, anyway? Note that I
am not recommending that we actually do this, but it is worth pointing out as
an option.
-- Mike
------------------------------
End of TCP-Group Digest V97 #48
******************************
You can send your message for this bulletin
to: tcp-group@pa2aga on .AMPR.ORG-net
or: tcpaga@pi8vnw.#zh2.nld.eu on BBS-net
------
NOT TO: pa2aga@pa2aga or pa2aga@pi8vnw.#zh2.nld.eu PLEASE!!
It will get posted automatically within a few days
Read previous mail | Read next mail
| |
