On 2023-04-18 11:34, Per Jessen wrote:
Carlos E. R. wrote:
I have no idea which is the IPv6 address of the router or how to find it.
Maybe this will do the trick -
ip -6 neigh | grep router
Nah. Telcontar:~ # ip -6 neigh fe80::ceed:dcff:fe05:80d4 dev eth0 lladdr cc:ed:dc:05:80:d4 router STALE Telcontar:~ # Not the one I want. Where do you expect the word "router" to come from, from the DNS server? :-? Ah. Too early, just booted the machine. Telcontar:~ # traceroute6 google.es traceroute to google.es (2a00:1450:4003:80f::2003), 30 hops max, 80 byte packets 1 2a02:9140:... (2a02:9140:...) 6.273 ms 6.283 ms 6.286 ms 2 * * * 3 2a02:9002:400::6 (2a02:9002:400::6) 14.124 ms * 15.058 ms 4 2001:1498:1:75f::1 (2001:1498:1:75f::1) 19.412 ms 19.499 ms 19.581 ms 5 2001:4860:1:1::2036 (2001:4860:1:1::2036) 16.155 ms 2001:1498:1:81d::1 (2001:1498:1:81d::1) 21.405 ms 2001:4860:1:1::2036 (2001:4860:1:1::2036) 17.295 ms 6 2001:4860:0:1347::1 (2001:4860:0:1347::1) 17.193 ms 13.308 ms 2001:4860::12:0:ba2d (2001:4860::12:0:ba2d) 15.083 ms 7 * 2001:4860:0:1::5319 (2001:4860:0:1::5319) 12.052 ms 2001:4860:0:1::56e2 (2001:4860:0:1::56e2) 12.306 ms 8 mad41s14-in-x03.1e100.net (2a00:1450:4003:80f::2003) 13.654 ms 14.236 ms 14.952 ms Telcontar:~ # ip -6 neigh fe80::ceed:dcff:fe05:80d4 dev eth0 lladdr cc:ed:dc:05:80:d4 router STALE 2a02:9140:...:ceed:dcff:fe05:80d4 dev eth0 FAILED Telcontar:~ # Ok, so the router address is 2a02:9140:...:ceed:dcff:fe05:80d4. I found the correct address yesterday, with my convoluted method. That's today's address, the ISP "promised" to use dynamic prefixes. I run this from the server, 24*7: while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; \ fping -c 100 --quiet 2a02:...ceed:dcff:fe05:80d4 ; \ done Result: 2023-04-18T11:37:23+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/75/25%, min/avg/max = 0.45/0.58/0.92 2023-04-18T11:39:04+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/77/23%, min/avg/max = 0.39/0.69/5.99 2023-04-18T11:40:45+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/79/21%, min/avg/max = 0.42/0.92/13.9 2023-04-18T11:42:26+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/90/10%, min/avg/max = 0.45/0.80/18.8 2023-04-18T11:44:07+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/82/18%, min/avg/max = 0.43/0.66/7.53 2023-04-18T11:45:48+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/81/19%, min/avg/max = 0.43/0.59/1.39 2023-04-18T11:47:29+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/85/15%, min/avg/max = 0.43/0.88/13.5 2023-04-18T11:49:10+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/77/23%, min/avg/max = 0.42/0.75/4.31 2023-04-18T11:50:51+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/79/21%, min/avg/max = 0.43/0.58/1.15 2023-04-18T11:52:33+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/82/18%, min/avg/max = 0.42/0.97/7.59 2023-04-18T11:54:14+02:00 2a02:...80d4 : xmt/rcv/%loss = 100/78/22%, min/avg/max = 0.40/1.44/16.6 Notice the losses. Same as with IPv4.
Otherwise
ip -6 neigh | grep mac-addr-of-router
Ok... Now how do I find the mac of the router... Oh, yes, I see it. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)