Router Firmware

[robcuk1]

Hi.

I've been having problems every few weeks with my Broadband connection with the only fix being power cycle the router. No-one from your support organization can tell me why .

Can you please update the firmware on my router please. DG8041W - currently v1.06t 

Thanks

Robin

[Debbie-TalkTalk]

Thanks for your help @KeithFrench 🙂

[robcuk1]

Fantastic explanation. Thank you. Now fully understand and cleared up the confusion that's out there. A lot of people are using the term "Bridge" mode in the context of the setup of their WiFi Mesh network when they really mean "Modem" mode. So much so, that multiple articles mention "Bridge" mode and as you say they don't really mean that as otherwise there would be no Layer 3 routing to the Internet. 

The guided DECO setup put itself on 192.168.68.x (255.255.255.0) hence why it's working and yes "Double NAT" but I have no port forwarding requirements at the moment.  

[KeithFrench · Accepted solution]

Hi @robcuk1 

First off the differences between modem & bridge mode in general. If you have the TT router connected to the broadband & put it in modem mode, it would act as a modem (assuming FTTC/VDSL or ADSL) and pass on the public IP address to your mesh. This is what you needed.

You mention being advised to put the TT router in bridge mode, this is where there is a lot of confusion & whoever told you this is wrong. Let me explain, but it will be quite technical. When a router is configured in bridge mode, a bridge is essentially a layer 2 device. This removes all routing capabilities, turning it into an Access Point (AP). If you now connect this to the broadband line, it will be impossible to route any IP packets from the private IP address range (e.g. 192.168.1.2 - 192.168.1.254/255) to the public IP address provided by the TalkTalk network. So this solves all problems, as it results in no internet access at all!

Now to specifics. No current TalkTalk router and most older ones do not support modem or bridge mode. However, for your intended scenario I do have a simple workaround. You setup a TalkTalk router such as one of the Wi-Fi hubs that you had to their default configuration, but you change the router's IP address to be on a different subnet to that used by your mesh. For instance, if the mesh used 192.168.1.1/255, and you put the TT router's address to be 192.168.2.1/255, you would be fine. The third Byte or Octet of the address (in bold) needs to be different, to keep them on separate networks. There is a disadvantage though in so much as you have created what is called a "Double NAT" environment. This is only a problem if you ever want to do port forwarding, but even then I can talk you through doing this on the TT router, so long as your mesh supported it.

[Debbie-TalkTalk]

Hi robcuk1

"I'll send the old router back tomorrow and will continue to monitor stability of the connection"   

Thank you 🙂

[robcuk1]

Sorry, bridge mode. Best practice I'm led to believe when setting up my own MESH Network (TP-Link Deco) is to change the router to "Bridge" mode. They say this can help to avoid some problems, assume they mean things like avoiding "Double NAT"

Anyhow. I've setup the Mesh network without any change other than disabling the TalkTalk router WiFi. Appears to working just fine.

I have been using Huawei and have just swapped and now using the Sagemcom.

Thanks 

[Debbie-TalkTalk]

Thanks @KeithFrench 🙂

[robcuk1]

The TP-Link DECO seems to be working with the new router just fine without any change to the mode. I would be interested to know whether it is possible or not to configure this router in Bridge/Modem mode.

I'll send the old router back tomorrow and will continue to monitor stability of the connection

Thanks 

[KeithFrench]

Hi @robcuk1 

Which do you want, modem or bridge mode, as they are totally different? In what scenario do you want to implement it?

Which router are you using now, the Huawei or the Sagemcom?

[Debbie-TalkTalk]

Hi robcuk1

Sorry for the delay.

@KeithFrench are you able to help with this please?

[robcuk1]

Hi Debbie, How do I put the new router into Bridge/Modem mode in order to setup with my TP-Link Deco Mesh network devices?

[robcuk1]

Hi Debbie. I have router here. How do I put the Router into Bridge or Modem mode in order to use my TP-Link Deco MESH network?

[Debbie-TalkTalk]

Hi robcuk1

Have you received the replacement router?

[Debbie-TalkTalk]

Hi robcuk1

Thanks for your reply.

The router is on its way, please allow 48hrs for this to arrive.

Let us know how the connection compares with this router.

Thanks again.

Debbie

[robcuk1]

Yes please. I'll try anything to see if it improves the service. Thanks

[robcuk1]

Yes please. I'm happy to try that and see if it improves matters

[Debbie-TalkTalk]

Hi robcuk1

Would you like me to send a Sagemcom WIFI hub?

[ferguson]

The router firmware is the latest available and is known to be stable. Have you looked to your mesh setup for any issues there?

[ferguson]

The router firmware is the latest available and is known to be stable. Have you looked to your mesh setup for any issues there?

[robcuk1]

and....  if we reference my previous issue a few years back, the failed authentication was occuring then but v1.06t firmware stopped the panic occurring

https://community.talktalk.co.uk/t5/Broadband/Having-to-reboot-Router-daily-at-the-moment/td-p/25906...

Could it be that instead of an automatic panic reboot now by the router OS, the router is now struggling / hanging when something (unknown as yet)occurs., e.g v1.06t hasn't totally fixed the root cause perhaps???

Is the router hitting some kind of limit (files/storage/memory) but the code (v1.06t) stops it from automatically rebooting, it's just now I am having to reboot the device myself to resolve the connectivity.

Something is not right here..... and I need some assistance to diagnose the problem. More detailed monitoring, escalate to the software code developers if necessary? 

Is this configuration correct? TBC for the userid??????  I assume all of this has been checked??? 

[robcuk1]

This seems to occur when I have problems. Can it help to explain what's happening. Occurred before the issue back in the 12th too?

2023-01-26 15:23:22 [Critical][Config-Log] Terminal:ACS(78.150.63.238),Result:Fail,Type:Authorization,:

[robcuk1]

I didn't get a chance to check that before it came back online. My TP-Link mesh network reported a loss in Internet connection (you get a red flashing light on those boxes) and my PC had it's webcast drop. By the time I got upstairs with my laptop to plug into the box, check light etc, the connection had re-established itself.