From: "Gerold van Dijk" <gerold@sicon-sr.com>
To: <Valdis.Kletnieks@vt.edu>
Cc: <linux-kernel@vger.kernel.org>, "Alwin" <d_j_d@hotmail.com>,
"oswin martopawiro" <o_martopawiro@hotmail.com>,
"guno" <guno@sicon-sr.com>, "albert" <albert@sicon-sr.com>
Subject: Re: traceroute bug ?
Date: Sun, 29 Jan 2006 07:37:23 -0300 [thread overview]
Message-ID: <002201c624bf$fdcc83b0$1701a8c0@gerold> (raw)
In-Reply-To: 200601271852.k0RIqaC0023706@turing-police.cc.vt.edu
Dear Valdis et.al.,
thanks for biting! I really tested this thing thoroughly, with different
distributions (Red Hat, SuSE 8.0 and 10.0) on different machines with the
firewalls completely open, and without any router or switch involved: cross
cable straight from one machine to another!
IF I ONLY CHANGE TO ANOTHER IP BLOCK (E.G. 206.253.5.64/24) OR A PRIVATE
RANGE (E.G. 192.168.1.0/24) THE TRACEROUTE WORKS FINE! SO IT IS SPECIFICALLY
THIS 207.253.5.0/24 BLOCK THAT DOES NOT TRACEROUTE WITHIN IT'S OWN RANGE!
Not only the subnetwork 207.253.5.64/27 but the whole class C block
207.253.5.0/24 !?
Just to be complete: we CAN ping normally within this network!
But the traceroute simple displays "* * *" row after row!
Of course it is not that urgent a problem, cause what is the sense of doing
a traceroute within your own network anyway? But I thought it might be
useful to report this strange thing!
Thank you all for your time!
Regards,
Gerold H. van Dijk
Research & Training Manager
SICON; Suriname Information &
Communication Network
Verl.Gemenelandsweg 163
Paramaribo, Suriname
South America
(+597) 464791
(+597) 491510 (fax)
(+597)(0) 8579216 (gsm)
gerold@sicon-sr.com
gerold_vandijk@hotmail.com
On Fri, 27 Jan 2006 15:38:23 -0300, Gerold van Dijk said:
> Why can I NOT do a traceroute specifically within my own (sub)network
>
> 207.253.5.64/27
>
> with any distribution of Linux??
OK.. I'll bite. What happens when you try? And why are you posting here -
is
there *any* evidence that there is a Linux kernel bug involved?
The output of 'ifconfig' and 'netstat -r -n' would likely be helpful, as
would
proof that the host(s) you're tracerouting from and to are *not* running a
firewall that interferes with the way traceroute functions. (It's amazing
how
many people block all ICMP, then wonder why traceroute doesn't work... ;)
Watching the wire with 'tcpdump' and/or 'ethereal' can also help....
next prev parent reply other threads:[~2006-01-29 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 18:38 traceroute bug ? Gerold van Dijk
2006-01-27 18:52 ` Valdis.Kletnieks
2006-01-29 10:37 ` Gerold van Dijk [this message]
2006-01-27 18:57 ` Jesper Juhl
2006-01-27 21:45 ` OT: " ed
2006-01-27 18:59 ` linux-os (Dick Johnson)
2006-01-27 19:34 ` Kyle Moffett
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='002201c624bf$fdcc83b0$1701a8c0@gerold' \
--to=gerold@sicon-sr.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=albert@sicon-sr.com \
--cc=d_j_d@hotmail.com \
--cc=guno@sicon-sr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o_martopawiro@hotmail.com \
/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