I just ran into this: We have a Windows DHCP that has a scope for a
vlan.the vlan interface on the FGT100E is set to do dhcp relaying to
this Windows DHCP.the Windows DHCP also has dhcp option 138 set for all
scopes it has.If I now connect a client t...
I did the following: - upgraded FMG to 7.0.11 while the FGT still were
on 7.0.13 => everything still worked fine afterwards- upgraded the FGT
to 7.0.14 during the next night (scheduled) => since then FGT keep
losing the connection to FMG when I deplo...
We just ran into this: today our FortiMail states it has no antispam and
virus outbreak license.It did have one because it also states the last
update of the antispam definitions was on 2024-02-06 and it cannot do
that without vallid license. If I lo...
We just ran into this issue and I just wanted to warn you to not do so
too: if you rename global address objects in FMG you can only do that
via script (TAC said this).If you assign this to an adom afterwards it
will be correctly assigned.You will ha...
I keep encountering this behavior: all of a sudden on some clients https
websites stop working.every time this starts the only thing noticable on
the FGT is that the memory usage is >=60%. Mostly around 63-65%. It
however does not reach the threshold...
caveat: when you create interfaces for site B Subnets on Site A this
also creates static (connected) routing which will mean that you can no
longer route that to site B!So might be better to use some lab
environment that is behind NAT or similar to a...
The biggest thing with this is that the usuall FGFM Debuglogs don't show
you the actual certificate.It just reports the CAs and the error
itself.Only the last interim build reported the actuall certificate.
Accoardng to your screenshots on FortiGate Side you alreaday created a
trunk on Port2 (LAN) which has the two Vlans and port2 itself. This
means traffic that hits the FGT and has a vid of one of the two vlans
will be hitting that vlan interface any o...
I also see that before the sensors go off there is an I2C EEPROM write
error. That looks indeed like if something on your FGT's mainboard got
fried eve though PSUs seem to be still good. I would also advice
contactig customer support for a RMA!
either do not enable it on policies for the FMG<->FGT connection or make
sure that all FGT have the issuer ca you use for deep inspection so they
can still verify FMG's certificate.