Dynamic DNS Giga Hub 2 NOIP stopped working

[I-Vlad]

Hi All,

Anyone experience the same issue with NOIP? Tested with CURL and all worked ok giving nocng response. Submitting from the setting giving an error "Cannot be saved. Try again later.

My modem was recently reset, could that cause that issue?

Thanks

[SeanC]

Yip. Something to do with the CGNAT that's rolling out? Maybe. 

Regardless, something that has worked for more than a decade has stopped and that's a frustrating user experience without any messaging from Bell. Not all port forwarding broke, but 443 has and Plex no longer works as it should.

Here's hoping it gets addressed.

[Gimli1780]

Since I've migrate to Bell Giga Hub 1 to Giga Hub 2, my IoT objects are not working anymore. 

When I say not working... it's not working and I've tried : 

1. Separate the 3 Wifi Bands
2. Reboot the router
3. Using 5 different Matters Hubs and like 15/20 devices
4. Remove the Bell Guard on Bell Wifi apps 
5. Put on the privacy mode on Bell Wifi apps

It's just a waste of time, does anybody have the same issue ? 

Thanks, 

[I-Vlad]

Just wondering if port blocking in our residential terms of service. 

[SeanC]

Yeah, I just don't know. But the GH has port forwarding, add a note or prevent it from working? Offering a tool to port forward that can't or won't is senseless. Russian Roulette port forwarding is frustrating.

[Vanadiel]

Bell terms of services for residential services can be found here. 

[Vanadiel]

Without knowing brand details it's difficult to provide specific information on setup of the devices.

First thing to check is how the connection is made. I am assuming WiFi, and if that is the case are regular WiFI connections working properly?

[SeanC]

AI tells me (TLDR) Generally speaking their TOS does not explicitly ban the act of running a server for personal use (my use case). Commercial use is a no go.

[Gimli1780]

Hi, 

I try differents IoT hubs, like Apple TV 4k, Apple HomePod, Ikea Dirigera, Google Home even my Samsung TV. Every time it's a fail with lot of IoT items (different brands, Ikea, no name...) 

Previsously with Giga Hub 1, I have no difficulty at all, pairing taking like 20s and works perfectly after. Now, it's just no working... 

I assume I'm not the only person to use Matters IoT objects with a Bell Hub 2.0

[Vanadiel]

What is the error messages you are getting on the setup application that comes with any of those hubs when trying to set it up?

[jasonlamb]

@BellPatricia I submitted an email today about this and got a call back from a Bell Technician saying firmware updates are on Sagecom's end. When I asked about a potential timeline I was told "oh, who knows" and that Bell isn't notified of when firmware is being deployed.

Is there an actual investigation into a fix, or is this just something that we all need to wait to possibly be fixed by Sagecom at some nebulous point in the future?

[SabSnake]

I basically gave up, I replaced the Modem once already, exact same issue happened. It's on Bells end or whoever does the firmware, whenever it updates, even if it wasn't an actual firmware update ( since it seems the same version numbers ), it just breaks. I bought my own Router and hooked it up to the Bell Modem that basically broke, and now I can do what I want. Works. Had Bell techs mess with their modem before I got the router and nothing worked, they recommended me to pay for their business line or go buy a router and use that as the main device.

[Gimli1780]

Pairing failed, or please connect your phone to the wifi network. 

Of course, my phone are on the same wifi network, and I’ve try on the 2,4Ghz band only. Same result. 

[Lundon44]

I recently posted on Reddit how Bell's Giga Hub 2.0 suddenly broke the local connection to my Plex Media Server. And how upon contacting Bell live chat about it, not only were they unfamiliar with Plex but suggested that Bell moving to CGNAT was the cause of my problem and purchasing a 3rd party router and placing it in bridge mode could help. But not without some other possible issues arising as well.

Fast forward a few weeks and tons of hours wasted into troubleshooting the problem, I followed the direction of another user that swapped out their router for a new one and suddenly everything just "worked" again.

I swapped out my Giga Hub 2.0 last Friday for a new one and to my surprise, it worked immediately after getting it reconnected. My local server was now available again and no issues remotely either. Basically how things had been working for years until recently.

Now today, I had heard of another user who also swapped routers out had the issue come back again. So I decided to check myself and to my disappointment, the issue was back again. After several days of no issues I am no longer able to connect to my local server again. No changes have been made, router was rebooted as well.. Nothing.

I don't know if Bell pushed a firmware update to my Giga Hub 2.0 since swapping my router. I currently sit on firmware 3.11.6.1. I wish I checked it when I brought it home. But clearly something Bell has done has prevented users again from connecting to our home servers. Maybe it's specifically affecting port forwarding I'm not sure because . I'm also not a networking wizard so I can't waste more hours troubleshooting the issue further. 

I also just spoke to a Bell internet tech rep and my suspicions were confirmed. My Plex server connection last worked on May 3rd. A firmware update was pushed by on May 4th according to their system. They are unable to revert the update nor block the update from occurring on devices with older firmware. I have opened a ticket, however the rep did have difficulty understanding the issue so I'm not sure how much faith I have in this getting resolved.

#Plex #GigaHub #portforwarding

[Lundon44]

Update: I tried to escalate to a level 3 technician, however while on hold to speak to one the rep came back and said they would not take the call as Plex is "unsupported". The rep suggested I try to downgrade to the Giga Hub 1.0 as they cannot update the firmware automatically, only manually. I guess this is my only option now. So now I have requested to downgrade my Hub to the 1.0.

Also found this other post on Reddit to confirm my suspicions that port forwarding is broken

[Vanadiel]

If it worked and then stopped working with a new modem, that would confirm a firmware issue as firmware updates are pushed to all devices over time, to ensure they are all using the same firmware.

It could also be some kind of firmware "feature", but only Bell could comment on that.