DHCPv6 prefix delegation (266061)
Prefix delegation is now support for DHCP for IPv6 addressing. It is not practical to manually provision networks on a large scale in IPv6 networking. The DHCPv6 prefix delegation feature is used to assign a network address prefix, and automate the configuration and provisioning of the public routable addresses for the network.
Enabling the prefix delegation is done only in the CLI as in the following example:
config system interface edit “wan1”
config ipv6
set ip6-mode dhcp
set ip6-allowaccess ping
set dhcp6-prefix-delegation enable end
end
Proxy–arp extensions (250651)
The proxy-arp configuration can be extendend to an IP address range rather than a single IP address. A new setting has been added to the CLI. When configuring the proxy-arp, in addtion to setting the IP address, an end-ip address can also be set. If it is not set, the proxy-arp will be a single address as before. An example configuration using the new setting would be a follows:
config system proxy-arp edit 1
set interface “internal” set ip 192.168.1.100
set end-ip 192.168.1.102 end
Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!
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.