NAT loopback on UPC connect box stopped working

div · 2022-09-20T09:10:53+00:00

Sunrise Community - Kunden helfen anderen Kunden rund um die Themen Fernsehen, Internet, Telefon und Mobile. Jetzt registrieren!

div

Until recently, I had NAT loopback working on my UPC connect box (severs inside the local network were reachable from inside the local network via the public (external) IP + port forwarding on the UPC connect box). After what looked like a firmware upgrade on the UPC connect box on 06.09.2022, NAT loopback stopped working.

-- Should I hope that this feature would be fixed in one of the future upgrades? (If not, I will probably have to invest in my own router).

-- How frequent are firmware upgrades of the connect box? When should we expect the next one?

Daniele_Sunrise

div I was not aware that NAT loopback works on the Connect modems. I can’t tell you if NAT loopback will be fixed, because we never had it enabled. I can’t tell you how many times a firmware upgrade will be pushed out to our modems.

But you could make an entry in the host file on a Windows computer, then the NAT loopback works again.

Greetings
Daniele

div

Daniele_Sunrise – thanks for your quick reply, even though it is not reassuring.

My server and port-forwarding setup is a bit complex, and an entry in the host file would unfortunately not be sufficient for my needs.

I think the best solution for me would be then to buy a proper router and to use the connect box only as a modem.

I still hope that, since I am not the only customer complaining about the absence of NAT loopback (there are a couple of other forum topics on this in the English and German segments), you (or somebody in the support) could pass this message to the tech team who will try to revive NAT loopback eventually.

Markus951

Daniele_Sunrise

That’s no solution. I e.g. want access from a mobile or laptop, where I would have to modify the hosts file whenever I enter/leave the network.

I had arguments about this with the Sunrise Customer Service, but I gave up when they told me they don’t think they’ll ever fix that.
At that time, they even advertised DynDNS support, which was a blatant lie!

My solution was to set up my own DHCP & DNS server, but thats also an ugly hack. Only works for simple scenarios like a webserver, but not for port forwarding rules, etc.

div

Without any motivation from the UPC side to fix the NAT loopback issue, I gave up on using Connect Box as a router, switched it over to the modem mode and bought my own router/WiFi box. Now everything works alright.

udeheraie

Same problem. I have a webserver in my local network on which I’ve hosted a website. I could reach the website via the domain inside my local network but since 2 months that doesn’t work anymore, same for SSH, FTP, etc.

Daniele_Sunrise

Markus951 Welcome to the community!

Depending on the modem you use, you can set it to bridge mode, so you can install your own router afterwards. Does this solution not fit for you?

Greetings
Daniele

Markus951

Daniele_Sunrise
Sure I could buy and add another device, power adapter, cables, etc. and then power yet another device 24/7. That’s not sustainable.

I could also install a gasoline tank and a generator in the trunk of a Tesla to achieve the advertised range in winter.

But that’s not the point. The manual says:
"3.3.4 DynDNS
Objective: Enables a web surfer to access your Sunrise Internet Box (with no fixed IP address but
only a DNS entry) through a dynamic DNS provider such as, for example, dyndns.org."

The Sunrise Internet box currently does not provide that service for “web surfers” inside the network.

Please either fix NAT loopback or mention the defect in the manual.

alptz

The same thing happened on our connect box in February 2023. NAT loopback suddenly stopped working. To access the heating control, we now have to turn off the WLAN on the cell phone.

UPC and now sunrise no longer convince me in many respects and a change is becoming more and more likely.