Since there is no Fortigate forum, and I could only find very little information on the web about these firewalls I decided to post in here. I hope you don't mind. Here's my situation. I've got two class C blocks, one of the class C blocks xx.xx.14.xx is entirely behind my fortigate and will be used for web/email hosting services. For some reason, when I trace to any of my .14 addresses I get stuck on the Wan interface of the firewall which is on xx.xx.13.xx, note that I have no problem getting to machines on the .13 network behind the fortigate. I've created a static route on the firewall itself to the .14 network, and I still can't get to it. Can someone help??? Please...
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Fortigate 100A
- Thread starter ngazzano
- Start date
When you say that you "get stuck" on the 13 side, does that mean that the traffic routes to the 13 side or the trace dies there? If the trace dies there, do you have rules configured to allow traffic/ping traffic from the 13 interface to the 14? IIRC, the Fortigate stuff is configured to deny everything out of the box (but then I've got a 300 and a 400 and have never used a 100A).
- Status