1 |
On Monday, 13 January 2020 19:38:33 GMT Dale wrote: |
2 |
|
3 |
> I hope I did this right. If not, tell me what to run. This is what I |
4 |
> get and I changed a few parts so I don't get hacked, or them trying to |
5 |
> at least. |
6 |
> |
7 |
> |
8 |
> root@fireball / # traceroute6 2606:4700:1::6813:894b |
9 |
> traceroute to 2606:4700:1::6813:894b (2606:4700:1::6813:894b), 30 hops |
10 |
> max, 80 byte packets |
11 |
> 1 2602:304:abab:9029:d66e:eff:fe42:55cf |
12 |
> (2602:304:abab:9029:d66e:eff:fe42:55cf) 0.769 ms 0.750 ms 0.745 ms |
13 |
> 2 * * * |
14 |
> 3 * * * |
15 |
[snip ...] |
16 |
|
17 |
> 30 * * * |
18 |
> root@fireball / # |
19 |
> |
20 |
> |
21 |
> I'm not real good on traceroute but I'd assume the first hit is my |
22 |
> puter. The next step should be the router but it seems to die there. I |
23 |
> been suspecting the router anyway. |
24 |
|
25 |
The first hope would normally be the router. Instead of assuming check the |
26 |
IPv6 addresses and confirm. |
27 |
|
28 |
|
29 |
> What next? Ideas? |
30 |
|
31 |
The remaining hops in your test do not return ICMP packets. This could well |
32 |
be because intermediate nodes do not respond to ICMP for security reasons. |
33 |
ICMP has been abused to perform DDoS attacks over the years and many hosts |
34 |
just drop ICMP requests. Try running traceroute with --tcp or --udp instead, |
35 |
but you may need to run the command as root. |
36 |
|
37 |
Have a look at this online service to see what a normal traceroute6 response |
38 |
looks like: |
39 |
|
40 |
http://www.traceroute6.net/ |
41 |
|
42 |
If you get nowhere check from your PC, try the router. Modern routers usually |
43 |
provide network testing apps like traceroute. |
44 |
|
45 |
-- |
46 |
Regards, |
47 |
|
48 |
Mick |