Re: Traceroute

From: John Galt (everbeeninlove_at_gmail.com)
Date: 02/25/05

  • Next message: Capixaba: "Re: Bypassing NTFS ACL" 
    Date: Fri, 25 Feb 2005 07:53:10 +0530
To: pen-test@securityfocus.com

    I am not sure about this, but as far as i know, record route is not a
    mandatory directive according to standards, and routers are free to
    ignore it.

    Talking about traceroute, it works by incrementing the ttl by one each
    time, so that each packet travels one hop further before being dropped
    and an ICMP message coming back to the sender, right? However, IP
    itself is designed so that each route is decided when the packet is
    transmitted, not like in a VC. Thus, does a traceroute like that make
    much of a sense? Since you never know what route your other packets,
    or even all packets involved in the trace, took?

    pray forgive my foolishness everybody!

    regards

    John Galt

    On Wed, 23 Feb 2005 21:49:03 +0100, Chris <uid0@free.fr> wrote:
    > Hi,
    >
    > I've just got a little question which isn't really linked to
    > pen-testing: do you know any alternative to the normal UDP/TCP/ICMP
    > traceroute to trace the route of a packet? I'm already aware of the IP
    > Record Route option, but is there any other hack that you guys would be
    > aware of?
    >
    > Thanks.
    >
    > Christian Vincenot
    >
    > --
    > "Portability is for people who cannot write new programs"
    > -me [Linus Torvalds], right now (with tongue in cheek)
    >
    >

  • Next message: Capixaba: "Re: Bypassing NTFS ACL"

    Relevant Pages

    • Re: traceroute economical with information
      ... This means it will try to find a route for up to 30 hops - the actual route ... Can you ping the bbc - if so, traceroute will eventually get to it, although ... The way traceroute works is first to send a ping packet with a time-to-live ...
      (comp.sys.acorn.networking)
    • Kernel Panic due to NF_IP_LOCAL_OUT handler calling itself again
      ... option, I am using kernel 2.6.5, without smp and preemption support. ... describing the source route and the route error. ... ensuring that the packet makes it to the next hop. ... local_out is an icmp dest unreach. ...
      (Linux-Kernel)
    • Re: routing bug?
      ... In -current protocol cloning is gone and pointers to an rtentry are no ... This causes a route lookup to be done for ... UDP packet is being sent to determine the source address and thus it ... storing the rtentry pointer in the inpcb at all. ...
      (freebsd-current)
    • Re: sent an invalid ICMP type 11, code 0 error to a broadcast: 0.0.0.0 on lo?
      ... > If you ping an IP address on your computer, ... > the lo route filtering altogether. ... ICMP packet, with source address on this same box. ... IF that packet comes from the interface where the default ...
      (Linux-Kernel)
    • Re: iptables: fake ip using DNAT and SNAT
      ... Route NAT is no longer supported in Linux 2.6." ... When a packet is destined to an address in this network, the packet is routed to the ham0 inteface. ... No "translation" necessary here, only adding and stripping IP headers. ... This is starting to get ugly, but I had to try:) Now there seems to bee som issues about the source based routing. ...
      (comp.os.linux.networking)