In reply to a post by candlerb:

If you can get into the router's web admin page and see what IP address it has for its WAN interface, that's the safest one to go for.

If both of them show the same latency, they're probably both on the router (e.g. WAN and LAN addresses).

However, xxxx:: and xxxx::1 *might* be the Sky side of the link and your router respectively. There are lots of different ways this might be configured and I've not see a NowTV connection in action.

Yeah this needs checking. I don't know the Sky setup/

seb

In reply to a post by candlerb:

If you can get into the router's web admin page and see what IP address it has for its WAN interface, that's the safest one to go for.

If both of them show the same latency, they're probably both on the router (e.g. WAN and LAN addresses).

However, xxxx:: and xxxx::1 *might* be the Sky side of the link and your router respectively. There are lots of different ways this might be configured and I've not see a NowTV connection in action.

I was only talking about the Sky/NowTV router as they don't provide a full IPv6 address for the router other than the ::1 as a loopback address which I made reference too.

In reply to a post by dect:

Because you have a Sky/Now TV router you can make that respond rather than your PC, you can tweak the IP address like below, just replace 'xxx' with what you have. The 'xxx' may represent 3 or 4 characters between the colons as leading zeros are not required.

2a02:xxx:xxx:xxx::1

Thanks, but sorry not sure what you mean by what I have. I have my IP from here https://www.thinkbroadband.com/tools/what-is-my-ip
which is
2a02:x:x:x:x:x:x:85a5
Do I just add ::1 on the end ?

Edited by seb (Thu 18-May-23 14:26:52)

Yes laptop is on wireless. I have logged in to the router & have been through all the menus. The only sections that appear to have relevant info I have taken screen shots of & are here:
[links removed]

Can I use any of these addresses so as to monitor the router & not my laptop ?

Thanks for all the help

Edited by seb (Thu 18-May-23 14:28:12)

Everything up to 2800 then add ::1 immediately after it

Please delete your post ASAP as its really not good posting your IP address.

In reply to a post by dect:

]I was only talking about the Sky/NowTV router as they don't provide a full IPv6 address for the router other than the ::1 as a loopback address which I made reference too.

They may well not provide a numbered WAN address, but at very least the router must have a LAN-side IPv6 address.

If you go to any of the client devices, and ask it what its default gateway on IPv6 is, that may give you an address on the router you can use. I think it's something like "route print -6" under Windows.

They could be announcing a link-local gateway address though (fe80::xxxxx) in which case that's no good.

If xxxx::1 works though, then that's great. It will be easy for OP to test: they can switch off their client devices and still see results on the BQM.

I removed the full IP from your post as it's generally advisable not to disclose those publicly.

Hi,

I've removed those links as they have your IPv6 address on them.
The IPv6 Loopback on one and the IPv6 Global on the other is the same - that should be the IP address of your router.
That is the number that ends in "::1"

I can ping that and it's quite stable..
That's the IP you should put into BQM.

The other thing I would say is your posting IP (i.e. on the forums) has changed at least once so it's likely your router is assigning a different v6 address from time to time for where you're posting from (or you're using different devices). This is why monitoring the computer isn't helpful.

There's what your router ping looks like:

64 bytes from 2a02:x:x:x::1: icmp_seq=114 ttl=58 time=11.2 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=115 ttl=58 time=10.4 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=116 ttl=58 time=10.7 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=117 ttl=58 time=10.8 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=118 ttl=58 time=10.9 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=119 ttl=58 time=10.8 ms
64 bytes from 2a02:x:x:x::1: icmp_seq=120 ttl=58 time=10.5 ms

compare that to your computer on latest IP:

64 bytes from 2a02:x:x:x:x:x:x:x: icmp_seq=1 ttl=57 time=39.8 ms
64 bytes from 2a02:x:x:x:x:x:x:x: icmp_seq=2 ttl=57 time=49.7 ms
64 bytes from 2a02:x:x:x:x:x:x:x: icmp_seq=3 ttl=57 time=71.7 ms
64 bytes from 2a02:x:x:x:x:x:x:x: icmp_seq=4 ttl=57 time=92.7 ms

That is almost certainly wi-fi causing that.

seb

Edited by seb (Thu 18-May-23 20:27:15)

Whoops sorry about that, live & learn I suppose.

Thanks for all the help here & for correcting my mistakes. I've set up a new monitor with ::1 at the end & it seems to be working. If it's ok ill post the graph here in a few days as I'm still a bit unsure as to how to fully interpret it.
Thanks

In reply to a post by mckenzie126:

Whoops sorry about that, live & learn I suppose.

Thanks for all the help here & for correcting my mistakes. I've set up a new monitor with ::1 at the end & it seems to be working. If it's ok ill post the graph here in a few days as I'm still a bit unsure as to how to fully interpret it.
Thanks

Do let us know. You should get an idea after a few hours. The graph shows only 24 hours anyway.. so post it in the morning