Good morning everyoneWe are experiencing a strange situation. The
following is the scenario.The user connects via SSL VPN to the head
office's fortigate and then, in this connection, with the head office's
devices, the packet loss is minimal. However...
We currently have a Windows Server that not only serves AD, but also
Radius and DNS servers, where this server serves other branches, where
the FWs are connected via VPN (without significant packet loss, average
amount of 0.5%).However, in one of our...
First of all, thank you for your feedback and collaboration.Yes, I
previously tested just leaving "Traffic Shaping Profiles" on and it
didn't work, but since I needed to restrict the amount of traffic, I had
to try Traffic Shapers, but I would like t...
I was going to create basically the same topic, the Fortigate tool,
Traffic Shaping Profiles, is also not working on my firewall.These are
the configurations made: Traffic Shaping Profile Traffic Shaping Policy
IIn my case the equipment is 100F versi...
I was part of the established connection, but specifically part of the
second phase of ipsec, I created the addresses again with the option
marked as active static route.The strange thing is that both Route
Lookup and Policy Match return accepted rou...
Important informationCommunication between the head office and the
branch is normalPacket loss: acceptable, only 0.5%And communication
between the head office and the branch is carried out by 3 IPSEC
internet links using Aggregated Ipsecand both equi...
