I could figure a problem with spinfo_state between Linux and FreeBSD
sctp stack.
While in linux stack the return value of spinfo_state is defined as
enum with four items, FreeBSD defines a lot more states. The problem
is that these values do not match with each other. For example if
FreeBSD means INACTIVE this value in linux results in UNCONFIRMED.
In sctp socket api these states are namely defined but not assoziated
with any value.
Is there any possibility to standardize these values ??
Regards,
Schoch Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
