Daniele_Sunrise
Good morning Daniele, and thank you for kindly replying to this thread.
We have no way to enable this as it was done via firmware.
This is factually false. One can roll out another firmware without the bug. When a problem is introduced into a computer system. One can resolve that problem in a number of ways.
- For example here, by rolling back the firmware to the state prior to the problem occurrence.
- Or by fixing the firmware and rolling that fix out, on top to fix the problem.
An alternative is to suggest the problem is per se not repairable. This is incorrect. The problem is fixable. Where there is a will, there is a way.
ON/OFF
I can’t personally think of any circumstances where I would not want NAT LOOPBACK functioning. So the ability to turn this feature on or off makes no sense to me. And if the feature were to have a bug - as is the case here - the Bug on/ Bug off button wouldn’t work anyway.
The NAT LOOPBACK is obviously a feature of the modem else it this algorithm would never have worked. The fact that it worked for the last 10 years proves it is a feature and that it is a new bug introduced recently.
To err is human. Or as the Americans say. Sh*t happens.
PROBLEM RESOLUTION
To summarise
- Somebody made a change to the firmware, introducing the bug.
- Somebody failed to find the bug during testing.
- Somebody rolled the bug out into the UPC community.
- People are experiencing difficulties.
I understand the frustration you may feel in your support role. You can’t resolve the issue personally. May I suggest tracing the above chain of events in reverse order, in order to resolve the issue at hand?
Please report the issue as an issue to the manufacturer or team responsible at UPC for the firmware rollout.
ALTERNATIVES / WORK AROUND
I’d also like to thank you for your kind and useful suggestion regarding the Windows host file. Adding an entry there will allow the user’s PC to resolve to the internal IP address.
Since many customers use mobile devices, there are Android and Apple devices where there is no Windows host file to manually correct. What can these users do?
The connect box can operate in both router and modem modes. I’m considering your other great suggestion and placing my own router behind the connect box.
Do you know if the firewall functionally is completely lost whn I re-configure the connect box to drop the router functionality and operate in modem mode?
Thanks and have a great day!
BTW
Does anybody know who makes the hardware?
The manufacturer probably knows nothing about this problem. Perhaps an Email to the manufacturer can assist in resolving this issue for the next firmware rollout.
I’d be willing to run and provide any assistant diagnostics I can to help resolve the issue.
