Re: Help routing two networks
☼ Best Answerby DanST93 2019/08/13 06:27:06
and welcome to the forums.
After re-reading your post I still wonder why you use a Policy Route. A PBR is a route which is matching fields other than the destination address, like source address, port etc.
As far as I see it you only need a regular route. Actually, you don't need any extra route on the FGT - as long as your devices don't need internet access. Check 'Monitor > Routing Monitor' to see the active routes. You won't see any sign of your PBR which is one of the reasons I dislike PBRs. But, you'll see a route to the 69 subnet, and one to the 50 subnet. They are 'connected', and for subnets in which a FGT port participates, the FGT will insert a route automatically.
When you've got the routing right, you need policies to allow traffic.
You need 2 policies:
- from 50 to 69
- the reverse
If you already have the first policy, right-click it and 'clone reverse' to create the second.
For starters, use 'ALL' for service. No NAT.
The problems you state do come IMHO from missing routes on your iLO cards. Their default route needs to point to the local FGT interface (say, .50.1). Otherwise, they don't know how to reach the 69 subnet. They don't route, the FGT does.
Your switch seems to be configured correctly, though. Have a look at it's default route.
And I wonder how your DHCP server shells out addresses from the 50 subnet while it doesn't have a direct connection (a port in) this subnet. But it seems you are seeing 50's IP leases on the switch and iLos.
I'd just put a DHCP server on the 50 interface on the FGT, and DNS and NTP servers. Done.
Let's see what you find.
Ede " Kernel panic: Aiee, killing interrupt handler!"