Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3 
sigod

38 posts

Geek
+1 received by user: 5


  #3393981 14-Jul-2025 22:26
Send private message

I know i used to have fibre for 4 years in a different city. I found another possible issue in the router logs:

 

14.07.2025 22:08:07 [Steering] (Mac address of my device) RadioId:0, Rssi:-42, targetBand:0, steerReason:2

 

The log is full of these messages. I think the firmware is causing steering logging even when I turned off band steering and only use 2.4ghz and this is causing DHCP instability.

 

This person had a similar issue:

 

https://www.geekzone.co.nz/forums.asp?forumid=39&topicid=315188

 

 




michaelmurfy
meow
13616 posts

Uber Geek
+1 received by user: 10982

Moderator
ID Verified
Trusted
Lifetime subscriber

  #3393988 14-Jul-2025 22:37
Send private message

I don't think it is related to this at all - this log is related to WiFi.

 

Confirm the problem happens over Ethernet because this thread is now going on a bit of a tangent between blaming Spark, and blaming the router when in reality it's sounding more and more like your WiFi device.

 

But as others mentioned multiple times, it really sounds like you should be looking into UFB if upload speeds and stability are this much of a concern for you. I would only ever use FWA / Starlink etc as a secondary backup connection if UFB exists at your premises.





Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.


sigod

38 posts

Geek
+1 received by user: 5


  #3393990 14-Jul-2025 22:44
Send private message

It's doing it on multiple wifi devices it's not just one... I GET IT I UNDERSTAND FIBRE IS THE ANSWER to my new 4g router problems. I don't want to hear that again. I'm trying to get to the heart of the problem with THIS NEW ROUTER for the sake of interest in the technical reasons why. I will eventually just go back to my old router or get fibre.




Asteros
363 posts

Ultimate Geek
+1 received by user: 189


  #3393994 14-Jul-2025 23:19
Send private message

Your router sounds faulty. Could you return it and get a replacement one?


sigod

38 posts

Geek
+1 received by user: 5


  #3393995 14-Jul-2025 23:27
Send private message

Asteros:

 

Your router sounds faulty. Could you return it and get a replacement one?

 

 

Yes that is the obvious course of action assuming the other Futura modems don't do the same thing. It'll go back to Spark in any case.


acsmaster
1 post

Wannabe Geek


  #3398905 31-Jul-2025 20:41
Send private message

sigod:

 

I think i've figured out what is happening and it's not on my side.

 

 

 

[ Your Router ]
    |
    | (Event A: The Router's Daily Timer)
    |   - Configured to check in once every 24 hours.
    |
    V
[ The ISP's ACS System ]
    |
    | (1. The Flawed Handshake)
    |    - Router tries to contact the server at 12:00 PM NZST.
    |    - The specific server it tries to connect to is in a scheduled maintenance window.
    |    - (BUG #1: Lack of Load Balancer/DNS Fallback) The connection fails, logging the "Inform Fail" error.
    |
    V
[ Your Router's Ongoing State ]
    |
    | (Event B: The Random Request)
    |   - At a random time later in the day, the server-initiated connection request arrives.
    |
    V
[ A Server in the Farm ]
    |
    | (2. Successful Connection)
    |    - Your router successfully connects to an active server.
    |
    V
[ The Flawed Provisioning Script ]
    |
    | (3. The Two-Part Bug)
    |    - The script runs on the server.
    |    - It contains two separate errors:
    |
    +-----> (BUG #2: Mis-provisioning)
    |            - The script sets the router's upload speed to 1/4 of what it should be.
    |
    +-----> (BUG #3: Forced Disconnect)
                 - The script forces a network session reset.
                 - This is why you get disconnected.

 

 

 

And this:

 

 

 

+-------------------------------------------------+
|                                                 |
|          [ Your Router's Schedule ]             |
|          --------------------------             |
|          - Daily Inform (Scheduled)             |
|          - Connection Request (Random)          |
|                                                 |
+--------------------------|----------------------+
                           |
                           V
+--------------------------|----------------------------------------------------+
|                                                                                |
|                 [ THE ISP'S SERVER FARM ]                                      |
|                 -------------------------                                      |
|                                                                                |
|            (The 12 PM "Inform Fail" Bug)                                       |
|            - Your router's daily check-in tries to connect.                    |
|            - BUG #1: The server is temporarily unresponsive.                   |
|            - Result: Connection Fails.                                         |
|                                                                                |
|            (The Random "Connection Request" Bug)                               |
|            - The server sends a command to your router.                        |
|                                                                                |
|        +------>  [ Path A: The Good Server ] <-----------------------------+   |
|        |           - Has the correct provisioning scripts.                   |   |
|        |           - BUT...                                                  |   |
|        |           - (BUG #2: The Disconnect) A systemic script runs         |   |
|        |             that forces your connection to drop.                    |   |
|        |           - Result: Internet disconnects.                           |   |
|        +------>    [ Path B: The Bad Server ] <-----------------------------+   |
|        |           - Has the incorrect provisioning scripts.                 |   |
|        |           - AND...                                                  |   |
|        |           - (BUG #2: The Disconnect) A systemic script runs         |   |
|        |             that forces your connection to drop.                    |   |
|        |           - (BUG #3: The Bad Speed) A separate script runs          |   |
|        |             that sets your upload speed incorrectly.                |   |
|        |           - Result: Internet disconnects AND speed is low.          |   |
|        +----------------------------------------------------------------------+

 

 

 

I could be wrong just trying to figure it out.

 

 

Hi Sigod,

 

I can give you a more accurate steer on the process above.

 

Router Scheduled informs
- "Daily" are either 24 hours or 5 minutes if waiting for a provisioning update. These are known as Periodic Informs, they can be set to any value but these are the ones used for the Futura
- "Random", aren't really random. They're when Spark need your device to come in to receive instructions or return data immediately, you could receive many of these over a short period if a customer agent is actively working on an issue with your modem. Your router doesn't receive these daily, only as and when a specific need arises - you may never see one on a device that doesn't need to be interactively managed.

 

One thing you missed is an IP Address change, and that's the real killer on 4G connections. Every time the Router flips to a new IP address that triggers a connection to tell the backend the IP address has changed. If you have a sub-optimal 4G connection or your cell is overloaded this can happen frequently, of course the 4G IP flipping is probably what’s killing your upload as well, you probably don't see a connection drop but because the source IP changes on the Router it can cause lots of weird stuff to happen.

 

ISP Servers
- Firstly, there is no maintenance window. The servers receive traffic 24/7.
- The "schedule" for 24 hour Inform isn't midnight. It's 24 hours from the last time it occurred, if your router was rebooted at 14:25, then the next 24 hour inform with be at 14:25. If it informed a change of IP address at 15:15, it's next Period Inform will be at 15:15 the next day. What you've probably seen is some upstream network maintenance like a cell tower reconfig/restart, these would have reset the IP address triggered an inform and for some reason network engineers love to group all this stuff together on the hour at midnight/1am/2am/3am/4am.

 

So the Inform Fail "bug", it's not really a bug is a design feature of the protocol standard. If the Router doesn't get a respond from the server it enters a lengthening back-off retry cycle until is succeeds.

 

and on to the final part - the provisioning script
This part is just wrong I'm afraid.
There isn't anything that is sent that causes a connection drop except in the case of a firmware upgrade being loaded to your Router, however IIRC the whole router itself would reboot rather than just a connection drop. Bug #2 just doesn't exist.
The connection speed thing is also not handled by this system, if your speed is being changed it's somewhere in the Core Network. Again I'd suspect this is going to be a 4G cell issue and/or a bug in the router firmware that trying to be helpful, detecting a flaky 4G signal and reducing the upload speed itself in an attempt to make the connection stable (and slow) rather than fast and unstable.

 

Hope that helps,

 

A


 
 
 
 

Shop now on Samsung phones, tablets, TVs and more (affiliate link).
sigod

38 posts

Geek
+1 received by user: 5


  #3398941 31-Jul-2025 23:59
Send private message

I went back to my old router and I've had zero problems since. It was the new router that was the problem not the network. I knew about the daily IP address change, it doesn't cause connections to be lost on my old router even though the new router was losing connections at random. That diagram was AI generated.

 

If you never see those connections unless it's managed why was the Futura seeing them daily then? The 4g connection is solid, the tower is literally down the road and doesn't drop out on my old router or any of my cellphones. I'm pretty sure the Futura's firmware is bugged.

 

I don't care about this problem anymore I'm not getting another Futura modem. 


1 | 2 | 3 
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.