You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I unstuck my Cargo.lock while trying something else out, and wound up with the upgrade to rtnetlink 0.14.1, and netlink-packet-route 0.20. So, actually rtnetlink 0.14.1 wants netlink-packet-route 0.19, which I discovered, at which point I moved to github rtnetlink.
While there were a few deprecation notices (and I don't actually understand xfrmtun_link's third argument yet), in many cases, I just had to grep. Yes, Bridge "MASTER" now becomes Controller, but I didn't actually figure out what happens to the slave device attributes.
Please, maybe a few more comments in the code, like "// this used to be SlaveKind" or something would really help.
and at least, at this point it compiles. It does not pass tests, because my tests involve constructing netlink messages to feed into the loop that processes them, and the non_exhaustive attribute breaks that. I hope all the right ::new() methods exist.
As for Kernels that change the structure: I would suggest that rather than attempt to match every structure, that the structures maybe should just be dated or KernelVersionNumbered, with new structures created. Maybe. It's really a tuscle.
BTW: in many cases, I print any netlink message I don't understand, because sometimes they are important to process, and sometimes they are just noise. So for some things, if I don't know how to translate to new naming, I just comment out the ignore, and {:?} will print it out for me, and I'll put back the right ignores.
(This is an RFC8994 daemon, btw. It creates and lives in three network namespaces)
The text was updated successfully, but these errors were encountered:
I unstuck my Cargo.lock while trying something else out, and wound up with the upgrade to rtnetlink 0.14.1, and netlink-packet-route 0.20. So, actually rtnetlink 0.14.1 wants netlink-packet-route 0.19, which I discovered, at which point I moved to github rtnetlink.
While there were a few deprecation notices (and I don't actually understand xfrmtun_link's third argument yet), in many cases, I just had to grep. Yes, Bridge "MASTER" now becomes Controller, but I didn't actually figure out what happens to the slave device attributes.
Please, maybe a few more comments in the code, like "// this used to be SlaveKind" or something would really help.
Anyway, I gathered it all together as:
AnimaGUS-minerva/connect@9279594
and at least, at this point it compiles. It does not pass tests, because my tests involve constructing netlink messages to feed into the loop that processes them, and the non_exhaustive attribute breaks that. I hope all the right ::new() methods exist.
As for Kernels that change the structure: I would suggest that rather than attempt to match every structure, that the structures maybe should just be dated or KernelVersionNumbered, with new structures created. Maybe. It's really a tuscle.
BTW: in many cases, I print any netlink message I don't understand, because sometimes they are important to process, and sometimes they are just noise. So for some things, if I don't know how to translate to new naming, I just comment out the ignore, and {:?} will print it out for me, and I'll put back the right ignores.
(This is an RFC8994 daemon, btw. It creates and lives in three network namespaces)
The text was updated successfully, but these errors were encountered: