| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
0fa3641706 |
MT#55283 report netlink errors by seq num
Not 100% sure if this is how it's intended to be handled, as the failed requests seem to produce multiple ACK messages, but at least this fixes the immediate problem of the printed error message not matching the request which failed. Closes #2041 Change-Id: I2a6bf57ce996c134b44d4f3484164a39c68fc93c |
3 weeks ago |
|
|
d891145474 |
MT#55283 add sequencing to netlink messages
Change-Id: I6346c79a204d0ee1f7587676848cdcfca7055262 |
3 weeks ago |
|
|
b833a39198 |
MT#55283 print readable msg for netlink errors
closes #2039 Change-Id: If6c16d29482f16ed57b9059f3c13b23520b74cab |
4 weeks ago |
|
|
5dcc70c240 |
MT#55283 track human readable messages
Change-Id: I53380194d66591ada7bf48bca3cae5a933eabc79 |
4 weeks ago |
|
|
09be6451d5 |
MT#55283 replace linmnl/libnftnl usage
Change-Id: I42c64bf9b4cc78835f98030b540c982bf70b8b8b |
1 month ago |
|
|
0ed79a2f0f |
MT#55283 add hand-rolled netlink layer
Change-Id: I3af7dcf0ed109db984c7eafca260eff89ec2b852 |
1 month ago |