Hi – my central office peplink is sitting on a very fast, very reliable, publicly routable network. I initially setup the device with only a WAN1 interface – the intention is that the WAN1 ip of this box be the speedfusion remote ip used by each of our remote sites. This actually worked however the speedfusion initialization never completed – the process would hang forever with ‘Updating routes’ displayed in the status menu of each peplink. I theorized that the speedfusion process must learn about the networks connected to each peer via that peer’s LAN interface – so I configured the LAN interface on the central node with another address on the same network as the WAN1 interface. This seems to work I think – but I**’**m not entirely sure if its the ‘right thing’? Will this cause problems? Is there a better way?
Additionally we externally advertise the central node as owning the ‘route’ to the networks on the remote sites. Which ip addresses should own the route in this case – that of the LAN interface or that of the WAN1 interface? I’m advertising the LAN’s ip addresses as having a route to the remote sites and it seems to be working – however I’m not entirely sure if I’m running afoul of the way the firewall configuration works (the intention to have a firewall on the central node to allow or certain kinds of access to the remote site through the speedfusion)… Thanks for any advice.