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....
Attachment:
pgpRfImT6fucn.pgp
Description: PGP signature
- Follow-Ups:
- Re: traceroute bug ?
- From: "Gerold van Dijk" <[email protected]>
- Re: traceroute bug ?
- References:
- traceroute bug ?
- From: "Gerold van Dijk" <[email protected]>
- traceroute bug ?
- Prev by Date: Advantech touch screen driver
- Next by Date: Re: More information on scsi_cmd_cache leak... (bisect)
- Previous by thread: traceroute bug ?
- Next by thread: Re: traceroute bug ?
- Index(es):
 |