Policy not directing web traffic to WAN2

Forum|Forum|8 years ago
January 19, 2018
7 replies
9263 views

There's a good chance that I'm going about this the wrong way, but it feels like I'm close to the solution.

I have a 60D running FortiOS 5.4. WAN1 is connected to my modem router and WAN2 is connected to a VPN router, which is connected to the Modem Router.

Both interfaces are configured identically other than the IP Address.

There's then two IPV4 policies

[ul]

Policy ID #1, Seq #2 is a catch all for all internal traffic to go to WAN1.

Policy ID #9, Seq #1 has anything incoming from internal with the source of a named address to go out on WAN2[/ul]

However, the named address is still going out on WAN1, although I can access the VPN router connected to WAN2. If I change Policy ID #9 to deny and WAN1 then internet access is denied to that box.

What have I missed?

5.4

dmcquade

New Member

Did you try creating a policy route for the named source? Here you can define the incoming interface, source, outgoing interface, destination and various protocol options. This should do the trick.

HTH

d

_RobAuthor

New Member

I've created a policy route with:

Protocol: Any

Incoming Interface: internal

Source addres/mask: 192.168.3.23/255.255.255.255

Destination address/mask: 0.0.0.0/0.0.0.0

Action: Forward Tradffic

Outgoing interface: Wan2

Gateway address: 0.0.0.0

Still going through WAN1 :\

dmcquade

New Member

Policy routes take precedence over static. You should have a static default route set and use a policy route where necessary. Looks like you are missing the gateway. Set this to the WAN2 interface next hop (ISP router address).

HTH

d

Sign up

Login with SSO

Login to the community

Login with SSO