Tunnel IPSec vs Fortigate
Hi Guys
I setup IPSec tunnel between Tp-Link Site A and Fortigate Site B.
Phase 1 UP
Phase 2 UP
When I try to reach an host from Site A to Site B source IP address is interface of WAN port.
In routing table there isn't static route to Site B via tunnel IPSec and it's impossible to manually add static route because there isn't tunnel IPsec as interface destination.
SSH connection doesn't exist to set parameter via CLI
Any suggest?
Thank you
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Why static route? route is automatic added when remote lan is added in vpn configuration.
but what I have seen is that there can be problems if you select several local networks on the tp-link vpn configuration, I myself have this problem against the cisco firewall. Do you need several local LANs in VPN, create several identical VPN tunnels with the same encryption and preshred key.
- Copy Link
- Report Inappropriate Content
In my Routing table there isn't any route to Site B.
I have 3 route:
No Route to Site B.
And I have only one Subnet in /16.
Site A 172.16.0.0/16
Site B 172.21.0.0/16
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
it looks right, I don't know fortigate so I can't help there, but if I had a tp-link cisco or unifi router at the other end, this would have worked.
you should not create a static route on TP-Link, it creates this itself based on the vpn configuration
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1125
Replies: 8
Voters 0
No one has voted for it yet.