public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] traceroute not working
Date: Fri, 22 Feb 2013 15:30:13 -0500	[thread overview]
Message-ID: <5127D555.5000602@libertytrek.org> (raw)
In-Reply-To: <CAJ0EP40Ke2g-+zmaNKAB3L3=gf+gtiSRc=xonhnABPf8L_xbeQ@mail.gmail.com>

On 2013-02-22 12:18 PM, Mike Gilbert <floppym@gentoo.org> wrote:
> Unix traceroute normally operates by sending UDP packets to
> high-numbered ports with successively larger TTL values. You'll need
> to make sure you are allowing outbound UDP traffic as well.

Thanks guys - I had forgotten about this (haven't used it in a while)...

I forgot that I had to specify -I to designate using ICMP protocol...

duh...

Sorry for the noise...

Now to pose the real question I have (the reason I needed to use 
traceroute in the first place) in a new thread...


      reply	other threads:[~2013-02-22 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 15:51 [gentoo-user] traceroute not working Tanstaafl
2013-02-22 16:28 ` Mick
2013-02-22 16:40 ` Michael Mol
2013-02-22 17:18 ` Mike Gilbert
2013-02-22 20:30   ` Tanstaafl [this message]

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=5127D555.5000602@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.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