On 14/12/10 03:01, Jan Engelhardt wrote: > > On Thursday 2010-12-09 13:08, Pablo Neira Ayuso wrote: >> >> If we follow the one message per rule basis, you can put several >> messages into one batch with different sequence numbers. Thus, you can >> know what message in the batch has triggered the error and the reason. > > /* The unwritten laws of netlink */ > > Normally, the sequence number of a response message is simply > the one from the request message. But in a dump where there > can be multiple messages, do they all share the sequence number? Yes, because they are the result of one request. Responses use the sequence number of the original request. Thus, you can identify what messages come as part of what requests. > Must the response sequence numbers match at all, or is it like TCP > where each side has its own set? They have to match. > BTW, can response messages - all those leading up to NLMSG_DONE - > have different nlmsg_type, or not? They all have the same type. > Does the nlmsg_type need to match the request type? No. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
