Byte order for conntrack fields over netlink

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi netfilter team,

Why are all conntrack related fields converted from host to network
byte order by kernel before sending it to userspace over netlink and
again from network to host by
conntrack tools ( even though most fields are not related to network)?
I am referring to packet exchange during commands e.g. conntrack -L
etc.

Is there any good reason for these conversions?

I was assuming that the kernel will send all non network related
fields in host byte order but that is not the case here.

Vimal




[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux