In version 6.2 I know the PIX supports ntp as a client but I don't think as a server (see http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_62/cmdref/mr.htm#xtocid7). NTP uses port 123. I believe the client starts the ntp connection with the ntp server, so the PIX can allow your internal clients to communicate with the NTP server without having to create an acl. If I am wrong, and you need an acl, put a server on the DMZ, sync with the internet NTP server that way, and allow your inside devices to sync with the DMZ ntp server.
If you have any internal acls, only allow that internal ntp server to communicate with others via ntp, and lock that server down (not a server guy anymore so can't help with that). If it's a router, have an acl on it only allow the public ntp server to access it via ntp. Not much else you can do if you are stuck with direct external to internal.
An NTP client initiates all communications to servers and even to peers. There is no server push. If you are syncing to outside sources, you will only need an acl if you are restricing outbound traffic.
Most routine NTP traffic is UDP. Only some interactive traffic, like ntpq queries, are TCP, so you generally only have to allow UDP.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...