RFC support added in FortiOS 5.4
The following RFCs are now supported by FortiOS 5.4:
RFC 2231 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations (280039)
Improve support for RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE) (213945) RFC 4106 The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP) RFC 4273 Definitions of Managed Objects for BGP-4 (168927)
RFC 4303 IP Encapsulating Security Payload (ESP) (255144)
RFC 4304 Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet
Security Association and Key Management Protocol (ISAKMP)
RFC 4478 Repeated Authentication in Internet Key Exchange (IKEv2) Protocol (282025)
RFC 4750 OSPF Version 2 Management Information Base (168927)
RFC 4754 IKE and IKEv2 Authentication Using the Elliptic Curve Digital Signature Algorithm (ECDSA) (0206110) RFC 5176 Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) (239028) RFC 5177 Network Mobility (NEMO) Extensions for Mobile IPv4 (249570)
RFC 5643 Management Information Base for OSPFv3 (168927)
RFC 5723 Internet Key Exchange Protocol Version 2 (IKEv2) Session Resumption (289914)
RFC 5996 Internet Key Exchange Protocol Version 2 (IKEv2) (255144)
RFC 6106 IPv6 Router Advertisement Options for DNS Configuration (266061)
RFC 6290 A Quick Crash Detection Method for the Internet Key Exchange Protocol (IKE) (298970)
RFC 6888 Common Requirements for Carrier-Grade NATs (CGNs)
RFC 7539 ChaCha20 and Poly1305 for IETF Protocols (264785)
I’m running FortiOS 5.6.7 on FG-1500D’s. We have virtual wire pairs set up for our VDOM’s that run in transparent mode, with no port channeling. One of the SFP’s is twinax (connecting to a Cisco Firepower) and the other is fiber (going into a Cisco switch). Does that cause issues, or is the Fortigate OK with media not being exactly the same on both ports?
I like to keep things identical for standardization sake. It won’t break anything though.