Today
Causes a panic. Abandoning.
I think we should probably have tests check we do the correct things when we get a jumbogram. If these tests aren't run they don't really help with that.
LGTM. Feel free to commit.
Hi Adrian,
Isaac, let me know if you want to take over maintainership of this port for the long run. But if not, I'd be interested in keeping it going on the FreeBSD ports side.
This time for sure!
Further error message refinement.
I'd suggest to use more specific commit line, e.g. ndp: handle a case when two timers coalesce for the same ifa. Or something else that you can come up with. Just more specific than "make things better" :)
Continue the WIP.
Handle NMIs and #MC.
Misc bug fixes.
Yesterday
Add sx(9) and rmlock(9) support.
Fix a minor issue on PATH_MASK.
Reuse ndq and cancel out previous pending NA for same ifa.
@glebius done.
i wonder: why is this in base, when pkg repository can only be built when pkg(8) is installed?
This is the commit message.
Do you need to validate the enum value is know?
I'll see if rmlock(9) and sx(9) can be added and update.
This is really clever. What about other lock types (rm / rms, sx, etc)?
Don't count for grand for delayed solicited NAs.
Valid complaint, but not sure what the error message should be for the third case.
Panel Used By
| Dashboard | acidburn0_live.be's Dashboard |