On Wed, Nov 23, 2022 at 03:12:36PM +0100, Miroslav Lichvar wrote:
> This is not an issue with the protocol. As I understand it, the kernel
> will normally not send or accept a unicast packet to itself over a
> real network interface. It has the loopback interface for that.
>
> One way to get
no, i am not using hybrid_e2e option.
just two port, port 0 as master and port 1 as slave (ordinary clock mode),
and they are connected with cable.
run ptp4l on port 0 and run another ptp4l on port 1, but port 0 didn't
send delay response message.
Thanks
Alex
Miroslav Lichvar 于2022年11月23日周三
On Wed, Nov 23, 2022 at 08:41:36PM +0800, Hamilton Alex wrote:
> Hi, Miroslav:
> Thank you for your reply!
> but i didn't understand, on a single system, port 0 as master and port 1 as
> slave, and there is cable connect port 0 and port 1 for pkt communication.
> why ptp protocol doesn't work this
Hi, Miroslav:
Thank you for your reply!
but i didn't understand, on a single system, port 0 as master and port 1 as
slave, and there is cable connect port 0 and port 1 for pkt communication.
why ptp protocol doesn't work this way?
Thanks
Alex
Miroslav Lichvar 于2022年11月23日周三 16:00写道：
> On Wed,
On Wed, Nov 23, 2022 at 03:35:57PM +0800, Hamilton Alex wrote:
> so I wonder whether linuxptp can run on a single system(one CPU)?
You can have multiple ptp4l instances talking to each other on a
single system, but you need to disable the loopback shortcut between
them. The easiest way to do that
Hi, Team:
I have a network switch card, there are two ports(port 0 and port 1)
connected with cable. I run linuxptp with BC mode, set port 0 as master and
port 1 as slave (freerun mode).
I can see that port 1 received the SYNC message from port 0 and port 0
received the DelayRequest message from
