|
Create Virtual IPs to enable port forwarding:
To forward TCP or UDP ports received by the FortiGate external interface to an internal server, follow two steps:
- Create a Virtual IP and enable Port Forwarding.
- Create a firewall policy and add the Virtual IP.
This example describes how to configure port forwarding to allow RDP access to an internal server on port 3389.
To add a virtual IP that forwards RDP packets, follow the steps below.
- For v6.0.x, v6.2.x, v7.0.x, v7.2.x, v7.4.x, v7.6.x navigate to Policy & Objects -> Virtual IPs.
- Select Create New.
- Add a name for the virtual IP.
- Select the External Interface. This will typically be the interface that connects the FortiGate to the Internet. (Can leave as 'any').
- Set the External IP Address/Range. The following can be used:
- The FortiGate unit public IP.
- If there is a cable or DSL connection with a dynamic IP, it is possible to use 0.0.0.0. (Cannot user 0.0.0.0 when interface is 'any').
- If the ISP provides a block of IPs that route to the FortiGate external interface, it is possible to add one of these IPs here.
- Set the Mapped IP Address to the internal IP address of the server.
- Select Port Forwarding.
- Set the protocol to TCP.
- Set External Service Port and Map to Port. For this example, the RDP service uses port 3389. Set both External service port and Map to Port to 3389.
- Select OK.
After, all that remains is to define a firewall policy that accepts RDP traffic from the Internet and forwards it to the internal server.
To add a firewall policy with a virtual IP:
- In v6.0, Go to Policy & Objects -> IPv4 Policy. In v6.4.x, v7.0.x, v7.2.x, v7.4.x, v7.6.x Navigate to Policy & Objects => Firewall Policy.
- Select Create New.
- Set Source Interface to the WAN/Internet interface.
- Set Source Addresses to all.
- Set Destination Interface to internal.
- Set the Destination Address to the name of the Virtual IP created previously.
- Usually, the remainder of the options in this firewall policy does not need to be changed. For example, the Service can remain as ANY, because the virtual IP only forwards packets using port 3389. NAT can be enabled or disabled based on the network requirements. Some servers might not respond to RDP connection from a different network due to Windows/host-based firewall. NAT must be enabled in these cases.
- Select OK.
Note:
If the 'External service port' and 'Map to IPv4 port' are different, both ports must be specified in the 'Service' field of the firewall policy (if it is not set to 'any').
 
To configure the Port Forwarding via CLI:
config firewall vip
edit "Test"
set extip 20.20.20.20
set mappedip "192.168.3.3"
set extintf "any"
set portforward enable
set extport 11111
set mappedport 3389
next
end
To verify traffic hitting and using the correct policy, the below debugs can be used:
Packet Sniffer:
diag sniffer packet any ' host a.a.a.a and port bb ' 4 0 l <----- <a.a.a.a is the source IP and port bb is the NAT port>.
Debug Flow:
diagnose debug disable
diagnose debug flow trace stop
diagnose debug flow filter clear
diagnose debug reset
diagnose debug flow filter addr x.x.x.x <----- x.x.x.x is the src IP.
diag deb fl sh ip en
diagnose debug flow show function-name enable
diagnose debug console timestamp enable
diagnose debug flow trace start 999
diagnose debug enable
|
