The new NAT engine in V18 provides a high degree of flexibility when it comes to solving some interesting network problems. I don't know if it has been shared here or not, but you can use NAT to achieve NTP proxy like functionality. A standard use case seen is that clients would like to use the IP address of the firewall as the NTP server. Consider this as an example environment:
There are two different approaches to a transparent NTP solution.
1.: NTP should be forwarded to a particular externally(WAN) host/host group.
2.:NTP should be forwarded to a own ressource within the network and this server should provide the information.
First scenario is rather simple.
You need one NAT Rule, which translate everything NTP based to a particular host.
You can specify all internal hosts with "Interface matching criteria - Inbound Interfaces". This example shows ANY. You can select all internal network interfaces (expect WAN).
This rule will fetch all NTP related traffic, forward it to a public NTP service and use MASQ. MASQ is required for WAN related traffic.
You need a firewall rule:
You can attach IPS rules to this, if you want.Build your own NTP rule, with all NTP related IPS pattern.
Regardless of the configured IP on a client behind Sophos Firewall, the NTP request will work.(Example: 18.104.22.168)
Second scenario needs more rules, as you can easily generate a NTP loop. Your internal server need a own NAT rule and own firewall rule. Example = Windows2016 is a NTP server.
NAT Rule 1# NTP Server to WAN (to get the NTP server to the WAN NTP servers.)You can also force the internal NTP server to get the IP from a particular NTP pool, but we assume, the NTP server has his own NTP request pool.
NAT 2# It will forward the NTP traffic transparent to the internal NTP server.
Firewall rule #1Allowing the traffic of the NTP server to the WAN to get current time.
Firewall rule #2Allowing the Traffic from all internal clients to the internal NTP server. Notice the destination zone.
Naturally, you can create variations of this NAT policy, based on your network configuration and the location of the NTP server.
In the new XG V18 architecture training course, there are a few more examples demonstrating how to control NTP and DNS traffic. I encourage you to check out the training material as it provides more in-depth knowledge of the new V18 features.
I voted, like the other 665 administrators, to implement the NTP server in the XG Firewall. Unfortunately, even though the NTP server is the second most demanded feature at the ideas.sophos…
Just updated use cases, which should reflect most common scenarios.
Hi Lucar Toni,
the following are the firewall rule and NAT rule that provide my hairpin NTP access.
The NTP server has its own firewall rule and NAT rule that are higher priority than the general LAN NTP access rules.
the XG does occasionally double NAT some of the traffic using the above rules.
Do no use ANY in your firewall destination network the XG does not like it and your connectivity will fail after some hours.