| |
PA2AGA > TCPDIG 09.07.97 08:07l 99 Lines 3320 Bytes #-10572 (0) @ EU
BID : TCP_97_36
Read: GUEST
Subj: TCP-Group Digest 97/36
Path: DB0RGB<DB0ABH<DB0SRS<DB0FP<DB0ERF<DB0HSK<PI8DRS<DB0ACC<ON4RAT<ON5VL<
ON4AIC<ON1AEO<ON6AR<PI8HWB<PA0RVR<PI8VAD<PI8VNW
Sent: 970709/0101Z @:PI8VNW.#ZH2.NLD.EU #:10307 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA37834 ; Tue, 08 Jul 97 23:54:39 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00002435 ; Sat, 12 Apr 97 14:26:55 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00002429 ; Sat, 12 Apr 97 14:16:39 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.6.1) with SMTP
id AA00009352 ; Sat, 12 Apr 97 14:16:32 MET
Date: Sat, 12 Apr 97 14:06:07 MET
Message-Id: <tcp_97_36>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 97/36
X-BBS-Msg-Type: B
TCP-Group Digest Sat, 12 Apr 97 Volume 97 : Issue 36
Today's Topics:
http://www.cc.columbia.edu/~fuat/cuarc/mailing-lists.html
What Protocole traceroute use ?
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: Fri, 11 Apr 1997 20:15:03 -0700 (PDT)
From: ve7axy@vcn.bc.ca
Subject: http://www.cc.columbia.edu/~fuat/cuarc/mailing-lists.html
subscribe to list
thank you 73 de Walter
ve7axy
------------------------------
Date: Fri, 11 Apr 1997 16:32:14 +0000 (GMT)
From: Ron Atkinson <n8fow@hamgate.cc.wayne.edu>
Subject: What Protocole traceroute use ?
My mailer said Mike Bilow said this:
>
> Traceroute relies upon ICMP replies. It is a very bad idea to have
firewalls
> blocking ICMP as a matter of course, and ICMP is almost always permitted.
Actually it's a good idea to block ICMP at firewalls for security reasons.
Every good firewall I know of does that. You only want to allow it to pass
through (usually through a VPN) when you are connecting with a known
trusted distant end, usually another business that you're working with.
Firewalls actually either modify the kernel and TCP/IP networking anyways,
or they just plain replace it with their own versions that are more secure
and have features removed (such as IP forwarding, RPC, X, etc..).
> If traceroute is implemented by using ICMP Echo Request frames to provoke
the
> ICMP Time Exceeded replies, then this would likely pass your firewall.
It won't pass through a good firewall. Maybe an incorrectlly configured
packet filtering one, but not an application layer.
> -- Mike
-----
Disclaimer: The views stated above are my own and do not reflect those
of Computer Task Group, Inc. or the Detroit Edison Company.
Ron Atkinson - AtkinsonR@DetroitEdison.com (313) 235-3558
------------------------------
End of TCP-Group Digest V97 #36
******************************
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
| |
