Updating Routes

in Peplink Balance 380 the SpeedFustion Established , but in anther side (Peplink Balance 580) not Established and give me Updating Routes…any help?

Hi,

  1. May I know end to end communication is ok (from PC to PC)?

  2. What is the firmware version for both B380 and B580?

Azhari:

For personal experience, when this happens its because in the updating routes peplink you have a Wan subnet that conflicts with the subnets of the other Peplink.

Try disconnecting that Wan and you’ll see…

I think that this is solved in new fw 6.2.2 but you’ll have a routing problem, because, let say you’ll try to get to 192.168.1.15 that is on the central lan and it can be too at the wan subnet in the branch site because that wan is 192.168.1.254/24 and peplink is 192.168.1.64/24 ( and 192.168.1.15/24 can be in both sides).

The solution, go to outbound policies, turn on advanced routing and add a enforced rule that say 192.168.1.0/24 priority or enforced by pepvpn.

It’s not an “elegant” solution, but it works.

AG

Another reason for this occurring is that the FusionHub doesn’t have a LAN IP address assigned via DHCP so you need to manually configure one then this issue goes away.