Drugi raz w przeciągu kilkunastu dni spotyka mnie blokada trasy do 1.1.1.2. Drugi DNS usługi Cloudflare 1.0.0.2 jest w tym czasie osiągalny. Rozwiązaniem jest restart sesji PPPoE w FB3.
Przed restartem sesji:
pi@rpi:~ $ traceroute -n 1.0.0.2
traceroute to 1.0.0.2 (1.0.0.2), 30 hops max, 60 byte packets
1 192.168.76.1 0.500 ms 0.513 ms 0.617 ms
2 83.1.5.5 7.844 ms 7.805 ms 7.755 ms
3 80.50.122.81 5.841 ms 5.576 ms 80.50.18.81 5.306 ms
4 195.116.35.189 5.076 ms * *
5 193.251.154.18 9.432 ms * 193.251.143.154 8.844 ms
6 162.158.100.27 7.155 ms 162.158.100.7 8.767 ms 162.158.100.25 8.541 ms
7 162.158.100.61 8.140 ms 1.0.0.2 2.711 ms 162.158.100.61 4.191 ms
pi@rpi:~ $ traceroute -n 1.1.1.2
traceroute to 1.1.1.2 (1.1.1.2), 30 hops max, 60 byte packets
1 192.168.76.1 0.446 ms 0.429 ms 0.493 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 *^C
Po restarcie sesji PPPoE:
pi@rpi:~ $ traceroute -n 1.1.1.2
traceroute to 1.1.1.2 (1.1.1.2), 30 hops max, 60 byte packets
1 * * *
2 83.1.5.5 7.283 ms 7.234 ms 7.190 ms
3 80.50.122.81 4.366 ms 4.407 ms 4.202 ms
4 * * *
5 * * 193.251.154.18 8.499 ms
6 162.158.100.67 7.556 ms 162.158.100.59 4.872 ms 193.251.154.18 4.816 ms
7 1.1.1.2 3.584 ms 162.158.100.27 6.139 ms 1.1.1.2 4.779 ms
Orange, WTF?
