topic Re: Has the port forwaring bug been fixed in Fibre

Has the port forwaring bug been fixed

harrybarman — Sat, 11 Feb 2023 15:18:06 GMT

Hi. I have a FAST5364 3.00 with firmware SG4K100136. I'm running with a non standard ip 192.168.0.1. I can't create port forwarding rules. I'm getting an error 'Operation could not complete, something wrong happened' I really don't want to change the network ip as I've got bit of a complex setup.

Has this been fixed in a newer firmware revision?

Harry

Re: Has the port forwaring bug been fixed

ferguson — Sat, 11 Feb 2023 16:07:44 GMT

I am not aware of a bug with this firmware? We are fortunate to have an expert on port forwarding here, @KeithFrench are you able to help, please?

Re: Has the port forwaring bug been fixed

KeithFrench — Sat, 11 Feb 2023 17:49:44 GMT

I have tried port forwarding and it works on all private IP address ranges. It is impossible for me to test every single address though. This is of course a subnet zero address.

All of that said, there was a bug that only seemed to affect hardware V3 and different pf problems. I have never been able to replicate these bugs as I have V4 firmware.

Would you like to try V158?

Re: Has the port forwaring bug been fixed

Anonymous — Mon, 13 Feb 2023 06:40:20 GMT

Hello,

Would you like us to update the router firmware for you? When would be the best time as this can take up to 20 minutes to complete and the router cannot be rebooted or switched off during this time?

Thanks

Re: Has the port forwaring bug been fixed

harrybarman — Mon, 13 Feb 2023 08:34:47 GMT

Hi - new firmware would be great! Can you schedule it for any time after 6.30pm this evening?

Cheers,

Harry

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 08:39:50 GMT

It's not possible for us to schedule this and we would need to push this during our working hours. The update usually takes about 5 minutes to complete.

Karl.

Re: Has the port forwaring bug been fixed

harrybarman — Mon, 13 Feb 2023 08:50:14 GMT

Ah - no worries. Please go ahead.

Harry

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 08:59:06 GMT

Firmware pushing now, will post back when completed.

Karl.

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 09:02:26 GMT

All done, firmware now showing as V158.

Karl.

Re: Has the port forwaring bug been fixed

harrybarman — Mon, 13 Feb 2023 14:21:40 GMT

Many thanks Karl!

I'm still getting the error "Operation could not complete, something wrong happened." when trying to add a manual port forwarding rule. (example attached)

We can leave this for now as I'm running a upnp client on my vpn box that is adding the forwarding rule I need.

Cheers,

Harry

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 14:27:49 GMT

OK, maybe @KeithFrench can cast his eye over the example above and see if he sees anything amiss,

Karl.

Re: Has the port forwaring bug been fixed

KeithFrench — Mon, 13 Feb 2023 15:06:30 GMT

Hi @harrybarman

I have just tried that & it worked the first time, not just adding it within the UI, but also able to send test UDP packets to it OK. However, I am using the standard IP address range.

@Karl-TalkTalk I did send this across a while back saying that despite trying IP addresses in all three private subnet ranges, I have never been able to reproduce this. The difference is, all of these affected customers seem to be on hardware revision V3 & I am on V4.

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 15:11:20 GMT

Hi @KeithFrench

I've asked Farrukh to have a read through this thread and see if he can get PQA Teams to test.

Karl.

Re: Has the port forwaring bug been fixed

KeithFrench — Mon, 13 Feb 2023 15:13:58 GMT

Hi @Karl-TalkTalk

I have just updated the spreadsheet & emailed it to you.

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Mon, 13 Feb 2023 15:19:02 GMT

COOL 🙂

Re: Has the port forwaring bug been fixed

KeithFrench — Tue, 14 Feb 2023 11:21:58 GMT

Hi @harrybarman @Karl-TalkTalk

Whilst not quite the same, I have just tried this on a Hub 2, which is running hardware version 2.00 and firmware V158. I set it to have an IP address of 192.168.0.1 and it all worked the first time on there as well.

Re: Has the port forwaring bug been fixed

Karl-TalkTalk — Tue, 14 Feb 2023 13:01:23 GMT

Hi @harrybarman

Would you like to try a replacement router to see if this works ?

Karl.

Re: Has the port forwaring bug been fixed

harrybarman — Fri, 17 Feb 2023 17:45:25 GMT

Thanks for the offer Karl. If you'd like me to test with more recent hardware then I'm happy to, but no need otherwise. I've solved the immediate problem so I'm ok for now.

Cheers,

Harry

Re: Has the port forwaring bug been fixed

Anonymous — Mon, 20 Feb 2023 06:39:25 GMT

Morning,

Ok thanks for confirming and I'm glad to hear that this is now working ok 🙂

Thanks