| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
This pertains mostly to FILES, HISTORY, EXIT STATUS and AUTHORS sections.
Found by: mdocml lint run
Reviewed by: ru
|
| |
|
|
|
|
|
|
|
|
|
|
| |
values like 0x80 or 0x40 into a uint8_t foo:1 bitfield. This would
result in the bit always being 0. One of these caused a warning for
overflow (one that was 0x80), but the other didn't. They were both
wrong.
This is why I hate code that mixes c struct bitfields and #defines.
The rest of the fields accessed by the program should be audited.
|
|
|
|
|
|
|
|
| |
- convert to .Ex macro
- not bumping a date as this is not a real content change
Approved by: ru [1]
MFC after: 3 days
|
|
|
|
|
|
| |
OpenBSD does, since modulo is not power of 2.
Obtained from: OpenBSD
|
| |
|
|
|
|
| |
Obtained from: Slava Semushin via NetBSD
|
|
|
|
| |
Tested with: cmp(1)
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 day
|
| |
|
|
|
|
|
|
| |
Obtained from: KAME
Reviewd by: ume, gnn
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
because rs_input() need this option.
Obtained from: KAME
Reviewed by: ume, gnn
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
NDP-related kernel variables based on their configurations (RFC2461 p.43 6.2.1 mandates this for IPv6 routers)
Obtained from: KAME
Reviewd by: ume, gnn
MFC after: 2 weeks
|
|
|
|
|
| |
Submitted by: suz
Obtained from: KAME
|
| |
|
|
|
|
| |
PR: bin/71624
|
|
|
|
| |
(with permission of addtional copyright holders where appropriate)
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained From: KAME
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- deprecate routes#N, as it is hard to keep consistency with
rtprefixN. accept any number of "rtprefix", "rtrefix0",
..., "rtprefix99".
- deprecate "addrs#N", as it is difficult for users to keep
consistency with "addrN".
accept 100 prefix info in maximum - like "addr", "addr0"
... "addr99". WARNS=2 clean on netbsd.
old configuration file should work just fine.
behavior change:
previously, we rejected "addrN" if there's "addr", and we rejected
"addr" if there is "addrN". now we accept both without problem.
- when an advertised prefix configured from the kernel has been added
or invalidated, notice the change in a short delay.
- when invalidating a prefix, do not bark even if there is
inconsistency about prefix lifetimes.
- wrap more specific route info code into ROUTEINFO.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
| |
(otherwise file descriptors could be closed mistakenly)
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
| |
- remove unused block.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 day
|
|
|
|
|
|
|
| |
- corrected wording in a log message.
Obtained from: KAME
MFC after: 1 week
|
|
|
|
| |
No response from: suz
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
| |
Submitted by: jinmei@kame.net (JINMEI Tatuya)
Obtained from: KAME
|
| |
|