| 1 |
Mick wrote: |
| 2 |
> On Monday, 13 January 2020 19:38:33 GMT Dale wrote: |
| 3 |
> |
| 4 |
>> I hope I did this right. If not, tell me what to run. This is what I |
| 5 |
>> get and I changed a few parts so I don't get hacked, or them trying to |
| 6 |
>> at least. |
| 7 |
>> |
| 8 |
>> |
| 9 |
>> root@fireball / # traceroute6 2606:4700:1::6813:894b |
| 10 |
>> traceroute to 2606:4700:1::6813:894b (2606:4700:1::6813:894b), 30 hops |
| 11 |
>> max, 80 byte packets |
| 12 |
>> 1 2602:304:abab:9029:d66e:eff:fe42:55cf |
| 13 |
>> (2602:304:abab:9029:d66e:eff:fe42:55cf) 0.769 ms 0.750 ms 0.745 ms |
| 14 |
>> 2 * * * |
| 15 |
>> 3 * * * |
| 16 |
> [snip ...] |
| 17 |
> |
| 18 |
>> 30 * * * |
| 19 |
>> root@fireball / # |
| 20 |
>> |
| 21 |
>> |
| 22 |
>> I'm not real good on traceroute but I'd assume the first hit is my |
| 23 |
>> puter. The next step should be the router but it seems to die there. I |
| 24 |
>> been suspecting the router anyway. |
| 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 |
> The remaining hops in your test do not return ICMP packets. This could well |
| 31 |
> be because intermediate nodes do not respond to ICMP for security reasons. |
| 32 |
> ICMP has been abused to perform DDoS attacks over the years and many hosts |
| 33 |
> just drop ICMP requests. Try running traceroute with --tcp or --udp instead, |
| 34 |
> but you may need to run the command as root. |
| 35 |
> |
| 36 |
> Have a look at this online service to see what a normal traceroute6 response |
| 37 |
> looks like: |
| 38 |
> |
| 39 |
> http://www.traceroute6.net/ |
| 40 |
> |
| 41 |
> If you get nowhere check from your PC, try the router. Modern routers usually |
| 42 |
> provide network testing apps like traceroute. |
| 43 |
> |
| 44 |
|
| 45 |
|
| 46 |
I found traceroute on the router. Thing is, it doesn't like IPv6 |
| 47 |
addresses. It keeps saying "illegal characters". I can't find it on |
| 48 |
the modem but I could have sworn it was on there. I've even looked in |
| 49 |
menus that wouldn't make sense for it to be there. Still can't find it. |
| 50 |
|
| 51 |
I tried traceroute6 with both options but get the exact same result. I |
| 52 |
went to the info the router has for IPv6. I used ping -6 and am pretty |
| 53 |
sure I can ping the router. It receives the ping from what I see. Then |
| 54 |
I went to the modem and tried the IPv6 addresses it showed there. After |
| 55 |
trying all it shows, ping isn't reaching the modem. It seems the router |
| 56 |
is getting it but not able to send it on up to the modem. |
| 57 |
|
| 58 |
That sort of makes sense since it shows a IPv6 connection to my puter |
| 59 |
but the info for the modem connection does not. I'll send you a reply |
| 60 |
off list. Maybe it will make sense with it being unedited. Subject |
| 61 |
line will stay the same tho. |
| 62 |
|
| 63 |
Dale |
| 64 |
|
| 65 |
:-) :-) |
Archives