We are setting up static IPs from two ISP provider on one Forgitate
300.The first ISP setup using default static route works, but adding the
2nd ISP doesn't.Static routes and Policies are as follow Static Routes
:0.0.0.0/0.0.0.0, GW: up.ISPa.169.229 ...
Port 1: gw.xx.xx.81/29 (WAN)Port 2: lan.xx.xx.99/24 (DHCP)Policy IPv4:
Port 2 to Port 1 (all to all, NAT enabled) I've tested at Port 1 that
internet is accessible using static IP.When connected to Port 2 with a
LAN IP via DHCP, internet is inaccessi...
We've 8 static IP and tried to setup a WAN router using Fortigate 300 as
follow...Port 1: ISP gateway (isp.xx.xx.229/30)Port 2: WAN Router
(inet.xx.xx.81/29)Port 3: 192.168.1.99/24 with DHCP enabled Static
Route: 0.0.0.0/0.0.0.0 using gateway isp.229...
Vishal Sahu, We have created a policy route instead which takes Incoming
Port 7, source address 0.0.0.0/0 to destination 0.0.0.0/0 to Outgoing
interface Port 6 and gateway address 29.52.38.81. We could ping
29.52.38.81 on LAN, however unable to ping ...
Hi Vishal Sahu, The static route 192.168.1.99/255.255.255.255 attempts
to set 29.52.38.81(port6) as the gateway for internet access from LAN,
otherwise the default route takes place to 29.51.169.229(port5) which is
no good as this is our ISP downstre...
Hi Vishal Sahu, We managed to observe ping results using one ISP
connectivity via Port5/6 set and will try again during weekend with both
ISP services connected 8-) We've configured Port 7 as 192.168.1.99 with
DHCP enabled.At static route, a new entr...
Hi Vishal Sahu, We didn't quite follow 8-(we started a SSH session to
setup the diagnostic settings at source address 29.51.38.81 followed by
diag sniffer packet any "host 29.51.38.81 and host 8.8.8.8 and proto 1"
4 0 a.Then at the CLI console in the...
