David O'Brien wrote: > Do you know how traceroute works?? For one, the destination host cannot > be listening on the port used. And you know that each progressive > traceroute packet sent out bumps the destination port by one, to help > trace the ICMP "time exceeded" / "port unreachable" responses. Only UDP traceroute requires that the port not be listened to (otherwise you wouldn't get a packet back). If using TCP you will get a packet back (RST/SYNACK/ICMP-portunreachable etc) whether the port is open or not. In theory at least.. -- Hroi Sigurdsson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Should URL's be pervasive. Joseph Mallett
- Re: Should URL's be pervasive. Chris Costello
- Re: Should URL's be pervasive. Chris Costello
- Re: Should URL's be pervasive. Leo Bicknell
- Re: Should URL's be pervasive. Chris Costello
- Re: Should URL's be pervasive. Leo Bicknell
- Re: Should URL's be pervasive. David O'Brien
- Re: Should URL's be pervasive. Steve Roome
- Re: Should URL's be pervasive. David O'Brien
- Re: Should URL's be pervasive. Richard Hodges
- Re: Should URL's be pervasive. Hroi Sigurdsson
- Re: Should URL's be pervasive. Bruce A. Mah
- Re: Should URL's be pervasive. Leo Bicknell
- Re: Should URL's be pervasive. Matthew D. Fuller
- Re: Should URL's be pervasive. Richard Hodges
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Sansonetti Laurent
- Re: Should URL's be pervasive. Charlie Root
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Kenneth P. Stox