Probably a long shot this - but...

I've had Zzoomm as ISP for just over a year - with 2866Lac and then 2866ax routers - I've never used the provided Icotera 'thing'. I pay for the 'static IP' option.

Currently my service is dropping every 5.5 hours. I can bring it back by :- rebooting the router   OR   rebooting the ONT   OR   simply disconnected the cable between the two for a few seconds.

Syslog shows that right up until 15:17 on the 30th June these 5 lines appeared every 16 or 17 minutes  (essentially the DHCP checking the address - 5th line being the confirmation from the Zzoomm DHCP I believe)   The IP is obviously not my actual...

<166>Jun    30    15:17:29    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"
<166>Jun    30    15:17:33    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"
<166>Jun    30    15:17:41    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"
<166>Jun    30    15:17:57    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"
<166>Jun    30    15:17:57    DrayTek:    "1449bc3b1110:WAN2 DHCP <==XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 111.222.333.444, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"


After this time, it seems to go haywire - they only appear as single lines and then and much greater intervals (I'm assuming because the Zzoomm DHCP isn't responding the same way - these are the next four "WAN2 DHCP" entries. I'm pretty sure the fourth was after the ONT was powered off/on hence the client IP being 0.0.0.0  (this seems to be the key as it is only when it's 0.0.0.0 that the Zzoom end assigns the static IP to me).


<166>Jun    30    15:48:05    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd5375f, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"

<166>Jun    30    21:29:36    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd52d6c, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"

<166>Jul    1     03:28:07    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd52aa8, Client IP = 111.222.333.444, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"

<166>Jul    1     08:35:13    DrayTek:    "1449bc3b1110:WAN2 DHCP ==>XID = 0x3cd51848, Client IP = 0.0.0.0, Your IP = 0.0.0.0, Next server IP = 0.0.0.0, Relay agent IP = 0.0.0.0, Option:"

I have raised a ticket with them that I'm still awaiting a response on but they are going a bit towards the 'blame Draytek' approach despite the 13 months of previous faultless service.   Can anybody better versed at syslog confirm what's happening above ?  Allegedly they have several Draytek users with similar/same issues - maybe one of you is on here?

Thanks

And now their customer support guy has just stated:

"I am aware that DrayTek recently pushed a firmware update. It’s something we’re factoring into our investigations, but we’re not in a position yet to confirm whether it’s directly related."

 

It seems that the static IP lease time from Zzoomm has possibly been changed from 1000 to 20000 seconds. Based on the things I'm seeing.

Might this be larger than the router can deal with ?
(I know the internal DHCP goes beyond that but might the WAN side be more restrictive)

A long shot, but I might try spoofing the MAC address of the device they supplied. As a temporary measure I might also try putting that in as a “buffer” between your Draytek and their ONT.

There was a recent merger of Zoom and FullFibre and there may be “plumbing” changes afoot.

Thanks Mark...I was actually going to try this as a last ditch attempt when the syslog entries returned to 'normal' and everything is remaining up once again...Hope it lasts!

I’ve seen the odd previous mention of DHCP issues with Zzoomm but nothing definitive for your issue. My guess is that Zzoomm tried different DCCP servers and have now backed the change out (or possibly found and fixed the issue). It’s worth a support ticket with Draytek as the interesting question is why Zzoomm’s supplied routers worked ok.