Opened 11 years ago

Last modified 6 years ago

#3210 new bug

traceroute does not work here

Reported by: tigerdog Owned by: axeld
Priority: normal Milestone: R1
Component: Network & Internet Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

traceroute command does not work. First intermediate node information is displayed normally. All subsequent nodes display "* * *" with 5-second intervals between "*".

Welcome to the Haiku shell.

~> traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.45.100
traceroute to google.com (74.125.45.100), 30 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  1.643 ms  -0.096 ms  0.667 ms
 2  * * *
 3  * * *

~> 
~> 

Traceroute works fine on same computer from Xubuntu 8.10, Win2K and Zeta.  Tested on real hardware:  AMD 64x2 4200+, ECS Mainboard with nVidia chipset, nVidia Ethernet on-board.



Change History (8)

comment:1 by haiqu, 10 years ago

Working here.

~/code/OpenKernel/haiku> traceroute google.com

traceroute: Warning: google.com has multiple addresses; using 74.125.45.100

traceroute to google.com (74.125.45.100), 30 hops max, 40 byte packets

1 201.2.96.58.exetel.com.au (58.96.2.201) 17.758 ms 15.130 ms 14.159 ms

2 vlan202.33bhc76f000.optus.net.au (59.154.44.77) 14.267 ms 15.577 ms 13.241 ms

3 google.sd13.optus.net.au (119.225.36.2) 218.959 ms 251.597 ms 219.937 ms

4 66.249.95.232 (66.249.95.232) 219.901 ms 222.638 ms 219.723 ms

5 66.249.95.166 (66.249.95.166) 230.466 ms 224.295 ms 230.265 ms

6 216.239.43.212 (216.239.43.212) 288.890 ms 221.843 ms 220.663 ms

7 216.239.43.81 (216.239.43.81) 259.546 ms 261.997 ms 72.14.232.97 (72.14.232.97) 259.602 ms

8 72.14.239.90 (72.14.239.90) 269.432 ms 269.958 ms 267.474 ms

9 209.85.254.243 (209.85.254.243) 275.539 ms 300.672 ms 275.916 ms

10 209.85.253.145 (209.85.253.145) 280.775 ms 209.85.253.133 (209.85.253.133) 290.160 ms 209.85.253.137 (209.85.253.137) 282.523 ms

11 yx-in-f100.google.com (74.125.45.100) 279.045 ms 278.476 ms 275.382 ms

comment:2 by luroh, 9 years ago

tigerdog, is this still a problem?

comment:3 by Ziusudra, 9 years ago

Well, I don't know about tigerdog, but I've got it here on R1A2 on hardware.

My connection is computer - router - satelite modem. Taking out the router only removes that hop leaving * * * for all hops.

Windows 7 tracert works as expected showing info for all hops.

How can I help?

comment:4 by luroh, 9 years ago

39059, gcc2, vmware

~> traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.39.103
traceroute: Can't find any network interfaces

comment:5 by luroh, 9 years ago

hrev39750 and traceroute works for me again, most likely due to phoudoin's hrev39747. tigerdog, Ziusudra?

comment:6 by Ziusudra, 9 years ago

Downloading hrev39748 nightly and will try it tonight.

comment:7 by Ziusudra, 9 years ago

hrev39748 gcc2h hardware

Same as before:

20:03:32 ~> traceroute dev.haiku-os.org
traceroute to vmdev.haiku-os.org (188.40.89.174), 30 hops max, 40 byte packets
 1  192.168.2.1 (192.168.2.1)  0.513 ms  0.473 ms  0.592 ms
 2  * * *
 3  * * *
    <snip>
30  * * *
20:12:18 ~> 

comment:8 by mmadia, 6 years ago

hrev46791 traceroute fails with output similar to Ziusudra's above comment.

Note: See TracTickets for help on using tickets.