I have setup my first pepVPN and thought it worked just fine until I found out that it works only one way : From one place (main) I can reach whatever machine on the other one, but the reverse seems not true. It seems I can’t even ping any machine from the other side to the main one…
And more precisely, even the remote routeur can’t ping the main one (while pepVPN status is green everywhere)…
PepVPN looked symetrical to me. I must have missed something.
Destination subnet (at main site) able to learn by remote Balance router? Please check via Status > SpeedFusion.
Ensure traffics not block by firewall. Please check via > Network > Access Rules > Internal Network Firewall Rules > Default rule = Allow on both main and remote Balance routers. Fyi, Internal Firewall supported since v6.2.1.
I just need your confirmation whether this static route is available on remote router. 192.168.1.0/24 will not learn from SpeedFusion peer if you have local static for same subnet.
One question, waiting for my ticket to be processed : Where and how on the PepVPN definition should I state which LAN I want to be “connected” to the pepVPN (remember that, on the main router, I have 2 LANs).
I don’t see any place to do that (except if I enable NAT on the pepVPN - but I don’t think I should need to enable NAT to be able to select which LAN pepVPN will connect to…
Ah, so this is not what i want. This means that if this would work properly, i would need to use the firewall rule you gave me in à différent topic to prevent the access to the LAN i don’t want to see involved? Right ?
Or maybe using NAT option is what i should do then? Would that give me what i want?
Coming back to this, is there a firewall rule that I could add that would ensure that my PepVPN connection is not visible to the second LAN on the main site?