Hi there!We are installing a new Fortigate 60F. It will be quite a basic
configuration, we have 3 VLAN defined in a VLAN switch attached to a L2
switch port in trunk/tagged mode and have created several policy rules
to allow traffic between them (wor...
Hi @hbac:NAT on this policies is messing things: On 21/6 I posted: Hi
again. We found out that when we configure the policy rule with NAT
enabled, we can see al devices in the VLAN Est (not only those connected
directly to FG). Same applies to other ...
Hi @Pittstate.NAT is not enabled on the SSLVPN - VLAN policies. I posted
a few days ago, that if we enable NAT on this rules, we see al devices
in the LAN, but somehow (probably NAT issue) internal servers (e.g.
Exchange) can't reach Internet. Regard...
Hi @Pittstate, thanks again for your response.Yes, we have the reverse
rules defined (not triggering though...) In the previous trace, I don't
really understand this messages:checked gnum-4e20 policy-6,
ret-no-match, act-acceptPolicy 6 is disabled an...
Hi @Pittstate.I checked the Debug Flow, but I only get sent packets
matching a policy:24/06/2024 9:55vd-root:0 received a packet(proto=1,
172.120.0.1:1->10.1.1.6:2048) tun_id=0.0.0.0 from ssl.root. type=8,
code=0, id=1, seq=293.24/06/2024 9:55allocat...
Hi @hbac. Thanks for your response.Yes, we have all other policies
defined. I just posted one example, but all of them are on the same
situation regarding the visibility to other hosts in their own VLAN. BR
