BQM 100% packet loss

I recently changed my router that meant a change of my public IP address. I am using a dynamic dns service to locate my router. It now shows 100% packet loss where as before i changed my router it was working fine. I can ping my dynamic dns name fine. I also set up a monitor to the ip adreess that the dynamic dns name resolves to and this works fine. It is the BQM does not seem to be resolving to the new IP address. I have tried deleting the BQM monitor and then re-creating it but this also does not work.
Is there anything else to try?

Do you need to allow your router to respond to pings from the BQM IP?

I tried the trace route tool on ThinkBroadband and this seems to work fine

In reply to a post by pjr66:

Is there anything else to try?

Have you tried other places to ping the IP your router shows? You may be one of the new ISPs that uses CGNAT which would stop this working.

In reply to a post by pjr66:

I recently changed my router that meant a change of my public IP address. I am using a dynamic dns service to locate my router. It now shows 100% packet loss where as before i changed my router it was working fine. I can ping my dynamic dns name fine. I also set up a monitor to the ip adreess that the dynamic dns name resolves to and this works fine. It is the BQM does not seem to be resolving to the new IP address. I have tried deleting the BQM monitor and then re-creating it but this also does not work.
Is there anything else to try?

I can't find the BQM or your main site account to look at this.
I'd need to really find the details to look at this further.

seb

I have a public IP address that I can access via a ping OK

Just for everyone else's benefit as I'm so confident I know the answer now having seen the hostname - it includes an fe80:: IPv6 address we can't ping so dual stack issue

Hi Seb

Thanks for looking into this, I logged into my dynamic dns provider and have deleted the IPv6 address. Not sure where that come from as I am with cukoo (TalkTalk) which I thought did not have IPv6. Will see tomorrow if that fixes it.