I have several RFC1918 subnets on various interfaces of my Fortigate. My
Fortigate is advertising info OSPF a default route. This is causing my
internal routers to pass up traffic to unused subnets (like
192.168.200.0/24) to the Fortigate. The Fortig...
Right now, in order to add a passive interface to OSPF I need to
enumerate all of the existing passive interfaces, plus the new one. Am I
missing an easier way, perhaps a passive-interface-default or
passive-interface-default-except option? Example: ...
Can anyone point me in the general direction of what causes this error
message? smtp helo/ehlo domain name DNS check failed. Starting last
night, thousands of legitimate email was being blocked at the Fortigate.
I have since disabled antispam protect...
Thanks ede_pfau. This is what I wanted, and what I figured that I needed
to do. I was just looking to see how anyone else was doing it. I ended
up blocking the routes by way of firewall policy to ensure that it would
show up in the GUI. I figure that...
Internal Routers speak OSPF with Fortigate. Fortigate has a default
route configured to the Internet. All internal routes are advertised
into OSPF. At this point, if you look at a routing table you' ll see
entries for all of your internal networks an...
We don' t have any outside... But we' ve just got a static 0.0.0.0
pointing to the Internet. That default route will send out all unknown
destinations (including RFC1918) to the next hop, regardless of if it is
private or not.
I have a working NPS RADIUS server passing group membership back to a
FortiSSL: 1. Create a new Network Policy (Network Policy and Access
Services > NPS > Policies > Network Policies > New • Name: VPN-Example
• Type of network access server: Unsp...
