Cannot get SpeedFusion on MAX BR1 Pro 5G to connect to Fusion hub

Product Discussion
,
1

I had a test fusion hub in AWS that expired and SpeedFusion had worked to the MAX BR1 Pro 5G. Was built late December 2024 from AWS marketplace. I built a new FusionHub a few days ago from the AWS marketplace instance and added 5 peers OK.

Now the FusionHub and MAX BR1 Pro 5G are up and can be seen ok on IC2 but the SpeedFusion connection is stuck at “starting” - failed to establish connection (failed to connect remote peer)

In addition the FusionHub and MAX BR1 Pro 5G have a connection back to a fixed IP old B380 where the SpeedFusion connects ok – B380 not on IC2.

The firewall on the AWS instance is set all outbound and the usual inbound.

11
11922×352 85 KB

I used the WAN Performance Analysis test between the Fusionhub and the MAX BR1 Pro 5G and of course it failed until I added TCP 6000 and TCP 44912. WAN Performance Analysis worked ok with fusionhub as server and MAX BR1 Pro 5G as client to FusionHub IP.

Now the build setting for the two devices were as below.:
• MAX BR1 Pro 5G Firmware 8.5.1 build 5714, SpeedFusion VPN Version 9.2.2 ,with one cellular connected to EE 5G ok and all other wan disabled.
• FusionHub Firmware 8.5.1s045 build 5258, SpeedFusion VPN Version 9.2.2

To test matters I downgraded the FusionHub to 8.5.1 build 5246 and this made no difference.

I downgraded the MAX BR1 Pro 5G to 8.5.0 build 5636 and this made no difference.

The modem code on the BR1 Pro 5G was old so updated it as below and this made no difference.

• Was: RM520NGLAAR01A08M4G_01.200.01.200
• Now is latest: RM520NGLAAR01A08M4G_17.203.17.203

I updated the MAX BR1 Pro 5G back to code 8.5.1 build 5714 and this made no difference.

There I no IC2 option to put FusionHub back as was.

So I am not sure what’s next?

2

and… just checking…
you look at the:

  • SpeedFusion VPN Local ID
  • Remote ID / Pre-shared Key

What can you see at SpeedFusion VPN Event Log?

3

SpeedFusion ids set correct at both ends

I don’t normally use a pre-shared key but i tried that and it made no difference. The link to the B380 just uses the device id and the fixed ip without a pre-shared key

SpeedFusion log at MAX BR1 end

Feb 13 15:35:14 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 13 15:34:58 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 15:31:13 SpeedFusion: MANC-pepink-ID (B380) disconnected from MANC (handshake failed)
Feb 13 15:23:16 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 13 15:23:01 SpeedFusion: FUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 15:22:58 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 14:43:52 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 13 14:43:35 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite (NONE)
Feb 13 14:34:55 SpeedFusion: MANC-pepink-ID (B380) disconnected from MANC (link failure detected)
Feb 13 14:19:10 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 13:45:50 SpeedFusion: FUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 13:03:45 SpeedFusion: FUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 12:54:55 SpeedFusion: FUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 12:50:25 SpeedFusion: SFC-LON-019 (SFC-LON-019, sn:11B2-AE66-F2F4) disconnected from SFC-LON (link failure detected)
Feb 13 12:41:29 SpeedFusion: SFC-LON-019 (SFC-LON-019, sn:11B2-AE66-F2F4) connected to SFC-LON
Feb 13 12:41:25 SpeedFusion: SFC-LON: Initiated TLSv1.3 connection to 45.154.205.121 using cipher suite TLS_AES_256_GCM_SHA384
Feb 13 12:41:24 SpeedFusion: SFC-LON: Initiated TLSv1.3 connection to 45.154.205.121 using cipher suite TLS_AES_256_GCM_SHA384
Feb 13 12:36:46 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:36:45 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:36:42 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 12:34:54 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:34:53 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:34:51 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 13 12:34:49 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:34:15 SpeedFusion: MANC failed to establish connection
Feb 13 12:34:14 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 13 12:33:57 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 13 12:33:54 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 12 14:32:11 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 12 14:17:13 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 12 14:16:14 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 12 14:15:48 SpeedFusion: MANC failed to establish connection (failed to connect remote peer)
Feb 12 14:15:48 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 11 16:19:26 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 11 16:19:24 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 11 15:49:30 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 11 15:49:17 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 11 15:49:32 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 07 14:10:02 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 07 14:10:01 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Feb 07 13:57:07 SpeedFusion: MANC-pepink-ID (B380) connected to MANC
Feb 07 13:56:54 SpeedFusion: TWLFUSIONHUB1 failed to establish connection (failed to connect remote peer)
Feb 07 13:56:51 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Jan 15 16:02:45 SpeedFusion: TWLFUSIONHUB1: Initiated TLSv1.3 connection to FUSIONHUB-ip using cipher suite TLS_AES_256_GCM_SHA384
Jan 15 16:02:45 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Jan 15 16:02:44 SpeedFusion: MANC: Initiated TLSv1.2 connection to MANC-IP using cipher suite AES256-GCM-SHA384
Jan 15 16:02:44 SpeedFusion: TWLFUSIONHUB1: Initiated TLSv1.3 connection to FUSIONHUB-ip using cipher suite TLS_AES_256_GCM_SHA384
1 Like
4

Works?? I never try! Always type some words like passwordpassword

Updating…
TST-DUO-Q (8.5.1) and FusionHUB 8.5.1s045 build 5258, just ID… no password. Cool… I don’t know… Thank you.

5

ignore the lines below. I was just trying speed fusion connect to see what happened. This is off now.

Feb 13 12:50:25 SpeedFusion: SFC-LON-019 (SFC-LON-019, sn:11B2-AE66-F2F4) disconnected from SFC-LON (link failure detected)
Feb 13 12:41:29 SpeedFusion: SFC-LON-019 (SFC-LON-019, sn:11B2-AE66-F2F4) connected to SFC-LON
Feb 13 12:41:25 SpeedFusion: SFC-LON: Initiated TLSv1.3 connection to 45.154.205.121 using cipher suite TLS_AES_256_GCM_SHA384
Feb 13 12:41:24 SpeedFusion: SFC-LON: Initiated TLSv1.3 connection to 45.154.205.121 using cipher suite TLS_AES_256_GCM_SHA384

6

Something… happened here… was nine minutes up.

7

OK I put in a pre-shared key, rebooted both, and still same issue

I also put FusionHub back on 8.5.1s045 build 5258

8

thank you. As noted this was me trying the SpeedFusion connect into the hub where the AWS instance is as a test. These SpeedFusion connects setting were removed.

9

So…

All SF tunnels, still down! Correct?!

10

Hello. I have sorted this thank you.
I ran packet grabs from support.cgi and used Wireshark to take luck and silly me set tcp port on firewall to 32105 instead of 30125.
HCG

11

this will be my another question… about 32015_udp (default port)

Ha ha ha… at your screen… you don’t have a rule for 30125…
You just type wrong, at speedfusion settings? It is happen… everybody did this, sometimes.

12

If WAN Performance Analysis fails, check TCP 6000 & 44912—made all the difference for me