Hello everyone Currently I am trying to make a VPN Site to Site between
a Fortigate 90D and a TP-LINK TL-R600VPN however I am facing an issue in
which the Fortigate CLI can make a ping to the private TP-LINK gateway
(192.168.4.1), and one of the mach...
As requested here is the sniffer, IP-A is public IP for Fortigate, IP-B
is public for TP-LINK, as you can notice there is an IP that is not
hidden due to being a Microsoft IP in the city of redmond, and it is not
a known IP to our company. Why is it ...
The TP-LINK side configures the routing automatically once you create
the VPN and there isn' t a way to configure a distance on that router If
I do the tracert from the 192.168.3.23 (Fortigate side) it gets stuck on
the 192.168.3.1 IP of Fortigate, h...
Hi. Thanks for the answer, as you correctly stated, I had a policy route
through the VPN (left only the static route I stated above), I removed
it and the VPN from the TP-LINK side works for all of the 192.168.3.0/24
of the Fortigate side, however, t...
Hello Maybe you can get something from this cli log I made, this log is
the result of a Ping between 192.168.3.23 and 192.168.4.100, the ping
didn' t respond but here is the log CXRFTG # diag debug enable CXRFTG #
diag debug flow filter daddr 192.168...
Hello I have the following routing policy IP 192.168.4.0/255.255.255.0
Device Castellana (The VPN I created) BTW, using diag debug flow I
notice that rxp and txp packets are increasing, so I don' t think it has
to do with the VPN, rather than the rou...
