Hi,I'm trying do do IPSEC between my Fortigate and a TP-Link MR 600 (4G
router).My Fortigate is traversing NAT.The configuration seems fine on
both ends but the phase 1 don't go up.Here are the log messages (public
IPs have been anonymised), I do not...
Hi,I'm having an issue with one of my VPN portals.I have a range of 20IP
available for 5 accounts, so more than enough.The range is from
10.3.0.78 to 10.3.0.99. Today, users get the IP from 10.3.0.97-99 when
connecting.When a fourth user try to conne...
Hi,I'm using a Fortigate 1500D with VDOMs in 6.0.14.Here is my network
topology :Initialy, there is only N2 and N3 communicating with a static
route on my firewall by R1 and R2.My goal here is to add N1 which has to
communicate with N3 using IPSEC co...
unfortunatly, there is no log on the TP-Link regarding IPSEC.I see both
devices communicating on both port 500 and 4500.The firmware I'm using
on the TP-Link to activate the VPN IPSEC feature is a beta firmware. I'm
asking TP-Link if there is an upda...
Thank you for the answer, using fortianalyzer, I can see the messages
coming from the TP-link on port 4500 and it seems that the fortigate is
responding. Maybe the firewall is not having what it is looking for in
the response from the TP-Link ?I'll o...
It's true that this issue could match with my problem.What's weird is
that this is the only portal doing that over 50 portals.Is it possible
that it's the forticlient the user use that is doing this ?To temporarly
bypass this problem, I've affected a...
Tested today, it worked :DFinal configuration on the firewall :First
configure IPSEC with remote IP address like on this KBConfigure one
route to N3 using IPSEC GW with weight of 10Configure one route to N3
using R1 GW with weight of 10Configure one ...
