Thanks Sergei for the input.
> On Jun 18, 2019, at 2:28 AM, Sergei Shtylyov
> wrote:
>
> Hello!
>
> On 17.06.2019 22:31, Vedang Patel wrote:
>
>> Currently, etf expects a socket with SO_TXTIME option set for each packet
>> it encounters. So, it will drop all other packets. But, in the future
Hello!
On 17.06.2019 22:31, Vedang Patel wrote:
Currently, etf expects a socket with SO_TXTIME option set for each packet
it encounters. So, it will drop all other packets. But, in the future
commits we are planning to add functionality which where tstamp value will
be set by another qdisc. Als
Currently, etf expects a socket with SO_TXTIME option set for each packet
it encounters. So, it will drop all other packets. But, in the future
commits we are planning to add functionality which where tstamp value will
be set by another qdisc. Also, some packets which are generated from within
the