Changes between Initial Version and Version 13 of Ticket #7972
- Timestamp:
- Mar 24, 2016, 4:30:05 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7972
-
Property
Status
changed from
new
toclosed
-
Property
Attachments.isobsolete
changed from
0
to1
- Property Cc markd@… added
-
Property
Resolution
changed from
to
fixed
- Property Port libnet11 added
-
Property
Status
changed from
-
Ticket #7972 – Description
initial v13 1 1 tcptraceroute reports a failure when attempting to trace to a site: 2 2 3 {{{ 3 4 fatman:~ dsinn$ sudo tcptraceroute www.seanet.com 80 4 5 Selected device en1, address 192.168.42.241, port 59746 for outgoing packets 5 6 Tracing the path to www.seanet.com (64.38.166.88) on TCP port 80, 30 hops max 6 7 libnet_write failed? Attempted to write 40 bytes, only wrote -1 7 8 }}} 8 9 9 10 This occurs via both en0 and en1. … … 11 12 Both libnet11 and tcptraceroute build fine: 12 13 14 {{{ 13 15 fatman:~ dsinn$ sudo port install libnet11 14 16 ---> Fetching libnet11 … … 36 38 ---> Activating tcptraceroute 1.5beta4_0 37 39 ---> Cleaning tcptraceroute 40 }}} 38 41 39 42 I have no other installed port's that rely on libnet11, so I am unable to test if it is tcptraceroute or libnet11 that is failing. The system is a MacBookPro running 10.4.5.