Package: traceroute-nanog
Version: 6.3.10-2
Tags: patch
Severity: wishlist

Graeme Hewson has submitted two patches to Ubuntu to address issues
found with traceroute-nanog.  Please find attached the following two
dpatch files generated from the submitted patches:

30_respect-prohibition.dpatch
   If traceroute receives ICMP type 3 code 9 or 10 (communication
with destination network or host administratively prohibited), the
trace doesn't finish and further probes are sent.

40_workaround-RFC_792-noncompliance.dpatch
   Some hops aren't reported because the hosts don't follow the RFC
properly and the checking of the ICMP time exceeded packets for
validity is (arguably) too strict.

I have been advised that the second patch has been accepted upstream,
but am unaware of the status of the first patch.

--
Emmet HIKORY

Attachment: 30_respect-prohibition.dpatch
Description: Binary data

Attachment: 40_workaround-RFC_792-noncompliance.dpatch
Description: Binary data

Reply via email to