fedora-docs-l10n/fedora-system-administrat/f30/pages/servers/Configuring_PTP_Using_ptp4l — Indonesian @ Fedora Weblate: ~]#{nbsp}dnf install linuxptp

Translation

English type: delimited block -

Indonesian

Needs editing

Skip

	English	Indonesian	Actions
	In order to use `PTP`, the kernel network driver for the intended interface has to support either software or hardware time stamping capabilities.
	Checking for Driver and Hardware Support
	In addition to hardware time stamping support being present in the driver, the NIC must also be capable of supporting this functionality in the physical hardware. The best way to verify the time stamping capabilities of a particular driver and NIC is to use the [application]ethtool utility to query the interface as follows:
	~]#{nbsp}ethtool -T em3 Time stamping parameters for em3: Capabilities: hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE) software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE) hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE) software-receive (SOF_TIMESTAMPING_RX_SOFTWARE) software-system-clock (SOF_TIMESTAMPING_SOFTWARE) hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE) PTP Hardware Clock: 0 Hardware Transmit Timestamp Modes: off (HWTSTAMP_TX_OFF) on (HWTSTAMP_TX_ON) Hardware Receive Filter Modes: none (HWTSTAMP_FILTER_NONE) all (HWTSTAMP_FILTER_ALL)
	Where _em3_ is the interface you want to check.
	For software time stamping support, the parameters list should include:
	`SOF_TIMESTAMPING_SOFTWARE`
	`SOF_TIMESTAMPING_TX_SOFTWARE`
	`SOF_TIMESTAMPING_RX_SOFTWARE`
	For hardware time stamping support, the parameters list should include:
	`SOF_TIMESTAMPING_RAW_HARDWARE`
	`SOF_TIMESTAMPING_TX_HARDWARE`
	`SOF_TIMESTAMPING_RX_HARDWARE`
	Installing PTP
	The kernel in Fedora includes support for `PTP`. User space support is provided by the tools in the [application]linuxptp package. To install [application]linuxptp, issue the following command as `root`:
	~]#{nbsp}dnf install linuxptp	~]#{nbsp}dnf install linuxptp
	This will install [application]ptp4l and [application]phc2sys.
	Do not run more than one service to set the system clock's time at the same time. If you intend to serve `PTP` time using `NTP`, see xref:Configuring_PTP_Using_ptp4l.adoc#sec-Serving_PTP_Time_with_NTP[Serving PTP Time with NTP].
	Starting ptp4l
	The [application]ptp4l program can be started from the command line or it can be started as a service. When running as a service, options are specified in the `/etc/sysconfig/ptp4l` file. Options required for use both by the service and on the command line should be specified in the `/etc/ptp4l.conf` file. The `/etc/sysconfig/ptp4l` file includes the [command]#-f /etc/ptp4l.conf# command line option, which causes the `ptp4l` program to read the `/etc/ptp4l.conf` file and process the options it contains. The use of the `/etc/ptp4l.conf` is explained in xref:Configuring_PTP_Using_ptp4l.adoc#sec-Specifying_a_Configuration_File[Specifying a Configuration File]. More information on the different [application]ptp4l options and the configuration file settings can be found in the `ptp4l(8)` man page.
	Starting ptp4l as a Service
	To start [application]ptp4l as a service, issue the following command as `root`:
	~]#{nbsp}systemctl start ptp4l	~]#{nbsp}systemctl start ptp4l
	Using ptp4l From The Command Line
	The [application]ptp4l program tries to use hardware time stamping by default. To use [application]ptp4l with hardware time stamping capable drivers and NICs, you must provide the network interface to use with the [option]`-i` option. Enter the following command as `root`:
	~]#{nbsp}ptp4l -i em3 -m
	Where _em3_ is the interface you want to configure. Below is example output from [application]ptp4l when the `PTP` clock on the NIC is synchronized to a master:
	~]#{nbsp}ptp4l -i em3 -m selected em3 as PTP clock port 1: INITIALIZING to LISTENING on INITIALIZE port 0: INITIALIZING to LISTENING on INITIALIZE port 1: new foreign master 00a069.fffe.0b552d-1 selected best master clock 00a069.fffe.0b552d port 1: LISTENING to UNCALIBRATED on RS_SLAVE master offset -23947 s0 freq +0 path delay 11350 master offset -28867 s0 freq +0 path delay 11236 master offset -32801 s0 freq +0 path delay 10841 master offset -37203 s1 freq +0 path delay 10583 master offset -7275 s2 freq -30575 path delay 10583 port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED master offset -4552 s2 freq -30035 path delay 10385
	The master offset value is the measured offset from the master in nanoseconds. The `s0`, `s1`, `s2` strings indicate the different clock servo states: `s0` is unlocked, `s1` is clock step and `s2` is locked. Once the servo is in the locked state (`s2`), the clock will not be stepped (only slowly adjusted) unless the [option]`pi_offset_const` option is set to a positive value in the configuration file (described in the `ptp4l(8)` man page). The `adj` value is the frequency adjustment of the clock in parts per billion (ppb). The path delay value is the estimated delay of the synchronization messages sent from the master in nanoseconds. Port 0 is a Unix domain socket used for local `PTP` management. Port 1 is the `em3` interface (based on the example above.) INITIALIZING, LISTENING, UNCALIBRATED and SLAVE are some of possible port states which change on the INITIALIZE, RS_SLAVE, MASTER_CLOCK_SELECTED events. In the last state change message, the port state changed from UNCALIBRATED to SLAVE indicating successful synchronization with a `PTP` master clock.
	The [application]ptp4l program can also be started as a service by running:
	When running as a service, options are specified in the `/etc/sysconfig/ptp4l` file. More information on the different [application]ptp4l options and the configuration file settings can be found in the `ptp4l(8)` man page.