Anything About Billion For UK Users
https://www.forum.billion.uk.com/
This is official firmware, I don't think there have been any fixes relating to your issues though, as our engineers need to debug the issues you encountered within your environment, as you have reverted back to d27, we can't debug them.Strider wrote: ↑Thu Jan 28, 2021 11:51 am Is this officialy released or still beta? As I'm wondering if the d4x series still has the issues I had encountered.
https://www.forum.billion.uk.com/viewto ... =50#p44581
Everything looks fine to me,viccycat wrote: ↑Sat Feb 13, 2021 8:29 am Hi! Yesterday, I upgraded firmware to Zcomax8900AX2400_2.52.d46.afw, reseted settings back to factory default & reconfigured device. Provider use IPoE connection & I want to know the optimal configuration of wireless 2.4G/5G on this router to have maximum perfomance using it. I attached my settings screen shots. Can you help me? By the way, I have only a few settings in advanced 5G options, is it normal?
That's all I was able to track down. https://github.com/spagu/billion
I've been testing this firmware the past week. Factory reset. No imported settings.billion_fan wrote: ↑Thu Jan 28, 2021 12:14 pmThis is official firmware, I don't think there have been any fixes relating to your issues though, as our engineers need to debug the issues you encountered within your environment, as you have reverted back to d27, we can't debug them.Strider wrote: ↑Thu Jan 28, 2021 11:51 am Is this officialy released or still beta? As I'm wondering if the d4x series still has the issues I had encountered.
https://www.forum.billion.uk.com/viewto ... =50#p44581
Submit a ticket on the following link https://support.billion.uk.com/index.ph ... ets/SubmitStrider wrote: ↑Thu Mar 18, 2021 1:57 pmI've been testing this firmware the past week. Factory reset. No imported settings.billion_fan wrote: ↑Thu Jan 28, 2021 12:14 pmThis is official firmware, I don't think there have been any fixes relating to your issues though, as our engineers need to debug the issues you encountered within your environment, as you have reverted back to d27, we can't debug them.Strider wrote: ↑Thu Jan 28, 2021 11:51 am Is this officialy released or still beta? As I'm wondering if the d4x series still has the issues I had encountered.
https://www.forum.billion.uk.com/viewto ... =50#p44581
.46 Some issues I'm still encountering that does not happen on .27.
https://www.forum.billion.uk.com/viewto ... =50#p44581
The logging into the router is one of them. You'll log in, then it says session expire even after logging out requiring to login multiple times. That's pretty messed up. Never had that on d27. I can be sitting in the router for 2 - 4 minutes, click another area in the UI and session timeout.
The connection uptime keeps resetting when I login to the router even though the connection has never dropped. Sometimes it says only uptime of 3 - 9 minutes. Then the number can magically jumps by 20+ minutes while being logged in for 5 minutes.
The 3rd being something is going on when I'm viewing twitch. The chat in any channel stops getting activity. There is no pattern to it. It can be working for 10 - 20 minutes then stop working then responds again within 2 - 5 minutes. As if the router is blocking something. Then all of a sudden there is a massive response of packets causing the chat to spam a lot of new responses on catchup. Also never happened on d27.
I still sometimes see sporadic lag pauses in games, not as often as .46 but still happens which is pretty annoying.
I'm also seeing loss of IPv6. No connection even though it was working fine days ago. Same settings used as d27 which was working flawless.
So, how do I debug this? As I said, I never encountered these issues on d27. Hence why I went back to d27 but now I'm currently on d46.
The only thing I'm seeing in the logs is:
Mar 18 12:13:45 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:17:23 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:24:14 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:29:28 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:39:03 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:42:59 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:49:50 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 12:57:49 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 13:07:14 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 13:16:54 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 13:26:19 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 13:28:50 daemon info syslog: MDM lock is held by ssk (pid=415) for 6 seconds
Mar 18 13:32:38 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx
Mar 18 13:42:34 daemon warn radvd[24622]: received RA from fe80::6203:xxxx:xxxx:xxxx