topic Re: Invalid IP address - port forwarding / DMZ in Broadband

Invalid IP address - port forwarding / DMZ

LeicesterLoser — Mon, 11 Dec 2023 12:43:18 GMT

I have a FAST5364 router, running SG4K100174.

I'm trying to set up port forwarding but always get an "invalid IP address" error.

My Router lives at 192.168.10.1; the only thing connected to it is a Unifi USG. I've seen some suggestion that forwarding doesn't work unless this router is at its default IP address?

I've also tried putting the USG in the DMZ - that also results in an invalid IP address error. If I navigate to the USG in the "connected devices" page in the router GUI and try to put it in the DMZ from there, I get a different error - "Operation could not complete, something wrong happened"

Is there different firmware available for this router to fix this?

Re: Invalid IP address - port forwarding / DMZ

Anonymous — Mon, 11 Dec 2023 12:52:51 GMT

Hello,

@KeithFrench - would you be able to offer some advice please?

Thanks

Michelle

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Mon, 11 Dec 2023 12:52:54 GMT

That will depend on the hardware revision of the 5364, is it V3 or V4? You can try a factory default of the router's configuration.

Re: Invalid IP address - port forwarding / DMZ

LeicesterLoser — Mon, 11 Dec 2023 12:56:53 GMT

Hi Keith,

The plate on the back says "5364-3 T8" - I assume V3 from that?

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Mon, 11 Dec 2023 12:56:53 GMT

Hi @Anonymous

Our posts crossed in the ether!

Re: Invalid IP address - port forwarding / DMZ

Anonymous — Mon, 11 Dec 2023 12:59:10 GMT

Thanks @KeithFrench 🙂

Michelle

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Mon, 11 Dec 2023 13:00:01 GMT

Possibly, @LeicesterLoser the best way is to log into the router & check Device Info.

Re: Invalid IP address - port forwarding / DMZ

LeicesterLoser — Mon, 11 Dec 2023 13:14:10 GMT

@KeithFrench There's no explicit mention of version numbers in there.

FAST5364 3.00

SG4K100174

5.100.1

I assume that 3.00 means V3?

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Mon, 11 Dec 2023 13:18:48 GMT

Yes, that is V3, which is the one that has the problems, you can try a factory default of the router, but it is probably not going to change anything. This is a known bug that is in hand with the developers. It is now a case of waiting for the next firmware release, to see if the fix is in there.

I am not party as to when this will be.

Re: Invalid IP address - port forwarding / DMZ

LeicesterLoser — Mon, 11 Dec 2023 13:22:12 GMT

Thanks for the confirmation @KeithFrench

@AnonymousIs it possible to get a replacement router that doesn't have this known issue? Waiting for a firmware release that may or may not ever appear isn't a very satisfactory solution.

Re: Invalid IP address - port forwarding / DMZ

Anonymous — Mon, 11 Dec 2023 13:29:29 GMT

Hi,

Apologies, we only have the one version of the wifi hub that we can send, we don't have another make and model of router. This has been raised and we're hoping a new version of firmware will be available in the new year.

Thanks

Michelle

Re: Invalid IP address - port forwarding / DMZ

LeicesterLoser — Mon, 11 Dec 2023 13:28:26 GMT

That's rather disappointing. This is functionality I now need for work; I may have to look elsewhere. Good thing I'm now out of contract!

Re: Invalid IP address - port forwarding / DMZ

Anonymous — Mon, 11 Dec 2023 13:32:02 GMT

Hello,

I understand and I'm really sorry to hear this. I'll ask the Devices Manager now if they have a set date for the new firmware.

Thanks

Michelle

Re: Invalid IP address - port forwarding / DMZ

EdHodson — Fri, 26 Jan 2024 17:53:48 GMT

Hi folks,

Not sure if this was issue resolved, but I had the same problem recently and I discovered a workaround. I thought I would post it here in case it helps someone else in future.

I also found that the UI always reported "Invalid IP Address" when trying to add a port forwarding rule (/2.0/gui/#/access-control/port-forwarding/add-rule).

The issue appears to occur when you have the DHCP server (/2.0/gui/#/mybox/DHCP) disabled on the Sagemcom 5364 router. I disabled it because I find the DHCP daemon to be unreliable on the router and so I run my DHCP server on another device instead.

When the router DHCP server is disabled, the router UI also reports "-" as the local subnet mask under /2.0/gui/#/mybox/deviceInfo/deviceInfo, rather than the expected 255.255.255.0 (or whatever you have configured). This is obviously impossible, but when it is reporting this, you won't be able to add the port forwarding rule.

Sagemcom 5364 Bug

The workaround is to enable the DHCP server temporarily, then add your forwarding rule, then disable it again (if you want to). You will find that when you enable the DHCP server, the subnet mask is reported correctly in the deviceinfo section too.

Cheers,

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Fri, 26 Jan 2024 21:57:44 GMT

Hi @EdHodson

This is a bug with firmware V174 and before only affecting V3 hardware. Perhaps you are on V4 hardware? Anyway, it should be fixed in the next release of firmware.

Re: Invalid IP address - port forwarding / DMZ

EdHodson — Wed, 31 Jan 2024 19:17:39 GMT

Hi Keith,

I'm on V3 hardware. I'm just passing on the workaround that worked for me, since it seems to be a long-standing bug and an issue for other users.

Cheers, Ed

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Thu, 01 Feb 2024 09:22:45 GMT

Thanks for that @EdHodson the vast majority of people with this issue are using the router's internal DHCP server. I am hoping that it is finally fixed in the next firmware due sometime soon. However, as mine is V4 hardware, I never saw the issue & could never tell if it was fixed or not.

Re: Invalid IP address - port forwarding / DMZ

EdHodson — Thu, 01 Feb 2024 10:04:46 GMT

Hi Keith,

Might be worth asking other users affected by this bug to disable the DHCP server on the router, save config, re-enable DHCP server, save config, and then try the rule again. It seems to be a bug in the way the router UI config stores or queries the local LAN subnet mask.

Under the hood, the actual router must of course have it stored correctly in order to operate as a router, but as described and screenshotted, something about the DHCP server config leaves the UI code thinking it has a blank subnet mask and hence when it checks the LAN address to be forwarded to in the forwarding rule, it fails as it appears like the target address is not on the same subnet.

BTW, I just received a new router from TT and I am a bit disappointed it is another v3!

Cheers,

Re: Invalid IP address - port forwarding / DMZ

KeithFrench — Thu, 01 Feb 2024 10:49:46 GMT

Hi @EdHodson

Thanks for this, the next person I see with this problem I will certainly ask them to try your workaround. However, I have dealt with so many customers since the last one of these, I have no idea who had the problem previously. Hopefully, as I said, it will be rectified in the next firmware release.

Re: Invalid IP address - port forwarding / DMZ

ben616937 — Mon, 19 Feb 2024 23:00:38 GMT

Is there an update on this issue please? Is the only reliable solution to get a new router with V4 hardware?