0deb984fd7
When tc rule is created via Netlink message application
can provide the unique rule value which can be accepted
by the kernel. Than rule is managed with this assigned
handle. It was found that kernel can reject the proposed
handle and assign its own handle value, the rule control
is lost, because application uses its initially prorosed
rule handle and knows nothing about handle been repleced.
The kernel can assign handle automatically, the application
can get the assigned handle value by specifying NLM_F_ECHO
flag in Netlink message when rule is being created. The
kernel sends back the full descriptor of rule and handle
can be retrieved from and stored by application for further
rule management.
Fixes:
|
||
|---|---|---|
| .. | ||
| baseband | ||
| bus | ||
| common | ||
| compress | ||
| crypto | ||
| event | ||
| mempool | ||
| net | ||
| raw | ||
| Makefile | ||
| meson.build | ||