HiI'm trying to figure out why my transparent proxy policies are
allowing traffic when they shouldn't. I have a transparent proxy policy
restricted to a single IP and FSSO group for testing, yet when I disable
the policy, the test device/user still h...
Hi We've been having spotty internet connectivity since adding a 4G
interface ( a Teltonika device in pass-through mode) to the SD-WAN on
our 200E running 7.2.10. The three fibre interfaces in the SD-WAN are
only running 20-30 % utilization generally...
HiYesterday I had to disable full SSL inspection in our proxy policies
due to poor browsing performance. Fortigate 200E running 7.0.15 No
policy changes were made, and user numbers, session numbers and
interface throughput are average for daily use. ...
Hi We have a SSLVPN Web portal on one Fortigate. When using it to get to
resources behind a tunnel on another Fortigate, it seems to NAT the
traffic despite the policy having NAT turned off. FG2 sees the source
address of traffic to AWS being 192.168...
Hi I'm using a Teltonika RUT240 in passthrough mode to add 4G to a
Fortigate 60E running 7.0.12. It seems to work well enough, and the
Forti interface connected to the Teltonika gets its public IP. The idea
is to create a second IPsec tunnel on the 4...
OK, then they're definitely be homogenous.Yeah, the 4G performance is
rubbish compared to the fibre connections. I can use the poor latency in
the performance SLA threshold to keep it unused except as a last resort.
Thanks Toshi :)
Unfortunately nothing was revealed looking at the crash log.I upgraded
the firmware to the Fortinet recommended version, 7.2.7, and the problem
has resolved itself. Thanks for taking the time to reply, I appreciate
it.
Edited: Looks like this is expected behavior for web SSLVPN. "The source
IP address used by the FortiGate when accessing SSL VPN Web Portal
bookmarks is the IP address configured for the outgoing interface
specified in the SSL VPN security policy."
h...
