In reply to a post by ianfretwell:

I can do a factory reset - but don't the numbers above seem highly suspect ?

The problem is you may be right but Zzoomm are not going to budge on their position and you know it works with their provided router so that only leaves you with trying everything you can with your kit. If you don't want to try it then best wait and see if people in the same position as you come forward and start complaining but it may be a UK region specific problem.

Edited by PCJM40 (Fri 04-Jul-25 11:15:32)

Thanks - and you're right.

This post was to see if anybody else could confirm similar - so I'm happy to wait a little longer. I've also emailed Draytek with the details to see if they will suggest anything - so far nothing from them though.

The Zzoomm support desk 'kind of' said that they'd had other Draytek users reporting similar issues but wouldn't expand upon that and wouldn't give any details of what the 'change' they'd made was.

I only have the two routers available to me at the moment - and anything else I could beg or borrow would ironically be more Icotera's from Zzoomm or Draytek's from work...

There is one very vocal Zzoomm customer (in Hereford) on here with their own TP-Link router and if they were having an issue like you I strongly suspect they would be posting about it.

Lol!

OK, so I've just checked the syslog entries created since putting the Draytek back online at 10:32.


The 5 repeating lines referring to "WAN2 DHCP -->" are now back and occurring at 1000 second intervals again - so maybe they've found something or maybe rolled back the change. Fingers crossed.

Next expected drop would have been at 16:05 - I'll see how it goes...

In reply to a post by PCJM40:

There is one very vocal Zzoomm customer (in Hereford) on here with their own TP-Link router and if they were having an issue like you I strongly suspect they would be posting about it.

No problem here and have not been any problem for nearly 2 years, the TP link is fine. Just do a reboot now and again to clear the router memory,

Zzoomm prefers people to use their router, I suppose it is easier to sort out problems. if you use your own, then you are on your own, so to speak.

In reply to a post by zyborg47:

Zzoomm prefers people to use their router, I suppose it is easier to sort out problems. if you use your own, then you are on your own, so to speak.

Unless you use a specialist ISP such as AAISP then all the providers will only support their own router. These companies are not the size of Apple, or HP where they would buy EVERY printer available in a country and test with them all to train helpdesk.

These ISPs have limited margins, so to control helpdesk costs they have no choice but to only support use of their router.

Having trained helpdesks I can see exactly why they do this.

In reply to a post by zyborg47:

No problem here

Thanks Adrian for confirming

In reply to a post by ianfretwell:

Hi,

Had Zzoomm for 13 months - used with Draytek 2866ax router (never used their Icotera). Never had a single issue, until...

they apparently did some work on the 29th/30th and now the Draytek will only stay connected to the WAN for either 20,000 or 30,000 seconds (very round numbers don't you think...)

After that time I have to force the line to drop by doing any of:-
1 - Reboot router
2 - Reboot ONT
3 - Remove cable betweeen router and ONT for approx 10seconds
4 - Perform Release / Renew in Draytek console

I have a ticket open with them but they are just going all-in on the 'use our (totally incapable) router'.

I'm looking for anybody else with the same issue so that we can compare notes, etc.

Thanks

As suggested, replace the problematic Draytek router with another, if at all possible, to confirm of the issue travels with the router. Or not.

I suspect the issue is within the Draytek router rather than service, given no wider complaints have been observed.

Thanks for all the comments.

So - as stated previously - everything appears to have gone back to normal with regards the syslog entries - and so far no drop.

As far as I'm concerned - they've rolled back the change or implemented a fix, but no actual contact from them so I'll just see how it goes over the weekend.