| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Obtained from: KAME
Reported in: freebsd-net@freebsd
MFC after: 1 day
|
|
|
|
|
| |
Submitted by: max
MFC after: 2 month
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- introduced fine-grain-timer to manage ND-caches and IPv6 Multicast-Listeners
- supports Router-Preference <draft-ietf-ipv6-router-selection-07.txt>
- better prefix lifetime management
- more spec-comformant DAD advertisement
- updated RFC/internet-draft revisions
Obtained from: KAME
Reviewed by: ume, gnn
MFC after: 2 month
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
| |
Obtained from: KAME
Reviewed by: ume, gnn
|
|
|
|
|
| |
Obtained from: KAME
Reviewd by: ume, gnn
|
|
|
|
|
|
|
|
|
| |
- disable IPv6 operation if DAD fails for some EUI-64 link-local addresses.
- export get_hw_ifid() (and rename it) as a subroutine for this process.
Obtained from: KAME
Reviewd by: ume, gnn
MFC after: 2 week
|
|
|
|
|
| |
Obtained from: KAME
Reviewed by: ume, gnn
|
|
|
|
|
|
| |
Obtained from: KAME
Reviewd by: ume, gnn
MFC after: 2 week
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
- fixed typos
- improved some comment descriptions
- use NULL, instead of 0, to denote a NULL pointer
- avoid embedding a magic number in the code
- use nd6log() instead of log() to record NDP-specific logs
- nuked an unnecessay white space
Obtained from: KAME
MFC after: 1 day
|
|
|
|
|
|
|
| |
of the first next-header value.
Obtained from: KAME
MFC after: 1 day
|
|
|
|
|
|
|
| |
message is received
Obtained from: KAME
MFC After: 3 days
|
|
|
|
|
| |
Submitted by: JINMEI Tatuya
MFC After: 1 day
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
| |
for rt->rt_rmx.rmx_expire.
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 day
|
|
|
|
|
| |
M_IPMOPTS, M_MRTABLE). Thus we had conflicting instantiations.
Create an IPv6-specific type to overcome this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
assigned to the interface.
IPv6 auto-configuration is disabled. An IPv6 link-local address has a
link-local scope within one link, the spec is unclear for the bridge case and
it may cause scope violation.
An address can be assigned in the usual way;
ifconfig bridge0 inet6 xxxx:...
Tested by: bmah
Reviewed by: ume (netinet6)
Approved by: mlaier (mentor)
MFC after: 1 week
|
| |
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 3 days
|
|
|
|
|
|
| |
- use TAILQ_FOREACH() for readability.
Suggested by: jhb
|
| |
|
|
|
|
|
|
|
| |
(by default, it is disabled)
Submitted by: suz
Obtained from: KAME
|
|
|
|
|
|
|
| |
- nuke unused code.
Submitted by: suz
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
| |
- rt0 passed to rt_check() must not be NULL, assert this.
- rt returned by rt_check() must be valid locked rtentry,
if no error occured.
o Modify callers, so that they never pass NULL rt0
to rt_check().
Reviewed by: sam, ume (nd6.c)
|
|
|
|
|
|
| |
net.inet6.ip6.fw with upcomming ipfw2 improvement for IPv6.
Requested by: bz
|
|
|
|
|
|
|
| |
code was #ifdef'ed out for a long time.
Submitted by: suz
Obtained from: KAME
|
|
|
|
|
| |
PR: kern/54625
MFC after: 1 week
|
|
|
|
| |
made static.
|
| |
|
|
|
|
|
|
| |
(e.g. pim6dd, pim6sd)
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
IFF_DRV_RUNNING, as well as the move from ifnet.if_flags to
ifnet.if_drv_flags. Device drivers are now responsible for
synchronizing access to these flags, as they are in if_drv_flags. This
helps prevent races between the network stack and device driver in
maintaining the interface flags field.
Many __FreeBSD__ and __FreeBSD_version checks maintained and continued;
some less so.
Reviewed by: pjd, bz
MFC after: 7 days
|
|
|
|
| |
L2/L3 mappings) make rt_check() return a locked rtentry.
|
|
|
|
|
|
|
|
| |
- Push 'i' into the only block where it is used.
- Remove redundant check for rt being NULL. If rt_check() hasn't
returned an error, then rt is valid.
Reviewed by: gnn
|
|
|
|
|
|
|
| |
to lock if_addr_mtx.
Problem reported by: Ed Maste <emaste at phaedrus dot sandvine dot ca>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
too much even though we actually validate the parameters. This code
also is more compatible with other *BSDs, which do copyin within
setsockopt().
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Reviewed by: security-officer (nectar)
Obtained from: KAME
|
|
|
|
|
|
|
|
|
| |
carefully crafted deflated data stream. [1]
Correct problems in the AES-XCBC-MAC IPsec authentication algorithm. [2]
Submitted by: suz [2]
Security: FreeBSD-SA-05:18.zlib [1], FreeBSD-SA-05:19.ipsec [2]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- most of the kernel code will not care about the actual encoding of
scope zone IDs and won't touch "s6_addr16[1]" directly.
- similarly, most of the kernel code will not care about link-local
scoped addresses as a special case.
- scope boundary check will be stricter. For example, the current
*BSD code allows a packet with src=::1 and dst=(some global IPv6
address) to be sent outside of the node, if the application do:
s = socket(AF_INET6);
bind(s, "::1");
sendto(s, some_global_IPv6_addr);
This is clearly wrong, since ::1 is only meaningful within a single
node, but the current implementation of the *BSD kernel cannot
reject this attempt.
Submitted by: JINMEI Tatuya <jinmei__at__isl.rdc.toshiba.co.jp>
Obtained from: KAME
|
|
|
|
|
|
|
| |
argument/structure member accordingly.
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
| |
in6p_outputopts at the entrance of the functions. this trick was
necessary when we passed an in6 pcb to in6_embedscope(), within which
the in6p_outputopts member was used, but we do not use this kind of
interface any more.
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
| |
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
| |
Submitted by: Keiichi SHIMA <keiichi__at__iijlab.net>
Obtained from: KAME
|
|
|
|
|
|
|
| |
they need special handling. makes it possible to take advantage of 9k ether
frames.
Obtained from: NetBSD
|