Up to [cvs.NetBSD.org] / src / sys / netinet
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: rpaulo-netinet-merge-pcb
Revision 184.108.40.206 / (download) - annotate - [select for diffs], Sat Sep 9 02:58:47 2006 UTC (8 years, 5 months ago) by rpaulo
Changes since 220.127.116.11: +12 -13 lines
Diff to previous 18.104.22.168 (colored) next main 1.147 (colored)
sync with head
Revision 22.214.171.124 / (download) - annotate - [select for diffs], Tue Feb 7 04:51:49 2006 UTC (9 years ago) by rpaulo
Changes since 126.96.36.199: +21 -25 lines
Diff to previous 188.8.131.52 (colored)
in6pcb -> inpcb.
Revision 184.108.40.206 / (download) - annotate - [select for diffs], Sun Feb 5 03:09:11 2006 UTC (9 years ago) by rpaulo
Changes since 1.146: +2 -3 lines
Diff to previous 1.146 (colored)
<netinet6/in6_pcb.h> went away. Bye!
Revision 1.146 / (download) - annotate - [select for diffs], Sat Jan 21 00:15:36 2006 UTC (9 years, 1 month ago) by rpaulo
Branch point for: simonb-timecounters, rpaulo-netinet-merge-pcb
Changes since 1.145: +20 -16 lines
Diff to previous 1.145 (colored)
Better support of IPv6 scoped addresses. - most of the kernel code will not care about the actual encoding of scope zone IDs and won't touch "s6_addr16" 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. - and, while there, don't try to remove the ff02::/32 interface route entry in in6_ifdetach() as it's already gone. This also includes some level of support for the standard source address selection algorithm defined in RFC3484, which will be completed on in the future. From the KAME project via JINMEI Tatuya. Approved by core@.
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.