On Monday, 13 January 2020 19:38:33 GMT Dale wrote: > I hope I did this right. If not, tell me what to run. This is what I > get and I changed a few parts so I don't get hacked, or them trying to > at least. > > > root@fireball / # traceroute6 2606:4700:1::6813:894b > traceroute to 2606:4700:1::6813:894b (2606:4700:1::6813:894b), 30 hops > max, 80 byte packets > 1 2602:304:abab:9029:d66e:eff:fe42:55cf > (2602:304:abab:9029:d66e:eff:fe42:55cf) 0.769 ms 0.750 ms 0.745 ms > 2 * * * > 3 * * * [snip ...]
> 30 * * * > root@fireball / # > > > I'm not real good on traceroute but I'd assume the first hit is my > puter. The next step should be the router but it seems to die there. I > been suspecting the router anyway. The first hope would normally be the router. Instead of assuming check the IPv6 addresses and confirm. > What next? Ideas? The remaining hops in your test do not return ICMP packets. This could well be because intermediate nodes do not respond to ICMP for security reasons. ICMP has been abused to perform DDoS attacks over the years and many hosts just drop ICMP requests. Try running traceroute with --tcp or --udp instead, but you may need to run the command as root. Have a look at this online service to see what a normal traceroute6 response looks like: http://www.traceroute6.net/ If you get nowhere check from your PC, try the router. Modern routers usually provide network testing apps like traceroute. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
