Re: [Linuxptp-users] Linuxptp - Supported Hardware

2023-09-26 Thread Richard Cochran
On Mon, Sep 25, 2023 at 02:36:35PM +0100, Fernando Gomes wrote:

> Is there a list of hardware that can be used with linuxptp to do
> timestamping at the hardware level (on PHY or on MAC)? There are some phys
> that support it, like the Vitesse / Microchip, etc., but is there a
> compatibility list available?

I used to maintain a list of hardware, but I gave that up years ago
when the number of products became too large.  Nowadays most new MACs
have PTP support.

The easiest way to find out your MAC's capabilities is:

ethtool -T eth0

For PHYs, the main issue is that the Linux networking stack doesn't
treat MACs and PHYs equally.  If you really need to use a PTP PHY,
then you will likely have to configure and even patch your kernel
specifically for your hardware.

HTH,
Richard


___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users


[Linuxptp-users] PTP client selecting source IP address when NIC configured for multiple IPs

2023-09-26 Thread David Turrie via Linuxptp-users
Hello,

Use Case: Our application is running in a N:1 redundancy configuration.  Each 
primary server is configured with a "real" IP address and a virtual IP address. 
The backup is configured with a real IP address only.  The real IP address is 
intended for communications to the server regardless of its state (active or 
inactive); the virtual IP address is assigned to the server when it is active 
only.   Besides management protocols, it is desired for PTP to use the real IP 
address in order to reduce impact to the grandmaster when the primary server 
changes its state from active to inactive (Failover) or inactive to active 
(Recovery).   When the interface is assigned an IPv4 address, PTP uses the real 
IP address. When IPv6, PTP uses the virtual IP address.   Our customer is using 
IPv6 and wants the real IP to be used.  We suspect that without PTP specifying, 
Linux (RHEL9) is choosing the source IP in an indiscriminate manner.  We could 
not find a PTP configuration to choose the source IP when using unicast to 
communicate to the master.

Requests: I am seeking confirmation that linuxPTP does not allow the user to 
specify the slave's source IP for unicast communications.  And second, if this 
is something the PTP development community would consider adding to PTP 
configuration.

Thanks
David Turrie


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, 
please notify the sender immediately and delete this message and any attachment 
from your system. Do not copy them or disclose the contents to any other person.
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users