Bug 7050
Summary: | Problem with traceroute | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | bpinaud |
Component: | traceroute | Assignee: | Crutcher Dunnavant <crutcher> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-04 16:07:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
bpinaud
1999-11-16 18:45:29 UTC
This sounds like a firewall configuration problem. Different traceroute tools may happen to implement their functionality using slightly different network protocols (e.g. ICMP vs. UDP). It's not a bug in these tools - if you want them to work, you will have to configure your firewall accordingly. |