On 2023-04-18 16:23, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-04-18 12:22, Per Jessen wrote:
Carlos E. R. wrote:
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.
Ah, I forgot, you wanted the external address, sorry.
No, the internal.
I meant external as opposed to link-local. There is no more internal/external, your machines all have public ipv6 addresses.
Yes, so I read somewhere else today. I assumed the router would have one address on the external, fibre, interface and another on the internal, eth, interface.
The external I can ask some web pages, and maybe the router itself.
Yep, got it - you want the LAN side address of the router.
Yes.
That's today's address, the ISP "promised" to use dynamic prefixes.
Which isn't the same as a guaranteed change, I expect.
Every time the rooter reboots, same as with IPv4.
Really? That is not how most providers do it.
Welcome to Spain. (I suspect Andrei is familiar with this setup, though) It may be even worse, though: on a reboot, I might loose IPv6. I would have to email the Beta Testing Group, and they would activate it again. I read something about that, so I'm not going to try a router reboot unless absolutely needed. I know read Andre's next email. I can not set up logging on this router. It worked on the previous incumbent, on this one the interface is missing. And, since this afternoon I can no longer ssh to my router: cer@Telcontar:~> ssh 1234@router.valinor kex_exchange_identification: read: Connection reset by peer Connection reset by 192.168.1.1 port 22 cer@Telcontar:~> The cron job that does an ssh on the router is failing. I fear the ISP has manually closed it, or the daemon (inside the router) has crashed.
Notice the losses. Same as with IPv4.
Try increasing the interval, the default is 10ms.
Why? :-?
To avoid having packets dropped. ICMPs may be dropped, they have the lowest priority. If you are flood pinging your network - which I suggest 100 pings per second is - some will be dropped.
The test takes a minute to run. I tried 25 mS, no difference. Any command that does ping tests fails the test. The same test, if run directly, without a switch, works perfectly. The old router worked fine. They replaced the router, and I lost ALL connectivity switch-router. They replaced the router, and I have this, 30% loss. When I try any web site, there is a delay, compared to the old router. Many packages fail, but being TCP it tries again. Ok, I'll put "--interval=100", count 20. I'll let it run for a while and report again. (1) Oh, the switch is fine. router----SW1-----SW2---computer_room | laptop laptop to computer room runs perfectly the same test. The Telefónica technician gave up. (1)
Isengard:~ # while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; fping -c 20 --quiet --interval=100 router ; done 2023-04-18T20:43:28+02:00 router : xmt/rcv/%loss = 20/14/30%, min/avg/max = 0.28/0.43/0.88 2023-04-18T20:43:50+02:00 router : xmt/rcv/%loss = 20/19/5%, min/avg/max = 0.31/0.37/0.52 2023-04-18T20:44:11+02:00 router : xmt/rcv/%loss = 20/20/0%, min/avg/max = 0.30/1.56/7.81 2023-04-18T20:44:31+02:00 router : xmt/rcv/%loss = 20/16/20%, min/avg/max = 0.30/0.98/4.89 2023-04-18T20:44:52+02:00 router : xmt/rcv/%loss = 20/17/15%, min/avg/max = 0.31/1.11/7.49 2023-04-18T20:45:13+02:00 router : xmt/rcv/%loss = 20/18/10%, min/avg/max = 0.28/0.35/0.58 2023-04-18T20:45:34+02:00 router : xmt/rcv/%loss = 20/15/25%, min/avg/max = 0.31/0.39/0.68 2023-04-18T20:45:55+02:00 router : xmt/rcv/%loss = 20/14/30%, min/avg/max = 0.32/0.39/0.66 2023-04-18T20:46:16+02:00 router : xmt/rcv/%loss = 20/20/0%, min/avg/max = 0.31/0.34/0.45 2023-04-18T20:46:36+02:00 router : xmt/rcv/%loss = 20/15/25%, min/avg/max = 0.30/0.40/0.73 2023-04-18T20:46:58+02:00 router : xmt/rcv/%loss = 20/18/10%, min/avg/max = 0.30/0.35/0.49 2023-04-18T20:47:19+02:00 router : xmt/rcv/%loss = 20/12/40%, min/avg/max = 0.32/1.22/10.1
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)