BQ16 Latest Firmware & Consistent disconnections from the internet after a week or 2?

[Reinforcer]

I'm having a similar issue now on the latest firmware - the internet will drop, but the router connected to my ISP shows no issues on the LED and when I try to login through the mobile app or the website I'm unable to authenticate. A power cycle resolves the issue temporarily, but it has happened twice in the past 24 hours now (no rhyme or reason).

I'm going to do a factory resetand set everything up again. Ugh.

I get the exact the same thing, The router reports no issue with the connection but I lose all internet lol, What's the point of the notices in the app or router when they don't even work as intended.

I'll wait for a decent WiFi 7 router from TP Link, Never had any stupid issues like this with their routers in the past.

 

[skypx]

That’s so weird. I wonder what the issue is. I’m using the pro without any issues since day 1, and that’s without resetting it to factory defaults (didn’t realize the reset button on the bottom just deletes the configuration) as recommended.

 

[jzchen]

Has anyone noticed consistent disconnections after like a week or 2 with the BQ16 latest firmware 3.0.0.6.102_37026?

It's not my fibre provider as when it happens I have to reboot the router and the internet is back, It is consistently doing it since I put this latest firmware on although I did subscribe to a fixed IP address from my FTTH provider around a month or so ago also so I am not sure what is going on, I can tell it's not my provider also because of the 2 green lights on the fibre box are always still on so 100% it is the router that keeps losing the internet connection.

This is what is reported in the log when it loses connection every single time.

Dec 7 17:20:09 wan: finish adding multi routes
Dec 7 17:20:09 wan_up: Restart DDNS
Dec 7 17:20:09 dhcp client: renew 6*.***.55.84/255.255.252.0 via 6*.***.52.1 for 600 seconds.

I have noticed the 1st IP is not the same as the 2nd one, The last 2 sections of the digits are different but my fixed IP is always the same if that makes sense?

So did the issues start after upgrading to a Static/"fixed" IP with the ISP?

1. There shouldn't be any need for DHCP Query if you pay for a Static IP.
2. DDNS is not needed as well. It's job is to track WAN IP changes to the DDNS address chosen or randomly assigned.

I don't think your ISP informed you correctly that Automatic or DHCP assignment to your router is correct. The lease time should be infinite...

 

[jzchen]

6*.***.55.84/255.255.252.0 via 6*.***.52.1

6*.***.55.84 is your IP address
255.255.252.0 is the subnet/subnet mask
6*.***.52.1 is your gateway/default gateway

 

[Reinforcer]

That’s so weird. I wonder what the issue is. I’m using the pro without any issues since day 1, and that’s without resetting it to factory defaults (didn’t realize the reset button on the bottom just deletes the configuration) as recommended.

I don't know, You'd have thought the configuration was very similar between the non pro and the pro.

Yes that button acts as a factory reset or you can do via the gui also.

 

[Reinforcer]

So did the issues start after upgrading to a Static/"fixed" IP with the ISP?

1. There shouldn't be any need for DHCP Query if you pay for a Static IP.
2. DDNS is not needed as well. It's job is to track WAN IP changes to the DDNS address chosen or randomly assigned.

I don't think your ISP informed you correctly that Automatic or DHCP assignment to your router is correct. The lease time should be infinite...

It was around the same time I think from memory, I may have been on the Fixed ip for a few weeks already and then the new firmware came out and that's when it started losing complete internet access within a few days to a week, Was only on the new firmware a few weeks and it did it around 4 times and the only thing that fixed temporarily was to reboot the router.

Well that's what I thought also but they said no need to change anything in the router when in fairness it does make sense to a degree because the DHCP query is just for detecting IP changes so if it hasn't changed as mine hasn't changed because I am fixed it should leave it as it was and lose any connection so I don't know.

 

[Reinforcer]

6*.***.55.84/255.255.252.0 via 6*.***.52.1

6*.***.55.84 is your IP address
255.255.252.0 is the subnet/subnet mask
6*.***.52.1 is your gateway/default gateway

Yes that's correct after more research I understood that in that end.

 

[avinin1]

That’s so weird. I wonder what the issue is. I’m using the pro without any issues since day 1, and that’s without resetting it to factory defaults (didn’t realize the reset button on the bottom just deletes the configuration) as recommended.

I've heard many more complaints about the 'regular' version than the Pro version. I don't know what it is, but it seems more problematic. A simple search here will show exactly that. @Richard1864 @msilva

 

[jzchen]

Yes that's correct after more research I understood that in that end.

Those numbers are what you enter in the Static IP settings (in WAN). I hope that resolves what you are experiencing....

 

[Reinforcer]

Those numbers are what you enter in the Static IP settings (in WAN). I hope that resolves what you are experiencing....

Thank you, I will try that when I get the chance to do so once my little boy is not here so I can fiddle with it, Appreciate that thanks.

 

[Futuristic]

I'm also having the same type of issue, but with the RT-BE82U (3.0.0.6.102_39099). It's happening roughly every 3-5 days and sometimes sooner. It appears to be DNS related. It basically loses connection with the DNS server section and makes it seem like you're suddenly offline. If you're on a call with someone on Discord or some other connection that doesn't really require DNS, you never really loose connection and that's basically how I figured out it was DNS related. I'm using the Adguard Adblock DNS servers under the WAN section and if I go in there and simply switch to another DNS provider and save... the connection comes back. And if I immediately switch back to the Adguard DNS servers everything is fine again.

I'm wondering if this is also what is happening on your router?

 

[Reinforcer]

I'm also having the same type of issue, but with the RT-BE82U (3.0.0.6.102_39099). It's happening roughly every 3-5 days and sometimes sooner. It appears to be DNS related. It basically loses connection with the DNS server section and makes it seem like you're suddenly offline. If you're on a call with someone on Discord or some other connection that doesn't really require DNS, you never really loose connection and that's basically how I figured out it was DNS related. I'm using the Adguard Adblock DNS servers under the WAN section and if I go in there and simply switch to another DNS provider and save... the connection comes back. And if I immediately switch back to the Adguard DNS servers everything is fine again.

I'm wondering if this is also what is happening on your router?

Possibly a similar issue, I am not sure if my issue is DNS or Wan port/IP related as reported when it in the log when it went down last time I was on the latest firmware.

However I am not using a custom DNS so I don't think that's the issue in my case.

 

[Futuristic]

Possibly a similar issue, I am not sure if my issue is DNS or Wan port/IP related as reported when it in the log when it went down last time I was on the latest firmware.

However I am not using a custom DNS so I don't think that's the issue in my case.

Yeah, it could definitely be DNS related cause I'm seeing a lot of other people that appear to be having the same issue across several different models. It must be something within the core of the newer model's firmware. I went back to using my AX58U temporarily until there's some kind of firmware update that hopefully addresses this. So far I haven't had any issues with the AX58U. (knock on wood)

 

[Reinforcer]

Yeah, it could definitely be DNS related cause I'm seeing a lot of other people that appear to be having the same issue across several different models. It must be something within the core of the newer model's firmware. I went back to using my AX58U temporarily until there's some kind of firmware update that hopefully addresses this. So far I haven't had any issues with the AX58U. (knock on wood)

Quite possibly, I haven't tried the latest firmware again since but as I am seeing others with a similar issue I think I will wait for a new firmware before testing again.

Hopefully they will release one soon.

 

[Reinforcer]

So I have just been trying to set my static IP and it won't let me because it wants me to setup and DNS address also lol.

So I can't even test the static IP settings in the router as it won't allow you to select the default DNS from your ISP when using a static IP.