From: Alexis <alexis@attla.net.ar>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: INCOMPLETE [ 8bytes] with two src addresses!
Date: Fri, 27 Feb 2004 15:41:01 -0300 [thread overview]
Message-ID: <1077907260.1647.18.camel@pepelui.baicom> (raw)
In-Reply-To: <1077906138.2526.48.camel@anduril.intranet.cartel-securite.net>
ok, its my mistake when i said first step, but we have 2 confrontations
here.
in traceroute ttl=1 is only for the first packet (thats what i said
about the first step)
icmp info throws code 11 , thats why i assumed this was an traceroute.
but like you said, traceroutes uses icmp or icmp and udp like unix does.
ICMP src and dst addresses are the ones that change at each hop, but the
addresses (at ip) involved in the udp packets are always the same.
(apparently this not happen here)
Ive been reading about magic number, but its not related at all.
so , i dont know what it is.
On Fri, 2004-02-27 at 15:22, Cedric Blancher wrote:
> Le ven 27/02/2004 à 19:10, Alexis a écrit :
> > at first sight its the first step of a traceroute
>
> I don't think so.
> When you traceroute, your first step is your default gateway that sends
> you ICMP TTL exceeded back with an IP within your network. We can see :
>
> > SRC=216.200.115.66
> > DST=80.5.144.39
>
> As they do not belong to the same network, it's not the first step, but
> can be a further one.
>
> Moreover, usual traceroute tools uses ICMP echo (Windows) or UDP (Unix)
> probes. We have TCP here. BTW, TCP is damn cool to traceroute when you
> target a host with a known opened port (e.g. www.microsoft.com) :)))
--
Tus problemas no se pueden resolver en el mismo
nivel mental que tenías cuando los creaste.
Albert Einstein
next prev parent reply other threads:[~2004-02-27 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 17:56 INCOMPLETE [ 8bytes] with two src addresses! Graham Swallow
2004-02-27 18:10 ` Alexis
2004-02-27 18:22 ` Cedric Blancher
2004-02-27 18:41 ` Alexis [this message]
2004-02-27 19:17 ` Cedric Blancher
2004-02-27 19:33 ` David Cannings
2004-02-27 18:15 ` Cedric Blancher
2004-02-27 19:05 ` INCOMPLETE [ 8bytes] with two src addresses! Faked Packet? Graham Swallow
2004-02-29 9:17 ` Strange log info from iptables ? Bo Jacobsen
2004-02-29 10:31 ` Antony Stone
2004-02-29 11:09 ` Cedric Blancher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1077907260.1647.18.camel@pepelui.baicom \
--to=alexis@attla.net.ar \
--cc=blancher@cartel-securite.fr \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox