Unlock Exclusive Benefits
Join Our Community Today!
Join our community and post in the forum to earn your exclusive Summer Badge! Become a member today!
LOGIN/REGISTER
CONTINUE AS A GUEST
- Support Forum
- Knowledge Base
- Customer Service
- Internal Article Nominations
- FortiGate
- FortiClient
- FortiADC
- FortiAIOps
- FortiAnalyzer
- FortiAP
- FortiAuthenticator
- FortiBridge
- FortiCache
- FortiCare Services
- FortiCarrier
- FortiCASB
- FortiConverter
- FortiCNP
- FortiDAST
- FortiDDoS
- FortiDB
- FortiDNS
- FortiDLP
- FortiDeceptor
- FortiDevSec
- FortiDirector
- FortiEdgeCloud
- FortiEDR
- FortiEndpoint
- FortiExtender
- FortiGate Cloud
- FortiGuard
- FortiGuest
- FortiHypervisor
- FortiInsight
- FortiIsolator
- FortiMail
- FortiManager
- FortiMonitor
- FortiNAC
- FortiNAC-F
- FortiNDR (on-premise)
- FortiNDRCloud
- FortiPAM
- FortiPhish
- FortiPortal
- FortiPresence
- FortiProxy
- FortiRecon
- FortiRecorder
- FortiSRA
- FortiSandbox
- FortiSASE
- FortiScan
- FortiSIEM
- FortiSOAR
- FortiSwitch
- FortiTester
- FortiToken
- FortiVoice
- FortiWAN
- FortiWeb
- FortiAppSec Cloud
- Lacework
- Wireless Controller
- RMA Information and Announcements
- FortiCloud Products
- ZTNA
- 4D Documents
- Customer Service
- Community Groups
- Blogs
Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
- Fortinet Community
- Support Forum
- Re: Inferface is up still cant ping from outside
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Inferface is up still cant ping from outside
I'm currently setting up a FortiGate firewall and facing a strange issue. The FortiGate WAN interface is directly connected to my ISP router.
From the FortiGate, I can ping the ISP gateway successfully.
However, from the ISP router side (or any host behind it), I cannot ping the FortiGate IP.
Here’s what I’ve checked so far:
Ping is enabled on the WAN interface (set allowaccess ping is configured).
The interface is up, IP is correctly assigned, and the cable is physically connected.
No local-in policy is blocking ICMP.
No trusted hosts are configured under the admin settings.
Subnet and default routes appear correct.
and when I connect that ips wire to my laptop it can get the internet access and able to ping my ip from outside network.
Solved! Go to Solution.
Labels:
- Labels:
-
FortiGate
1 Solution
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AHM_MANINAGAR_MNG # get router info routing-table details 103.240.162.91
Routing table for VRF=0
Routing entry for 0.0.0.0/0
Known via "static", distance 1, metric 0, best
vrf 0 185.75.142.113, via lan2 inactive
* vrf 0 43.250.164.190, via wan
If you see above output your active default route is only available via wan but you are pinging lan2 IP address and hence reverse path is failing
You are not able to ping lan2 IP because default route shows inactive via lan2. It could be because of sdwan perf sla down for lan2
If you have found a solution, please like and accept it to make it easily accessible to others.
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
20 REPLIES 20
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried using this command diagnose sniffer packet any "icmp and host 182.75.142.114" 4
and got this output:
AHM_MANINAGAR_MNG # diagnose sniffer packet a "icmp and host 182.75.142.114" 4
interfaces=[a]
filters=[icmp and host 182.75.142.114]
0.259517 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
0.356577 a -- 49.43.25.137 -> 182.75.142.114: icmp: echo request
3.258478 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
5.198390 a -- 49.43.25.137 -> 182.75.142.114: icmp: echo request
6.242370 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
9.247340 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
10.184206 a -- 49.43.25.137 -> 182.75.142.114: icmp: echo request
12.261584 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
15.180265 a -- 49.43.25.137 -> 182.75.142.114: icmp: echo request
15.297683 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
18.317582 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
21.315861 a -- 103.240.162.91 -> 182.75.142.114: icmp: echo request
^C
13 packets received by filter
0 packets dropped by kernel
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ths article hasnt been updated in years, but worth having a look https://community.fortinet.com/t5/FortiGate/Technical-Tip-FortiGate-does-not-respond-to-Ping/ta-p/19...
"jack of all trades, master of none"
"jack of all trades, master of none"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
so this firewall is not setup in my home Its my client firewall which is in other state. and I live in other state.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
and i am not getting the arp too while using get sys arp command
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
probably do some flow debug to see packet flow?
diag debug ena
diag debug flow filter clear
diag debug flow filter <filter>
diag debug flow trace start <numberofpackets>
then generate some traffic to see what happens to it.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
--
"It is a mistake to think you can solve any major problems just with
potatoes." - Douglas Adams
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the output i get
AHM_MANINAGAR_MNG # diag debug enable
AHM_MANINAGAR_MNG # diag debug flow filter clear
AHM_MANINAGAR_MNG # diag debug flow filter daddr 182.75.142.114
AHM_MANINAGAR_MNG # diag debug flow trace start
<xxx> Repeat number.
AHM_MANINAGAR_MNG # diag debug flow trace start 100
AHM_MANINAGAR_MNG # 2025-06-16 20:57:49 id=65308 trace_id=23 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103
.240.162.91:21479->182.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34500."
2025-06-16 20:57:49 id=65308 trace_id=23 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a13"
2025-06-16 20:57:49 id=65308 trace_id=23 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:49 id=65308 trace_id=23 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:52 id=65308 trace_id=24 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34548."
2025-06-16 20:57:52 id=65308 trace_id=24 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a18"
2025-06-16 20:57:52 id=65308 trace_id=24 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:52 id=65308 trace_id=24 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:53 id=65308 trace_id=25 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=6, 95.214.53.196:55229->18
2.75.142.114:16379) tun_id=0.0.0.0 from lan2. flag [S], seq 2576057558, ack 0, win 65535"
2025-06-16 20:57:53 id=65308 trace_id=25 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a1b"
2025-06-16 20:57:53 id=65308 trace_id=25 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:53 id=65308 trace_id=25 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:54 id=65308 trace_id=26 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=6, 188.166.234.65:47861->1
82.75.142.114:3326) tun_id=0.0.0.0 from lan2. flag [S], seq 2346924458, ack 0, win 1024"
2025-06-16 20:57:54 id=65308 trace_id=26 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a1c"
2025-06-16 20:57:54 id=65308 trace_id=26 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:54 id=65308 trace_id=26 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:55 id=65308 trace_id=27 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34596."
2025-06-16 20:57:55 id=65308 trace_id=27 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a1d"
2025-06-16 20:57:55 id=65308 trace_id=27 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:55 id=65308 trace_id=27 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:55 id=65308 trace_id=28 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=6, 149.50.106.170:45708->1
82.75.142.114:2345) tun_id=0.0.0.0 from lan2. flag [S], seq 3174029474, ack 0, win 65535"
2025-06-16 20:57:55 id=65308 trace_id=28 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a20"
2025-06-16 20:57:55 id=65308 trace_id=28 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:55 id=65308 trace_id=28 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:57:58 id=65308 trace_id=29 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34644."
2025-06-16 20:57:58 id=65308 trace_id=29 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a21"
2025-06-16 20:57:58 id=65308 trace_id=29 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:57:58 id=65308 trace_id=29 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:01 id=65308 trace_id=30 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34692."
2025-06-16 20:58:01 id=65308 trace_id=30 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a26"
2025-06-16 20:58:01 id=65308 trace_id=30 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:01 id=65308 trace_id=30 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:04 id=65308 trace_id=31 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34740."
2025-06-16 20:58:04 id=65308 trace_id=31 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a2e"
2025-06-16 20:58:04 id=65308 trace_id=31 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:04 id=65308 trace_id=31 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:07 id=65308 trace_id=32 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34788."
2025-06-16 20:58:07 id=65308 trace_id=32 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a35"
2025-06-16 20:58:07 id=65308 trace_id=32 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:07 id=65308 trace_id=32 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:10 id=65308 trace_id=33 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34836."
2025-06-16 20:58:10 id=65308 trace_id=33 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a3a"
2025-06-16 20:58:10 id=65308 trace_id=33 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:10 id=65308 trace_id=33 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:13 id=65308 trace_id=34 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34884."
2025-06-16 20:58:13 id=65308 trace_id=34 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a48"
2025-06-16 20:58:13 id=65308 trace_id=34 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:13 id=65308 trace_id=34 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:15 id=65308 trace_id=35 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.19.134.226:1->182.7
5.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=1, seq=115."
2025-06-16 20:58:15 id=65308 trace_id=35 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a51"
2025-06-16 20:58:15 id=65308 trace_id=35 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:15 id=65308 trace_id=35 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:16 id=65308 trace_id=36 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
82.75.142.114:2048) tun_id=0.0.0.0 from lan2. type=8, code=0, id=21479, seq=34932."
2025-06-16 20:58:16 id=65308 trace_id=36 func=init_ip_session_common line=5995 msg="allocate a new session-000f0a53"
2025-06-16 20:58:16 id=65308 trace_id=36 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop"
2025-06-16 20:58:16 id=65308 trace_id=36 func=ip_session_handle_no_dst line=6081 msg="trace"
2025-06-16 20:58:19 id=65308 trace_id=37 func=print_pkt_detail line=5811 msg="vd-root:0 received a packet(proto=1, 103.240.162.91:21479->1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
From the pcap and debug flow I can see that traffic is received on the FGT but it is getting drop due to reverse path failure
2025-06-16 20:57:58 id=65308 trace_id=29 func=ip_route_input_slow line=2267 msg="reverse path check fail, drop
Share below output
get router info routing-table details 103.240.162.91
get router info routing-table all
If you have found a solution, please like and accept it to make it easily accessible to others.
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AHM_MANINAGAR_MNG # get router info routing-table details 103.240.162.91
Routing table for VRF=0
Routing entry for 0.0.0.0/0
Known via "static", distance 1, metric 0, best
vrf 0 185.75.142.113, via lan2 inactive
* vrf 0 43.250.164.190, via wan
AHM_MANINAGAR_MNG # get router info routing-table all
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
V - BGP VPNv4
* - candidate default
Routing table for VRF=0
S* 0.0.0.0/0 [1/0] via 43.250.164.190, wan, [1/0]
B 10.0.10.0/23 [200/0] via 10.250.200.101 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.12.0/23 [200/0] via 10.250.200.51 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.0.14.0/23 [200/0] via 10.250.200.117 [3] (recursive is directly connected, HO1_ Aerloop), 01:57:17, [1/0]
B 10.0.16.0/23 [200/0] via 10.250.200.79 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.18.0/23 [200/0] via 10.250.200.99 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.20.0/23 [200/0] via 10.250.200.78 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.0.24.0/23 [200/0] via 10.250.200.104 [3] (recursive is directly connected, HO1_ Aerloop), 02:12:49, [1/0]
B 10.0.26.0/23 [200/0] via 10.250.200.124 [3] (recursive is directly connected, HO1_ Aerloop), 01:53:42, [1/0]
B 10.0.28.0/23 [200/0] via 10.250.200.16 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.0.30.0/23 [200/0] via 10.250.200.39 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.0.32.0/23 [200/0] via 10.250.200.6 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.34.0/23 [200/0] via 10.250.200.110 [3] (recursive is directly connected, HO1_ Aerloop), 02:02:14, [1/0]
B 10.0.36.0/23 [200/0] via 10.250.200.81 [3] (recursive is directly connected, HO1_ Aerloop), 00:06:50, [1/0]
B 10.0.38.0/23 [200/0] via 10.250.200.135 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.40.0/23 [200/0] via 10.250.200.134 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.42.0/23 [200/0] via 10.250.200.30 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.0.46.0/23 [200/0] via 10.250.200.89 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.0.48.0/23 [200/0] via 10.250.200.107 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.50.0/23 [200/0] via 10.250.200.96 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.54.0/23 [200/0] via 10.250.200.111 [3] (recursive is directly connected, HO1_ Aerloop), 02:08:30, [1/0]
B 10.0.56.0/23 [200/0] via 10.250.200.10 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:06, [1/0]
B 10.0.58.0/23 [200/0] via 10.250.200.64 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.0.60.0/23 [200/0] via 10.250.200.34 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.0.62.0/23 [200/0] via 10.250.200.108 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.64.0/23 [200/0] via 10.250.200.23 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.0.66.0/23 [200/0] via 10.250.200.17 [3] (recursive is directly connected, HO1_ Aerloop), 02:34:13, [1/0]
B 10.0.68.0/23 [200/0] via 10.250.200.86 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.0.70.0/23 [200/0] via 10.250.200.120 [3] (recursive is directly connected, HO1_ Aerloop), 01:48:50, [1/0]
B 10.0.76.0/23 [200/0] via 10.250.200.80 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.78.0/23 [200/0] via 10.250.200.69 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.80.0/23 [200/0] via 10.250.202.33 [3] (recursive via 43.250.164.190, wan), 00:57:25, [1/0]
B 10.0.82.0/23 [200/0] via 10.250.200.57 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.86.0/23 [200/0] via 10.250.200.127 [3] (recursive is directly connected, HO1_ Aerloop), 01:43:11, [1/0]
B 10.0.88.0/23 [200/0] via 10.250.200.55 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.0.90.0/23 [200/0] via 10.250.200.92 [3] (recursive is directly connected, HO1_ Aerloop), 02:47:51, [1/0]
B 10.0.92.0/23 [200/0] via 10.250.200.133 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.0.0/23 [200/0] via 10.250.200.46 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.4.0/23 [200/0] via 10.250.200.105 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.6.0/23 [200/0] via 10.250.200.126 [3] (recursive is directly connected, HO1_ Aerloop), 00:47:17, [1/0]
B 10.1.8.0/23 [200/0] via 10.250.200.19 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.1.10.0/23 [200/0] via 10.250.200.11 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.12.0/23 [200/0] via 10.250.200.103 [3] (recursive is directly connected, HO1_ Aerloop), 02:08:30, [1/0]
B 10.1.14.0/23 [200/0] via 10.250.200.82 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.1.16.0/23 [200/0] via 10.250.200.52 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.1.18.0/23 [200/0] via 10.250.200.67 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.20.0/23 [200/0] via 10.250.200.47 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.22.0/23 [200/0] via 10.250.200.7 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.24.0/23 [200/0] via 10.250.200.29 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.1.26.0/23 [200/0] via 10.250.200.38 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.1.32.0/23 [200/0] via 10.250.200.70 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.1.34.0/23 [200/0] via 10.250.200.14 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.2.0.0/23 [200/0] via 10.250.212.1 [3] (recursive is directly connected, RO1_G_GTPL), 01:04:09, [1/0]
C 10.2.4.0/23 is directly connected, lan1
B 10.2.6.0/23 [200/0] via 10.250.200.98 [2] (recursive is directly connected, HO1_ Aerloop), 02:15:43, [1/0]
[200/0] via 10.250.212.13 (recursive is directly connected, RO1_G_GTPL), 02:15:43, [1/0]
B 10.2.8.0/23 [200/0] via 10.250.200.36 [2] (recursive is directly connected, HO1_ Aerloop), 02:51:18, [1/0]
[200/0] via 10.250.212.9 (recursive is directly connected, RO1_G_GTPL), 02:51:18, [1/0]
B 10.2.10.0/23 [200/0] via 10.250.200.87 [2] (recursive is directly connected, HO1_ Aerloop), 1d01h49m, [1/0]
[200/0] via 10.250.212.19 (recursive is directly connected, RO1_G_GTPL), 1d01h49m, [1/0]
B 10.2.12.0/23 [200/0] via 10.250.200.24 [2] (recursive is directly connected, HO1_ Aerloop), 01:52:42, [1/0]
[200/0] via 10.250.212.18 (recursive is directly connected, RO1_G_GTPL), 01:52:42, [1/0]
B 10.2.14.0/23 [200/0] via 10.250.200.114 [2] (recursive is directly connected, HO1_ Aerloop), 01:07:32, [1/0]
[200/0] via 10.250.212.14 (recursive is directly connected, RO1_G_GTPL), 01:07:32, [1/0]
B 10.2.16.0/23 [200/0] via 10.250.200.115 [2] (recursive is directly connected, HO1_ Aerloop), 02:01:51, [1/0]
[200/0] via 10.250.212.16 (recursive is directly connected, RO1_G_GTPL), 02:01:51, [1/0]
B 10.2.18.0/23 [200/0] via 10.250.200.100 [2] (recursive is directly connected, HO1_ Aerloop), 1d03h02m, [1/0]
[200/0] via 10.250.212.11 (recursive is directly connected, RO1_G_GTPL), 1d03h02m, [1/0]
B 10.2.20.0/23 [200/0] via 10.250.202.89 [2] (recursive via 43.250.164.190, wan), 02:02:40, [1/0]
[200/0] via 10.250.212.20 (recursive is directly connected, RO1_G_GTPL), 02:02:40, [1/0]
B 10.2.22.0/23 [200/0] via 10.250.200.132 [2] (recursive is directly connected, HO1_ Aerloop), 1d03h02m, [1/0]
[200/0] via 10.250.212.7 (recursive is directly connected, RO1_G_GTPL), 1d03h02m, [1/0]
B 10.2.24.0/23 [200/0] via 10.250.200.130 [2] (recursive is directly connected, HO1_ Aerloop), 03:03:59, [1/0]
[200/0] via 10.250.212.4 (recursive is directly connected, RO1_G_GTPL), 03:03:59, [1/0]
B 10.2.58.0/23 [200/0] via 10.250.200.122 [2] (recursive is directly connected, HO1_ Aerloop), 01:53:42, [1/0]
[200/0] via 10.250.212.10 (recursive is directly connected, RO1_G_GTPL), 01:53:42, [1/0]
B 10.2.64.0/23 [200/0] via 10.250.200.62 [2] (recursive is directly connected, HO1_ Aerloop), 02:15:22, [1/0]
[200/0] via 10.250.212.12 (recursive is directly connected, RO1_G_GTPL), 02:15:22, [1/0]
B 10.2.98.0/23 [200/0] via 10.250.200.43 [2] (recursive is directly connected, HO1_ Aerloop), 02:51:16, [1/0]
[200/0] via 10.250.212.8 (recursive is directly connected, RO1_G_GTPL), 02:51:16, [1/0]
B 10.2.100.0/23 [200/0] via 10.250.200.91 [2] (recursive is directly connected, HO1_ Aerloop), 02:51:16, [1/0]
[200/0] via 10.250.212.6 (recursive is directly connected, RO1_G_GTPL), 02:51:16, [1/0]
B 10.2.102.0/23 [200/0] via 10.250.200.77 [2] (recursive is directly connected, HO1_ Aerloop), 1d03h02m, [1/0]
[200/0] via 10.250.212.3 (recursive is directly connected, RO1_G_GTPL), 1d03h02m, [1/0]
B 10.2.104.0/23 [200/0] via 10.250.200.13 [2] (recursive is directly connected, HO1_ Aerloop), 01:04:22, [1/0]
[200/0] via 10.250.212.15 (recursive is directly connected, RO1_G_GTPL), 01:04:22, [1/0]
B 10.2.106.0/23 [200/0] via 10.250.200.71 [2] (recursive is directly connected, HO1_ Aerloop), 1d03h02m, [1/0]
[200/0] via 10.250.212.17 (recursive is directly connected, RO1_G_GTPL), 1d03h02m, [1/0]
B 10.2.114.0/23 [200/0] via 10.250.200.60 [2] (recursive is directly connected, HO1_ Aerloop), 04:17:39, [1/0]
[200/0] via 10.250.212.2 (recursive is directly connected, RO1_G_GTPL), 04:17:39, [1/0]
B 10.3.0.0/23 [200/0] via 10.250.222.1 [3] (recursive via 43.250.164.190, wan), 00:27:59, [1/0]
B 10.3.4.0/23 [200/0] via 10.250.200.88 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.3.6.0/23 [200/0] via 10.250.200.54 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:06, [1/0]
B 10.3.8.0/23 [200/0] via 10.250.200.75 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.3.10.0/23 [200/0] via 10.250.200.50 [3] (recursive is directly connected, HO1_ Aerloop), 03:35:45, [1/0]
B 10.3.12.0/23 [200/0] via 10.250.200.15 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.3.14.0/23 [200/0] via 10.250.200.41 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.3.16.0/23 [200/0] via 10.250.200.3 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.3.18.0/23 [200/0] via 10.250.200.22 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.3.20.0/23 [200/0] via 10.250.200.53 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.3.22.0/23 [200/0] via 10.250.200.56 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.3.24.0/23 [200/0] via 10.250.200.59 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.3.26.0/23 [200/0] via 10.250.200.116 [3] (recursive is directly connected, HO1_ Aerloop), 01:59:10, [1/0]
B 10.3.28.0/23 [200/0] via 10.250.200.33 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.3.30.0/23 [200/0] via 10.250.200.45 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.3.32.0/23 [200/0] via 10.250.200.31 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.3.34.0/23 [200/0] via 10.250.200.2 [3] (recursive is directly connected, HO1_ Aerloop), 00:30:16, [1/0]
B 10.3.36.0/23 [200/0] via 10.250.200.66 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.3.38.0/23 [200/0] via 10.250.200.37 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.3.40.0/23 [200/0] via 10.250.200.32 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.3.42.0/23 [200/0] via 10.250.200.76 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.3.44.0/23 [200/0] via 10.250.200.49 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.4.0.0/23 [200/0] via 10.250.200.85 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.4.4.0/23 [200/0] via 10.250.200.20 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:32, [1/0]
B 10.4.6.0/23 [200/0] via 10.250.200.119 [3] (recursive is directly connected, HO1_ Aerloop), 01:55:29, [1/0]
B 10.4.8.0/23 [200/0] via 10.250.200.28 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.4.10.0/23 [200/0] via 10.250.200.25 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.4.12.0/23 [200/0] via 10.250.200.94 [3] (recursive is directly connected, HO1_ Aerloop), 02:15:18, [1/0]
B 10.4.14.0/23 [200/0] via 10.250.200.90 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.4.16.0/23 [200/0] via 10.250.200.58 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.5.0.0/23 [200/0] via 10.250.200.18 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.5.4.0/23 [200/0] via 10.250.200.61 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.5.6.0/23 [200/0] via 10.250.200.74 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.5.8.0/23 [200/0] via 10.250.200.109 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.5.10.0/23 [200/0] via 10.250.200.40 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.6.0.0/23 [200/0] via 10.250.214.1 [3] (recursive via 43.250.164.190, wan), 02:51:09, [1/0]
B 10.6.6.0/23 [200/0] via 10.250.200.26 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.8.0/23 [200/0] via 10.250.200.123 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.10.0/23 [200/0] via 10.250.200.44 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.12.0/23 [200/0] via 10.250.200.73 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.14.0/23 [200/0] via 10.250.200.84 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.18.0/23 [200/0] via 10.250.200.72 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.20.0/23 [200/0] via 10.250.200.27 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.24.0/23 [200/0] via 10.250.200.21 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.26.0/23 [200/0] via 10.250.200.131 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.28.0/23 [200/0] via 10.250.200.102 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.30.0/23 [200/0] via 10.250.200.8 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.32.0/23 [200/0] via 10.250.200.93 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.34.0/23 [200/0] via 10.250.200.35 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.36.0/23 [200/0] via 10.250.200.4 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.38.0/23 [200/0] via 10.250.200.106 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.40.0/23 [200/0] via 10.250.200.97 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.50.0/23 [200/0] via 10.250.200.118 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.62.0/23 [200/0] via 10.250.200.112 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.64.0/23 [200/0] via 10.250.200.113 [3] (recursive is directly connected, HO1_ Aerloop), 02:07:34, [1/0]
B 10.6.66.0/23 [200/0] via 10.250.200.95 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.68.0/23 [200/0] via 10.250.200.68 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.6.70.0/23 [200/0] via 10.250.200.65 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.7.4.0/23 [200/0] via 10.250.200.63 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.7.6.0/23 [200/0] via 10.250.200.42 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.7.8.0/23 [200/0] via 10.250.200.9 [3] (recursive is directly connected, HO1_ Aerloop), 02:49:56, [1/0]
B 10.7.10.0/23 [200/0] via 10.250.200.48 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.7.12.0/23 [200/0] via 10.250.200.128 [3] (recursive is directly connected, HO1_ Aerloop), 01:38:51, [1/0]
B 10.7.16.0/23 [200/0] via 10.250.200.129 [3] (recursive is directly connected, HO1_ Aerloop), 01:38:51, [1/0]
B 10.7.18.0/23 [200/0] via 10.250.200.83 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.7.20.0/23 [200/0] via 10.250.200.12 [3] (recursive is directly connected, HO1_ Aerloop), 02:50:44, [1/0]
B 10.7.22.0/23 [200/0] via 10.250.200.5 [3] (recursive is directly connected, HO1_ Aerloop), 02:51:09, [1/0]
B 10.10.0.0/22 [200/0] via 10.250.200.1 [2] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
[200/0] via 10.250.204.1 (recursive is directly connected, HO3_Airtel), 04:17:16, [1/0]
B 10.200.255.250/32 [200/0] via 10.250.222.1 [3] (recursive via 43.250.164.190, wan), 00:27:59, [1/0]
B 10.200.255.251/32 [200/0] via 10.250.200.46 [3] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
B 10.200.255.252/32 [200/0] via 10.250.214.1 [3] (recursive via 43.250.164.190, wan), 02:51:09, [1/0]
B 10.200.255.253/32 [200/0] via 10.250.212.1 [3] (recursive is directly connected, RO1_G_GTPL), 01:04:09, [1/0]
B 10.200.255.254/32 [200/0] via 10.250.200.1 [2] (recursive is directly connected, HO1_ Aerloop), 04:17:16, [1/0]
[200/0] via 10.250.204.1 (recursive is directly connected, HO3_Airtel), 04:17:16, [1/0]
C 10.250.200.0/23 is directly connected, HO1_ Aerloop
C 10.250.200.121/32 is directly connected, HO1_ Aerloop
C 10.250.204.0/23 is directly connected, HO3_Airtel
C 10.250.204.30/32 is directly connected, HO3_Airtel
C 10.250.212.0/23 is directly connected, RO1_G_GTPL
C 10.250.212.5/32 is directly connected, RO1_G_GTPL
C 43.250.164.128/26 is directly connected, wan
C 182.75.142.112/29 is directly connected, lan2
AHM_MANINAGAR_MNG # Timeout
Connection lost. Press Enter to start a new session.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AHM_MANINAGAR_MNG # get router info routing-table details 103.240.162.91
Routing table for VRF=0
Routing entry for 0.0.0.0/0
Known via "static", distance 1, metric 0, best
vrf 0 185.75.142.113, via lan2 inactive
* vrf 0 43.250.164.190, via wan
If you see above output your active default route is only available via wan but you are pinging lan2 IP address and hence reverse path is failing
You are not able to ping lan2 IP because default route shows inactive via lan2. It could be because of sdwan perf sla down for lan2
If you have found a solution, please like and accept it to make it easily accessible to others.
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
Fortinet Certified Expert (FCX) | #NSE8-003459
Salon Raj Joshi
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
so what should i do now
Labels
-
FortiGate
10,179 -
FortiClient
2,067 -
FortiManager
863 -
5.2
687 -
FortiAnalyzer
659 -
5.4
638 -
FortiSwitch
561 -
FortiAP
539 -
FortiClient EMS
526 -
6.0
416 -
IPsec
367 -
5.6
362 -
FortiMail
361 -
SSL-VPN
352 -
FortiNAC
258 -
6.2
251 -
Fortiweb
243 -
FortiAuthenticator v5.5
234 -
SD-WAN
177 -
FortiGuard
159 -
FortiAuthenticator
155 -
5.0
152 -
6.4
128 -
Firewall policy
128 -
FortiGateCloud
112 -
FortiCloud Products
112 -
FortiGate-VM
109 -
FortiSIEM
108 -
FortiToken
106 -
Wireless Controller
93 -
Customer Service
85 -
High Availability
80 -
FortiProxy
74 -
ZTNA
70 -
Routing
69 -
VLAN
69 -
FortiEDR
68 -
Fortivoice
67 -
DNS
67 -
SAML
64 -
FortiADC
63 -
BGP
62 -
Authentication
61 -
radius
57 -
Certificate
56 -
FortiLink
52 -
LDAP
52 -
FortiSandbox
51 -
FortiExtender
51 -
SSO
51 -
4.0MR3
49 -
NAT
49 -
FortiDNS
43 -
VDOM
41 -
Interface
40 -
Logging
39 -
Application control
39 -
FortiGate v5.4
38 -
FortiSwitch v6.4
38 -
Virtual IP
37 -
FortiConnect
34 -
Web profile
34 -
FortiPAM
32 -
FortiWAN
31 -
SSL SSH inspection
30 -
FortiConverter
28 -
FortiGate v5.2
27 -
Automation
26 -
Static route
25 -
Traffic shaping
24 -
SSID
24 -
FortiSwitch v6.2
23 -
FortiPortal
23 -
Fortigate Cloud
22 -
SNMP
22 -
System settings
22 -
API
21 -
WAN optimization
20 -
FortiMonitor
19 -
OSPF
19 -
Security profile
17 -
Web application firewall profile
17 -
FortiDDoS
16 -
FortiSOAR
16 -
FortiAP profile
16 -
Web rating
16 -
Admin
15 -
Proxy policy
15 -
IP address management - IPAM
15 -
FortiGate v5.0
14 -
FortiCASB
14 -
IPS signature
14 -
Explicit proxy
13 -
Intrusion prevention
13 -
FortiManager v4.0
12 -
Traffic shaping policy
12 -
FortiManager v5.0
11 -
FortiRecorder
11 -
NAC policy
11 -
Fabric connector
11 -
Port policy
11 -
FortiAnalyzer v5.0
10 -
FortiWeb v5.0
10 -
FortiBridge
10 -
DNS filter
10 -
Trunk
10 -
Users
10 -
Traffic shaping profile
10 -
Fortinet Engage Partner Program
10 -
FortiGate v4.0 MR3
9 -
FortiDeceptor
9 -
RMA Information and Announcements
9 -
Antivirus profile
9 -
FortiCache
8 -
FortiToken Cloud
8 -
Authentication rule and scheme
8 -
4.0
7 -
4.0MR2
7 -
Packet capture
7 -
Application signature
7 -
VoIP profile
6 -
FortiCarrier
5 -
FortiScan
5 -
FortiNDR
5 -
FortiTester
5 -
DLP profile
5 -
DLP sensor
5 -
DoS policy
5 -
Email filter profile
5 -
Protocol option
5 -
Cloud Management Security
5 -
Vulnerability Management
5 -
3.6
4 -
FortiDirector
4 -
Internet service database
4 -
DLP Dictionary
4 -
Netflow
4 -
TACACS
4 -
Replacement messages
4 -
SDN connector
4 -
Service
4 -
Multicast routing
4 -
FortiDB
3 -
FortiHypervisor
3 -
Kerberos
3 -
File filter
3 -
Multicast policy
3 -
FortiInsight
2 -
FortiAI
2 -
Video Filter
2 -
Schedule
2 -
ICAP profile
2 -
Zone
2 -
FortiEdge Cloud
2 -
FortiGuest
2 -
4.0MR1
1 -
FortiManager-VM
1 -
FortiCWP
1 -
Subscription Renewal Policy
1 -
Virtual wire pair
1 -
Lacework
1 -
FortiEdge
1 -
FortiAIOps
1
Top Kudoed Authors
| User | Count |
|---|---|
| 2424 | |
| 1303 | |
| 778 | |
| 551 | |
| 455 |
Broad. Integrated. Automated.
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.
Security Research
Company
News & Articles
Copyright 2025 Fortinet, Inc. All Rights Reserved.