Port forwarding stopped working

zhuser · 2022-09-16T11:42:06+00:00

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

zhuser

I have been using port forwarding on my connect box for all the years that I had it (more than 5) but I noticed today that it stopped working. Directly connecting to the port through the internal network (192.168.0.XX : PORT) works. I’ve tried removing / re-adding the port forwarding rule but it didn’t make a difference. My connect box is already in IPv4 mode.

Daniele_Sunrise

zhuser We have reactivated your firewall on the modem. Also, the ports are still active as forwarding.

192.168.0.XX 23… 23… 23… BOTH Enabled
192.168.0.XX 8… 8… 8… TCP Disabled
192.168.0.XX 4… 4… 4… TCP Disabled
192.168.0.XX 23… 23… 23… 23… BOTH Enabled

Can you please test it again? Perhaps you need to restart your modem and the affected devices.

Error we get from your Device:
ERR_INVALID_HTTP_RESPONSE and ERR_CONNECTION_REFUSED

Greetings
Daniele

zhuser

Hi Daniele

Thank you for your reply and for looking into this.

I have just restarted the modem but it still doesn’t work:
Local network:

192.168.0.XX:23XXX on the browser
on the 192.168.0.XX device
# nc -l 23XXX

GET / HTTP/1.1

Host: 192.168.0.XX:23XXX

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Upgrade-Insecure-Requests: 1

Cookie: Squeezebox-enableHiDPI=2; Squeezebox-expandPlayerControl=true; Squeezebox-expanded-FAVORITES=0; Squeezebox-expanded-MY_MUSIC=0; Squeezebox-expanded-PLUGINS=0; Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=0; Squeezebox-expanded-RADIO=0; Squeezebox-player=b8%3A27%3Aeb%3A9d%3Abb%3A1d

User-Agent: Mozilla/5.0 …..

Accept-Language: en-GB,en;q=0.9

Accept-Encoding: gzip, deflate

Connection: keep-alive

From the public IP address
77.58.242.XXX:23XXX on the browser
On the device the port was supposed to be forwarded:
# nc -l 23XXX

[nothing]

I’ll try on another device as well.

Daniele_Sunrise

zhuser I read on the Internet that Squeezebox can also allow and forbid IPs: https://forums.slimdevices.com/showthread.php?102076-blocking-IP-addresses-fails

Here I have also found another info. I assume that your Squeezebox blocks the IPs, because I get a connection refused from an external Swisscom line.

Greetings
Daniele

zhuser

I’ve tried forward a different port, on a different device in the local network (192.168.0.1XX) and it also doesn’t work, so it’s probably not the devices but the modem.

div

@zhuser – if this problem appears when you connect from inside your local network, then it is probably an issue with the so-called “NAT loopback” (port forwarding works for outside connections, but fails from inside). I have the same issue since 06.09.2022 after what looked like an automatic firmware upgrade. To me, it looks like they have done an upgrade that broke NAT loopback (which was working before).

If you manage to get some help on this from their support, I would be very grateful.

So far there are two other forum topics related to that:

-- https://community.sunrise.ch/d/22909-upc-connect-box-two-problems (another user reported a modem-config change on the same day)

-- https://community.sunrise.ch/d/22904-port-forwarding-kaputt (more specific about port forwarding; there, the support guy responded that “they don’t have and don’t support NAT forwarding”, which obviously contradicts the fact that it worked for me for many years).

Not sure if this helps, but you are not alone 🙂

Peter-R

div

@div

The exact same problem here. The firmware was updated (discovered this on 10. Feb). I know the firmware was upgraded, because the connect box login URL changed.

zhuser

@div Thank you for information, it’s really helpful. It looks like we have a very similar problem, but for me the port forwarding does not work for outside connections (public_ip:port does not forward to local_ip:port). The firmware update being the culprit sounds like a very possible explanation.

I see three options (@Daniele_Sunrise please comment if 1 is possible, otherwise if there’s a timeline for 2) :
1. we can ask for a firmware rollback
2. we wait for a firmware upgrade that fixes this problem
3. we set connect box to modem mode and use a separate router to do the forwarding

div

zhuser – then your problem seems to be different from mine: for me, the port forwarding continues working alright for outside connections (e.g., it works if I am connecting via an external VPN)

zhuser

@div One more thing: port forwarding has worked for me also for many years (almost 10 years now, first on a Thomson modem, and then with the connect box – for what is worth I’ve never had issues with the Thomson modem, I wish I could have kept it).

zhuser

Daniele_Sunrise I’m not exposing the port of the squeezebox through the port forwarding, at all. I only use it in the local network. The port forwarding is for a different service.

Also, this exact setup has been working for me for 10 years now (including port forwarding and squeezebox exposed in the local network only), so I don’t see how this could be.

In any case, I have checked the squeezebox logs and no “Did not accept HTTP connection from” are reported. I also stopped the squeezebox server and it made no difference to the port forwarding.

Daniele_Sunrise

zhuser May I reset your modem once? If it doesn’t work then, I’ll be happy to replace your modem.

Greetings
Daniele

Peter-R

Daniele_Sunrise

Same problem here after latest firmware rollout. Looks like you haver a NEW FIRMWARE BUG.

zhuser

@Daniele_Sunrise Please go ahead and reset it, thanks.

Daniele_Sunrise

zhuser We have reset your modem. Can you please forward the ports again and test it?

Greetings
Daniele

zhuser

@Daniele_Sunrise resetting didn’t change the problem but I think I’ve found what’s going on: I was testing the port forwarding from within my local network (accessing it through the public_address:port). I just tested it from a remote endpoint outside my local network and it worked. This is OK for me, since I can access the port directly on the local IP when within the local network. But this was working before, and it seems to be the same NAT loopback issue that @div mentioned.

Oaker

Yes I can confirm this as well. Quite annoying to be honest. I have a roaming notebook that connects to my NAS from my home LAN as well as from outside networks via DDNS. This severely impacts my ability to work at the moment.

stmilosh

I can confirm it too. A buggy firmware was pushed 3 days ago on February 10th and since then it stopped working.
Very annoying!

Daniele_Sunrise

stmilosh Basically the NAT loopback doesn’t work, which means that an external URL that points to the internal network doesn’t work. That it worked with some modems (cable modems) is also not understandable for me.

Greetings
Daniele

stmilosh

Daniele_Sunrise So if I understood correctly NAT loopback was not a feature that was present on some ConnectBoxes for years, but essentially a bug, so these recent firmware patches are attempts to fix that “bug” and therefore remove NAT loopback functionality???

What I really fail to understand is why is NAT loopback a security issue that Sunrise needs to so eagerly patch instead of leaving it as configurable modem option?

Is there at least a possibility to enable it from your side?

Daniele_Sunrise

stmilosh We have no way to enable this as it was done via firmware. We recommend either to make an entry in the host file in Windows, or to bridge the modem, if possible, so that you can use your own router.

Greetings
Daniele

Nächste Seite »