FGT60F has two WAN lines.
Reviewed the configuration with FWF60D to test WAN1
It is the same WAN1 setting. FWF60D is normal:
Confirm the Fixed IP line normal
When set FGT60F's WAN1 to be dynamic IP, the WAN1 can ping another device that can ping back FGT60F
Not sure why Fixed IP fails but Dynamic IP works on FGT60F
WAN1: Dynamic
exec ping-option reset
exec ping-option interface wan1
exec ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=58 time=1.7 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=1.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=1.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=1.4 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=1.4 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.4/1.4/1.7 ms
WAN1: Fixed
exec ping-option reset
exec ping-option interface wan1
exec ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
sendmsg failed: 101(Network is unreachable)
sendmsg failed: 101(Network is unreachable)
sendmsg failed: 101(Network is unreachable)
sendmsg failed: 101(Network is unreachable)
sendmsg failed: 101(Network is unreachable)
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
WAN2: Dynamic
exec ping-option reset
exec ping-option interface wan2
exec ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=59 time=2.8 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=3.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=2.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=2.8 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=2.9 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.8/2.9/3.1 ms
#FortiGate60F
Solved! Go to Solution.
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.
Obviously, your wan1 default route is not active because it has higher administrative distance. Both default routes should have the same distance. Please refer to https://community.fortinet.com/t5/FortiGate/Technical-Tip-Adding-new-DHCP-addressing-mode-wan-connec...
Routing table for VRF=0
S 0.0.0.0/0 [15/0] via FIXED.IP.123.105, wan1, [1/0]
S *> 0.0.0.0/0 [5/0] via DHCP.IP.161.1, wan2, [1/0]
Regards,
Thanks! Solved it by your suggestion.
1. Set the priority number of DHCP line higher than the Fixed IP line
2. Config the distance to be the same to ensure both routes active
config router static
edit 1
set gateway DHCP.IP.161.1
set distance 5
set priority 10
set device "wan2"
next
edit 2
set gateway FIXED.IP.123.105
set distance 5
set device "wan1"
next
end
get router info routing-table database
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
> - selected route, * - FIB route, p - stale info
Routing table for VRF=0
S *> 0.0.0.0/0 [5/0] via FIXED.IP.123.105, wan1, [1/0]
*> [5/0] via DHCP.IP.161.1, wan2, [10/0]
3. Setup link monitor
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 |
---|---|
1634 | |
1063 | |
751 | |
443 | |
210 |
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.