Skip to main content
Best answer by brizvi_FTNT

Hi Philippe,

 

Most of the monitor pages have been moved to the dashboard and can be added as widgets. This change is mentioned in the release notes here: https://docs.fortinet.com/document/fortigate/6.4.0/fortios-release-notes/743723/new-features-or-enhancements

 

550911: Consolidate Monitor and FortiView pages.

FortiView and Monitor entries have been removed from the navigation bar. Most of the pages under them now show up as widgets in several newly added default dashboards. Exceptions being: 

- WiFi Client Monitor, which has been renamed to WiFi Clients and moved to the WiFi & Switch Controller section.

- Modem and WAN OPT pages which will still show up under Monitor if the feature is enabled.

5 replies

James_G
James_GAuthor
New Member
April 1, 2020

To my eyes the highlights are ipv4 / ipv6 feature parity finally, vrf route leaking, and device types back in the form of IOT NAC.

 

But overall, smaller change than 6.2, or 6.0 were

 

 

NeilG
NeilG
New Member
April 1, 2020

No support for 40/60/100F models I see.

 

Anyone know if that is coming?

ede_pfau
SuperUser
ede_pfau
SuperUser
April 2, 2020

Definitely.

I'm rather surprised about the 30E/50E. Ain't that old, or ill-supplied. As with any new main line, FTNT might supply those later.

btp
btp
New Member
April 7, 2020

Discovered a quite severe bug; I have a FG60E with a transparent VDOM through which I run IPTV. The STB gets it IP address from the BRAS through this VDOM. On 6.2.3 (and before) this is no problem. On 6.4.0 the STB doesn't get a response on the DHCP Discover. Tech support chat didn't know where I could report this. Anyone knows?

 

6.2.3:

vdom (TRANSP) # di sniffer packet any "port 67" 4 0 l

interfaces=[any]

filters=[port 67]

2020-04-07 21:59:06.929429 internal6 in 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:59:06.929505 IPTV out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:59:06.929518 wan1 out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:59:06.943931 IPTV in 10.184.8.1.67 -> 10.184.11.253.68: udp 370

2020-04-07 21:59:06.943987 internal6 out 10.184.8.1.67 -> 10.184.11.253.68: udp 370

 

6.4.0

vdom (TRANSP) # di sniffer packet any "port 67" 4 0 l

interfaces=[any]

filters=[port 67]

2020-04-07 21:43:17.432823 internal6 in 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:17.432882 IPTV out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:17.432891 wan1 out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:18.964584 internal6 in 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:18.964654 IPTV out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:18.964665 wan1 out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:22.470057 internal6 in 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:22.470129 IPTV out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

2020-04-07 21:43:22.470139 wan1 out 0.0.0.0.68 -> 255.255.255.255.67: udp 300

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
April 16, 2020

FYI: The beta was delayed and started on 1/30 this year according to FNDN.

tsis
tsis
New Member
April 16, 2020

Hello everyone I upgraded from 6.2.3 to 6.4 on my fortigate 61E and the wan Vlan links from the fiber provider are not connecting now to receive a public ip, reboot and factory reset to leave it clean of settings. still the same. It is not capable of receiving the public IP. through vlan, if I dowgrade to the old 6.2.3 if it works. Greetings

 

 

 

bonafide
bonafide
New Member
April 16, 2020

On my 60E, I had a VLAN attached to a hardware switch interface that was configured as a DHCP server for voip traffic, attached to a hardware switch.  This worked fine with 6.0 and 6.2, but with 6.4, the interface stopped responding to vlan tagged dhcp discovery requests from my yealink phones. Other devices on the same vlan with reserved addresses  received IP addresses, but not the phones. I ended up removing the vlan from the Fortigate and dedicating a port for untagged traffic and its working fine again.  I mention it here in case others run into dhcp / vlan issues with 6.4.

Magnitude_8
Magnitude_8
Explorer
April 30, 2020

Update: downgrading to 6.2.2 resolved the issue for me.

 

I have previously downgraded these firewalls from 6.2.3 to 6.2.2 due to other bugs. The number of bugs in new firmware seems to have increased recently. Not sure if this is generally a problem, or related to the 200E models.

Jason_Xue_FTNT
Staff
Jason_Xue_FTNT
Staff
May 1, 2020
For Andy Bailey,   Your case has been recorded in mantis 628489. Developer would like to get your input if possible:   We will review the iotd code carefully to identify the issue. However, is it possible to collect log from the "diag debug app iotd -1" when observing mem leak?   Thanks, Jason
andrewbailey
andrewbailey
New Member
May 2, 2020
JasonXue_FTNT wrote:
For Andy Bailey,   Your case has been recorded in mantis 628489. Developer would like to get your input if possible:   We will review the iotd code carefully to identify the issue. However, is it possible to collect log from the "diag debug app iotd -1" when observing mem leak?   Thanks, Jason
Hi Jason, Sure, happy to help. I’ve got a small script restarting the iotd each day- but I can stop that and let the memory use build up and pull those diag logs? What’s the best way to share the output? Kind Regards, Andy.
Jason_Xue_FTNT
Staff
Jason_Xue_FTNT
Staff
May 4, 2020

Hi Andy,

 

You can either attach the log in this post, or you can email me with the attachment: jxue@fortinet.com.

 

As long as you see the memory is up significantly, you can send the log. Then developer can take a look.

 

Thanks,

Jason

Terms & ConditionsCookie settingsAccessibility statement