idolclub 发表于 2005-5-29 20:31:10

今次又回到了FreeBSD 4.11了.1.2b8 (05/29/2005) WARNING: this release does not include support for Atheros-based wireless NICs! switched base system back to FreeBSD 4.11 merged ifstats.cgi and cpustats.cgi into stats.cgi updated PHP to 4.3.11 only log the first passed packet, and not every packet in the same session back out captive portal per-user bandwidth patches for the time being as they're buggy and not currently maintained fix captive portal logout return ICMP port unreachable instead of protocol unreachable (ipfilter default) for rejected UDP packets auto-add proxy ARP option for new 1:1 NAT mappings auto-establish IPsec tunnel option removed for the time being (no good way of making it work actually) the IPsec SA preferral policy can be changed on the System: Advanced page (default: prefer new SAs after 30 seconds) captive portal: logout popup window is no longer enabled implicitly when using authentication kernel is now built with polling support; default is disabled, but it can be enabled using "sysctl kern.polling.enable=1" (see also "man polling") updated ipfilter window scaling and ICMP NAT checksum adjustment fixes updated DP83815 short cable bug workaround in sis driver

macafee 发表于 2005-5-29 20:38:39

消息已证实,为可靠消息!

pctone 发表于 2005-5-29 20:42:43

原本以? m0n0wall 新版?改用 FreeBSD 5.x kernel, 改用 pf (packet filter), 看?又回到 FreeBSD 4.x kernel 了.

macafee 发表于 2005-5-29 20:43:40

kernel is now built with polling support; default is disabled, but it can be enabled using "sysctl kern.polling.enable=1" (see also "man polling") 这个东西曾经这里不少人期待过.......

macafee 发表于 2005-5-29 20:57:51

太慢......下不下来.......

macafee 发表于 2005-5-29 21:03:56

终于找到个快的镜像~~~~~

macafee 发表于 2005-5-29 21:29:14

POLLING的详细设置如下:POLLING(4)             FreeBSD Kernel Interfaces Manual           POLLING(4)NAME   polling -- device polling supportSYNOPSIS   options DEVICE_POLLING   options HZ=1000DESCRIPTION   Device polling (polling for brevity) refers to a technique that lets the   operating system periodically poll devices, instead of relying on the   devices to generate interrupts when they need attention.This might seem   inefficient and counterintuitive, but when done properly, polling gives   more control to the operating system on when and how to handle devices,   with a number of advantages in terms of system responsiveness and perfor-   mance.   In particular, polling reduces the overhead for context switches which is   incurred when servicing interrupts, and gives more control on the sched-   uling of the CPU between various tasks (user processes, software inter-   rupts, device handling) which ultimately reduces the chances of livelock   in the system.   Principles of Operation   In the normal, interrupt-based mode, devices generate an interrupt when-   ever they need attention.        This in turn causes a context switch and the   execution of an interrupt handler which performs whatever processing is   needed by the device.The duration of the interrupt handler is poten-   tially unbounded unless the device driver has been programmed with real-   time concerns in mind (which is generally not the case for FreeBSD driv-   ers).Furthermore, under heavy traffic load, the system might be persis-   tently processing interrupts without being able to complete other work,   either in the kernel or in userland.   Device polling disables interrupts by polling devices at appropriate   times, i.e., on clock interrupts, system calls and within the idle loop.   This way, the context switch overhead is removed.        Furthermore, the oper-   ating system can control accurately how much work to spend in handling   device events, and thus prevent livelock by reserving some amount of CPU   to other tasks.   Enabling polling also changes the way software network interrupts are   scheduled, so there is never the risk of livelock because packets are not   processed to completion.   MIB Variables   The operation of polling is controlled by the following sysctl(8) MIB   variables:   kern.polling.enable             If set to non-zero, polling is enabled.Default is disabled.   kern.polling.user_frac             When polling is enabled, and provided that there is some work to             do, up to this percent of the CPU cycles is reserved to userland             tasks, the remaining fraction being available for polling pro-             cessing.Default is 50.   kern.polling.burst             Maximum number of packets grabbed from each network interface in             each timer tick.This number is dynamically adjusted by the ker-             nel, according to the programmed user_frac, burst_max, CPU speed,             and system load.   kern.polling.each_burst             The burst above is split into smaller chunks of this number of             packets, going round-robin among all interfaces registered for             polling.This prevents the case that a large burst from a single             interface can saturate the IP interrupt queue             (net.inet.ip.intr_queue_maxlen).Default is 5.   kern.polling.burst_max             Upper bound for kern.polling.burst.Note that when polling is             enabled, each interface can receive at most (HZ * burst_max)             packets per second unless there are spare CPU cycles available             for polling in the idle loop.This number should be tuned to             match the expected load (which can be quite high with GigE             cards).Default is 150 which is adequate for 100Mbit network and             HZ=1000.   kern.polling.idle_poll             Controls if polling is enabled in the idle loop.There are no             reasons (other than power saving) to disable this.Default is             enabled.   kern.polling.poll_in_trap             Controls if polling is enabled during hardware traps.Enabling             this can be useful to improve the network responsiveness of boxes             with 100% CPU usage.Default is disabled.   kern.polling.reg_frac             Controls how often (every reg_frac / HZ seconds) the status reg-             isters of the device are checked for error conditions and the             like.Increasing this value reduces the load on the bus, but             also delays the error detection.Default is 20.   kern.polling.handlers             How many active devices have registered for polling.   kern.polling.short_ticks   kern.polling.lost_polls   kern.polling.pending_polls   kern.polling.residual_burst   kern.polling.phase   kern.polling.suspect   kern.polling.stalled             Debugging variables.SUPPORTED DEVICES   Device polling requires explicit modifications to the device drivers.As   of this writing, the dc(4), em(4), fwe(4), fxp(4), nge(4), rl(4), sis(4),   ste(4), and vr(4) devices are supported, with others in the works.The   modifications are rather straightforward, consisting in the extraction of   the inner part of the interrupt service routine and writing a callback   function, *_poll(), which is invoked to probe the device for events and   process them.(See the conditionally compiled sections of the devices   mentioned above for more details.)   As in the worst case the devices are only polled on clock interrupts, in   order to reduce the latency in processing packets, it is advisable to   increase the frequency of the clock to at least 1000 HZ.HISTORY   Device polling first appeared in FreeBSD 4.6 and FreeBSD 5.0.AUTHORS   Device polling was written by Luigi Rizzo .FreeBSD 4.11                       April 5, 2004                          FreeBSD 4.11

samenlia 发表于 2005-5-29 22:24:24

QUOTE
原本以? m0n0wall 新版?改用 FreeBSD 5.x kernel, 改用 pf (packet filter), 看?又回到 FreeBSD 4.x kernel 了
1.2b5 (02/22/2005) upgraded base system to FreeBSD 5.3 support Atheros based wireless cards pf本身还不是很完善的,虽然多了一些功能,有了一些新特色,比如支持table(非常方便)。开发小组当前的目标是实现实用的功能,ipf其实也很出色。另外,freebsd 5.x也不是很出色,可以认为是一个过渡产品,预计下个月freebsd 6就出来了。

czw1240 发表于 2005-5-29 23:02:08

我现在还在用b6呢除非出1.2正式版否则我都费事换了

macafee 发表于 2005-5-29 23:14:12

QUOTE (samenlia @ May 29 2005, 10:24 PM)


QUOTE
原本以? m0n0wall 新版?改用 FreeBSD 5.x kernel, 改用 pf (packet filter), 看?又回到 FreeBSD 4.x kernel 了
1.2b5 (02/22/2005) upgraded base system to FreeBSD 5.3 support Atheros based wireless cards pf本身还不是很完善的,虽然多了一些功能,有了一些新特色,比如支持table(非常方便)。开发小组当前的目标是实现实用的功能,ipf其实也很出色。另外,freebsd 5.x也不是很出色,可以认为是一个过渡产品,预计下个月freebsd 6就出来了。
同意SAMENLIA的观点,FREEBSD5系列虽然支持不少新特性,但是系统的健壮性还不够,期待FREEBSD6能早日发布,从以前发布的一个对比测试可以看出,基于FREEBSD4系列的MONO确实在速度方面比基于FREEBSD5系列的更有优势!

macafee 发表于 2005-5-29 23:16:22

至于是否支持无线NIC,完全可以忽略,完全可以用NIC+无线AP的方案来解决,虽然成本提高,但是系统的可靠性和可管理性将更稳定更出色!

macafee 发表于 2005-5-29 23:25:40

明天有时间,我更新到1.2B8测试一下~~~~

analyst 发表于 2005-5-29 23:26:23

QUOTE (macafee @ May 29 2005, 09:03 PM)
终于找到个快的镜像~~~~~
估计是旧金山的。

su30fly 发表于 2005-5-30 00:53:02

b8的推出.证明freebsd4.11的经典之处.是什么我就不知道了还有polling,都是我想要的东西.先还准备自己弄出来.看来,还是指望开发小组靠得住.

lljlong 发表于 2005-5-30 05:21:02

如官方网下载慢,请到这下http://chonglang.3322.org/generic-pc-1.2b8.rar
页: [1] 2
查看完整版本: m0n0wall 1.2 b8 已推出