Features that you would like to see

Description for DHCP reservations

sms collection for guest

I would love so see hardware modules to add directly a VDSL2 modem for example to the box so I do not need a DSL router in front anymore. That' s one of they main reasons why enterprise customers buy the Juniper SRX instead of a Fortigate. That would be awesome.

For the SIP ALG feature, the opportunity to preserve the original source IP address in the Viaheader in a SIP message

If we think on the NSA - it would be great if Fortinet would support some less widespread encryption protocols for VPN. Between Fortigate units and FortiClient it would work fine and that' s okay. I believe, the NSA is trained to crack AES, DES, SSL and other common cryptographic protocols day by day. But if we could use something different - maybe developed in-house by fortinet for example - thy would have a lot more trouble to decrypt that, because it' s not that common. THAT would be outstanding in the market. For interoperation with other vendors, fortunate customers could use AES as well of course but within the Fortinet eco system it would be great to have alternatives. Maybe with an open API so that it is easy so implement new cryptographic protocols if necessary of when the customer has the necessary manpower and knowledge.

I' d like to see the ability to specificy Subnets or incoming interfaces that alwasy represent " On Net" for FCT registration. Right now if there is another L3 device between the FGT and the client they show up as " off net"

I would like to see more functions in the DLP module, it is pretty simple in my opinion

This is not so much re. a new feature but rather a cry for the old one... Traffic History is a nice little widget which many of us regularly use. Before FortiOS 5.X inbound and outbound traffic for an interface overlapped on the same reference frame, which was nice: In and Out traffic were drawn with different colors, scale was twice as higher (in comparison to what we see starting from v5.X: In and Out traffic are now drawn on their own frame of axis), you could have detached widget into a separate window for improved visibility or printing purposes and it was much easier to correlate inbound and outbound traffic. Traffic History widget' s implementation in 5.X is not as good as it used to be. It would be nice to get old one back.

I would like to see functionality ( do not resolve DNS query if IP adress is from botnet ip adress space) like it ofer www.nominum.com It will greatly improve sales of your equipment.

today the load-balancing feature is doing a source NAT. We need the original source IP for balancing SMTP. right now no graylisting is working because every connection has the same source IP. For http you cat activate inserting source IP as a http header field... And please add an iPv6 version of load-balancing, too; with keping the source IPv6 address