Hi,
I'm trying to schedule a full-config backup, from a 40F to a ftp server visible on vpn s2s.
using this command:
execute backup full-config ftp '/xxx/FGT_%%date%%.txt' 10.3.64.113 user pwd
I receive this output:
"Send config file to ftp server via vdom root failed."
ping from fgt to the server not working, so I did a packet capture for destination ip 10.3.64.113 and I found that the Fortigate use, by default, the wan interface, but in this case that port is disabled and I'm using A port as a Wan port.
what can i do to route the backup procedure correctly via vpn s2s using the correct tunnel-interface?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Created on 11-28-2024 08:56 AM Edited on 11-28-2024 08:59 AM
Hi @birillo ,
You did not assign an IP to "VPN-SF-HQ".
If the said IPSec VPN interface has no IP assigned, when traffic originated from FGT itself is being sent to this IPSec VPN tunnel, it will pick up one interface IP on this FGT as the source.
So always testing with passthrough traffic which has its own source IP.
Hi @dingjerry_FTNT thanks I resolved.
- assigned IP to vpn tunnels
- added a static route to destinations tunnel ip
- modified policy on both firewalls to accept incoming connection from tunnel ip
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
227 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.