Hi Charris,
Before deployment
- Ensure either site has public IP.
- Ensure port Tcp32015 and Udp4500 are open.
- Please ensure WAN IPs for both units are reachable. You my go System > Ping to confirm this.
After SpeedFusion/PepVPN was configured
You will noticed stages below once you have configured SpeedFusion/PepVPN profile:
- Starting… - VPN engine knows about this profile, and either waiting for client to connect, or trying to connect to the remote peer.
- Authenticating… - You might not be able to see this state because it should normally be short-lived. However, if you are stuck at this state, that means you have some authentication error, check PSK/X.509/ Remote ID setting settings. TCP 32015 is used on this state.
- Creating Tunnel… - This is after authentication is successful. VPN tunnel is creating in this stage. If you are stuck at this state, that means no tunnels are connected (L3 speedfusion) or there is something wrong with bridging the VPN interface (for Layer 2 Speedfusion).
- Updating Routes… - (Layer 3 only) Once one or more tunnel is health check OK, we can proceeds to exchange routes. If you are stuck at this state, you most likely need to first check for route conflicts between peers, including WAN IPs.
- Established. - Speedfusion is connected.