FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F9.3.0 2012-01-07T11:01:35Z 2012-01-07T11:01:35Z Gleb Smirnoff glebius@FreeBSD.org 2012-01-07T11:01:35Z urn:sha1:b03b6e622b513c86a8ac09f819271d606b10ccc9 r228732 | glebius | 2011-12-20 16:34:16 +0400 (вт, 20 дек 2011) | 3 lines - Cover pfsync callouts deletion with PF_LOCK(). - Cover setting up interface between pf and pfsync with PF_LOCK(). r228811 | glebius | 2011-12-22 22:31:47 +0400 (чт, 22 дек 2011) | 3 lines In FreeBSD we always have bpf(4) API, either real or stub. No need in detecting presense of 'device bpf'. r228813 | glebius | 2011-12-22 22:51:35 +0400 (чт, 22 дек 2011) | 2 lines We really mean MTU of the real interface here, not of our pseudo. r228814 | glebius | 2011-12-22 22:56:27 +0400 (чт, 22 дек 2011) | 16 lines Merge couple more fixes from OpenBSD to bulk processing: revision 1.118 date: 2009/03/23 06:19:59; author: dlg; state: Exp; lines: +8 -6 wait an appropriate amount of time before giving up on a bulk update, rather than giving up after a hardcoded 5 seconds (which is generally much too short an interval for a bulk update). pointed out by david@, eyeballed by mcbride@ revision 1.171 date: 2011/10/31 22:02:52; author: mikeb; state: Exp; lines: +2 -1 Don't forget to cancel bulk update failure timeout when destroying an interface. Problem report and fix from Erik Lax, thanks! Start a brief note of revisions merged from OpenBSD. r228815 | glebius | 2011-12-22 23:05:58 +0400 (чт, 22 дек 2011) | 12 lines Merge from OpenBSD: revision 1.120 date: 2009/04/04 13:09:29; author: dlg; state: Exp; lines: +5 -5 use time_uptime instead of time_second internally. time_uptime isnt affected by adjusting the clock. revision 1.175 date: 2011/11/25 12:52:10; author: dlg; state: Exp; lines: +3 -3 use time_uptime to set state creation values as time_second can be skewed at runtime by things like date(1) and ntpd. time_uptime is monotonic and therefore more useful to compare against. r228816 | glebius | 2011-12-22 23:09:55 +0400 (чт, 22 дек 2011) | 11 lines Merge from OpenBSD: revision 1.122 date: 2009/05/13 01:01:34; author: dlg; state: Exp; lines: +6 -4 only keep track of the number of updates on tcp connections. state sync on all the other protocols is simply pushing the timeouts along which has a resolution of 1 second, so it isnt going to be hurt by pfsync taking up to a second to send it over. keep track of updates on tcp still though, their windows need constant attention. 2011-06-28T11:57:25Z Bjoern A. Zeeb bz@FreeBSD.org 2011-06-28T11:57:25Z urn:sha1:e0bfbfce7922dd3c28eb072b599c6bb8f65f039e You need to update userland (world and ports) tools to be in sync with the kernel. Submitted by: mlaier Submitted by: eri 2004-06-16T22:59:06Z Max Laier mlaier@FreeBSD.org 2004-06-16T22:59:06Z urn:sha1:a306c902b8a24b04a2ecece767f48182fc31be1a - Remove pflog and pfsync modules. Things will change in such a fashion that there will be one module with pf+pflog that can be loaded into GENERIC without problems (which is what most people want). pfsync is no longer possible as a module. - Add multicast address for in-kernel multicast pfsync protocol. Protocol glue will follow once the import is done. - Add one more mbuf tag 2004-04-06T15:12:50Z Max Laier mlaier@FreeBSD.org 2004-04-06T15:12:50Z urn:sha1:1ffe5d762b1dba2d7bf54e412484286ccd02d1d4 for INET6-less kernel. Requested by: many Approved by: bms(mentor) 2004-02-26T03:53:54Z Max Laier mlaier@FreeBSD.org 2004-02-26T03:53:54Z urn:sha1:cc5934f5afcc7d243b43ff83f093676556c2488d pf/pflog/pfsync as modules. Do not list them in NOTES or modules/Makefile (i.e. do not connect it to any (automatic) builds - yet). Approved by: bms(mentor)