We've got some development that's going on in Azure which makes a call
to our internal servers. I've got the "source" inbound rule pointing to
a VIP and restricted to traffic coming from
*.azure-api.net*.microsoft.com*.slope.ioThe problem is with som...
I'm trying to lock down some of my web rules. The issue is many of the
server owners don't understand what web access they "need" so I resort
to turning on full logging. I put a more restrictive rule above the less
restrictive rule, and check the log...
We already have a FortiNet in place with "outbound" policies pointing to
WAN1 because we were going to use an ISP aggregator in front of the
FortiNet. Now things have changed and management no longer wants to use
the ISP aggregator and use the built ...
Short version of the story, I've got an external SDWAN provider but
traffic through the SDWAN provider is doubling my ping latency. The
provider says it's a routing issue that's outside of their control and
they've submitted a ticket but if or when t...
I'm following the directions found
herehttps://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-block-iCloud-Private-Relay-from-bypassing/ta-p/228629Which
are supposed to allow you to block the iCloud private relay but in a
somewhat graceful ...
I don't think we plan to NOT have FortiCare, but it's good to know.
Thanks so much for this! I never used it, didn't know it existed, but
it's going to make a life a lot easier! 10 points too !
I've never used this feature before! This is kind of awesome. Doing some
research it looks like you could look up the service via a CLI
commanddiagnose internet-service match
IEdiagnose internet-service match root 20.121.82.216
255.255.255.255which...
Oh, I'd not thought of that. Where does that end up in logs? Is that
under a specific location or does it still end up under the "show
matching logs" when you right click on a rule?
