- User Since
- Aug 29 2014, 12:11 PM (275 w, 3 d)
Fri, Dec 6
I'l split this up into a couple of chunks so we can more easily do the base infrastructure for the llatbl changes for IPv6 and the IPv4.
The rtr and prefix parts are unrelated to that.
Tue, Dec 3
In case I don't hear from you I'll go ahead and commit this the next days.
Mon, Dec 2
Thanks a lot for the feedback. let me know what you think about the suggestion to move the basic functionality into llatbl?
Address variable naming.
Address conditional checks.
Sun, Dec 1
Mon, Nov 25
Ignoring the one maximum value, is anyone interest in actually reviewing this?
Sun, Nov 24
inet_pton() stroes network byte order, so lose the original (now extra)
htonl() and unbreak IPv4 support.
Fri, Nov 22
Thu, Nov 21
Wed, Nov 20
Tue, Nov 19
Approved by: bz (co-mentor)
Address kp's catch of the SYSCTL_OPAQUE size.
Mon, Nov 18
Sat, Nov 16
Fri, Nov 15
Thanks a lot for reviewing! Much appreciated!
Wed, Nov 13
Tue, Nov 12
Rename FOO_<> to FOO.<> as requested by @imp.
Mon, Nov 11
libkvm does know about VNETs (see kvm_private.c / kvm_vnet.c) as much as it knows about DPCPU. I seem to remember however it needs something selected, such as a PID or curthread from the dump, as it gets VNET information from there. This is probably something that should be generally fixed for netstat and not just for mrouting, though I am sure I tested that on a core dump back then. People may have broken it or the netstat parts were never merged.
Sat, Nov 9
Nov 8 2019
Nov 7 2019
I'd like to commit the main part of the change with(out) the two changes I commented on the next 24 hours.
Does anyone want to have a look?
Nov 6 2019
Nov 5 2019
Nov 4 2019
In general I really like the changes. I've not looked into the large chunks of sysctls / UDP / TCP in too much detail. I'll try to do them based on their individual git changes the next days (at least sysctl and UDP). Hope someone else will do the TCP bits.
Oct 30 2019
All your "stub functions" return (0), when in fact they probably should return an error? Or what happens if someone tries to set a (hw)breakpoint on these architectures?