From owner-freebsd-ipfw@FreeBSD.ORG Sun May 8 06:07:54 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9702E106564A for ; Sun, 8 May 2011 06:07:54 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8208FC0C for ; Sun, 8 May 2011 06:07:54 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p485ngIi040127 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 7 May 2011 22:49:47 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DC62EF1.6050800@freebsd.org> Date: Sat, 07 May 2011 22:49:37 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jack Raats References: <80DC3A23AD6C467E8523B68F1F47DC1D@jarasc430> In-Reply-To: <80DC3A23AD6C467E8523B68F1F47DC1D@jarasc430> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ipfw@freebsd.org, Mickey Harvey Subject: Re: run pf or ipfw within a jail? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2011 06:07:54 -0000 On 5/6/11 11:01 PM, Jack Raats wrote: > Normally you run the firewall on the host machine not in the jail. > well that's the whole point of the new virtually networking on jails. each jail has its own networking stack and can have interfaces directly attached that don't come through the "host" machine. for this reason (and many others) it is possible for and often the required behaviour, to run a separate and separate firewall for each jail. ipfw works well though dummynet doesn't yet.. and you need a spaecial version of pf to do it which hasn't been committed yet. So the answer is: "use ipfw within a 'vnet' jail". > > ----- Original Message ----- From: "Mickey Harvey" > To: > Sent: Friday, May 06, 2011 10:29 PM > Subject: run pf or ipfw within a jail? > > >> Is it possible to run pf or ipfw within a jail? I am running 8.2 >> and have >> vimage compiled in the kernel. >> _______________________________________________ >> freebsd-ipfw@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw >> To unsubscribe, send any mail to >> "freebsd-ipfw-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" > From owner-freebsd-ipfw@FreeBSD.ORG Mon May 9 11:07:08 2011 Return-Path: Delivered-To: freebsd-ipfw@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7409A1065670 for ; Mon, 9 May 2011 11:07:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6317C8FC0C for ; Mon, 9 May 2011 11:07:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p49B78iB070654 for ; Mon, 9 May 2011 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p49B778t070652 for freebsd-ipfw@FreeBSD.org; Mon, 9 May 2011 11:07:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 May 2011 11:07:07 GMT Message-Id: <201105091107.p49B778t070652@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ipfw@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-ipfw@FreeBSD.org X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 11:07:08 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p bin/156838 ipfw [dummynet] ipfw(8): "ipfw pipe show" shows wrong dummy o kern/156770 ipfw [ipfw] [dummynet] [patch]: performance improvement and o bin/156653 ipfw ipfw(8) reports missing file as parameter problem o kern/156410 ipfw [patch][ipfw] tablearg option for ipfw setfib o kern/155927 ipfw [ipfw] ipfw stops to check packets for compliance with o bin/153252 ipfw [ipfw][patch] ipfw lockdown system in subsequent call o kern/153161 ipfw IPFIREWALL does not allow specify rules with ICMP code o kern/152113 ipfw [ipfw] page fault on 8.1-RELEASE caused by certain amo o kern/150798 ipfw [ipfw] ipfw2 fwd rule matches packets but does not do o kern/148827 ipfw [ipfw] divert broken with in-kernel ipfw o kern/148689 ipfw [ipfw] antispoof wrongly triggers on link local IPv6 a o kern/148430 ipfw [ipfw] IPFW schedule delete broken. o kern/148157 ipfw [ipfw] IPFW in kernel nat BUG found in FreeBSD 8.1-PRE o kern/148091 ipfw [ipfw] ipfw ipv6 handling broken. o kern/147720 ipfw [ipfw] ipfw dynamic rules and fwd o kern/145305 ipfw [ipfw] ipfw problems, panics, data corruption, ipv6 so o kern/144269 ipfw [ipfw] problem with ipfw tables o kern/144187 ipfw [ipfw] deadlock using multiple ipfw nat and multiple l o kern/143973 ipfw [ipfw] [panic] ipfw forward option causes kernel reboo o kern/143621 ipfw [ipfw] [dummynet] [patch] dummynet and vnet use result o kern/143474 ipfw [ipfw] ipfw table contains the same address f kern/142951 ipfw [dummynet] using pipes&queues gives OUCH! pipe should o kern/139581 ipfw [ipfw] "ipfw pipe" not limiting bandwidth o kern/139226 ipfw [ipfw] install_state: entry already present, done o kern/137346 ipfw [ipfw] ipfw nat redirect_proto is broken o kern/137232 ipfw [ipfw] parser troubles o kern/136695 ipfw [ipfw] [patch] fwd reached after skipto in dynamic rul o kern/135476 ipfw [ipfw] IPFW table breaks after adding a large number o o bin/134975 ipfw [patch] ipfw(8) can't work with set in rule file. o kern/131817 ipfw [ipfw] blocks layer2 packets that should not be blocke o kern/131601 ipfw [ipfw] [panic] 7-STABLE panic in nat_finalise (tcp=0) o kern/131558 ipfw [ipfw] Inconsistent "via" ipfw behavior o bin/130132 ipfw [patch] ipfw(8): no way to get mask from ipfw pipe sho o kern/129103 ipfw [ipfw] IPFW check state does not work =( o kern/129093 ipfw [ipfw] ipfw nat must not drop packets o kern/129036 ipfw [ipfw] 'ipfw fwd' does not change outgoing interface n o kern/128260 ipfw [ipfw] [patch] ipfw_divert damages IPv6 packets o kern/127230 ipfw [ipfw] [patch] Feature request to add UID and/or GID l o kern/127209 ipfw [ipfw] IPFW table become corrupted after many changes o bin/125370 ipfw [ipfw] [patch] increase a line buffer limit o conf/123119 ipfw [patch] rc script for ipfw does not handle IPv6 o kern/122963 ipfw [ipfw] tcpdump does not show packets redirected by 'ip o kern/122109 ipfw [ipfw] ipfw nat traceroute problem s kern/121807 ipfw [request] TCP and UDP port_table in ipfw o kern/121382 ipfw [dummynet] 6.3-RELEASE-p1 page fault in dummynet (corr o kern/121122 ipfw [ipfw] [patch] add support to ToS IP PRECEDENCE fields o kern/118993 ipfw [ipfw] page fault - probably it's a locking problem o bin/117214 ipfw ipfw(8) fwd with IPv6 treats input as IPv4 o kern/116009 ipfw [ipfw] [patch] Ignore errors when loading ruleset from o docs/113803 ipfw [patch] ipfw(8) - don't get bitten by the fwd rule o kern/112561 ipfw [ipfw] ipfw fwd does not work with some TCP packets o kern/105330 ipfw [ipfw] [patch] ipfw (dummynet) does not allow to set q o bin/104921 ipfw [patch] ipfw(8) sometimes treats ipv6 input as ipv4 (a o kern/104682 ipfw [ipfw] [patch] Some minor language consistency fixes a o kern/103454 ipfw [ipfw] [patch] [request] add a facility to modify DF b o kern/103328 ipfw [ipfw] [request] sugestions about ipfw table o kern/102471 ipfw [ipfw] [patch] add tos and dscp support o kern/98831 ipfw [ipfw] ipfw has UDP hickups o kern/97951 ipfw [ipfw] [patch] ipfw does not tie interface details to o kern/95084 ipfw [ipfw] [regression] [patch] IPFW2 ignores "recv/xmit/v o kern/93300 ipfw [ipfw] ipfw pipe lost packets o kern/91847 ipfw [ipfw] ipfw with vlanX as the device o kern/88659 ipfw [modules] ipfw and ip6fw do not work properly as modul o kern/87032 ipfw [ipfw] [patch] ipfw ioctl interface implementation o kern/86957 ipfw [ipfw] [patch] ipfw mac logging o bin/83046 ipfw [ipfw] ipfw2 error: "setup" is allowed for icmp, but s o kern/82724 ipfw [ipfw] [patch] [request] Add setnexthop and defaultrou o bin/78785 ipfw [patch] ipfw(8) verbosity locks machine if /etc/rc.fir o kern/74104 ipfw [ipfw] ipfw2/1 conflict not detected or reported, manp o kern/73910 ipfw [ipfw] serious bug on forwarding of packets after NAT o kern/72987 ipfw [ipfw] ipfw/dummynet pipe/queue 'queue [BYTES]KBytes ( o kern/71366 ipfw [ipfw] "ipfw fwd" sometimes rewrites destination mac a o kern/69963 ipfw [ipfw] install_state warning about already existing en o kern/60719 ipfw [ipfw] Headerless fragments generate cryptic error mes o kern/55984 ipfw [ipfw] [patch] time based firewalling support for ipfw o kern/51274 ipfw [ipfw] [patch] ipfw2 create dynamic rules with parent o kern/48172 ipfw [ipfw] [patch] ipfw does not log size and flags o kern/46159 ipfw [ipfw] [patch] [request] ipfw dynamic rules lifetime f a kern/26534 ipfw [ipfw] Add an option to ipfw to log gid/uid of who cau 79 problems total. From owner-freebsd-ipfw@FreeBSD.ORG Mon May 9 17:17:31 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74FCB106566C for ; Mon, 9 May 2011 17:17:31 +0000 (UTC) (envelope-from quamarniyaz.zhcet@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 087818FC0A for ; Mon, 9 May 2011 17:17:30 +0000 (UTC) Received: by wyf23 with SMTP id 23so5273173wyf.13 for ; Mon, 09 May 2011 10:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ofLnrQNAjvvF3SOVKys0BI51kjX8uvBL60yvl5Ys4O0=; b=iO4kYRtd9PRb364aZdK6jlLd1Wepy7hcz3JWW/ZincNftjL0ND5IKO88gtxHMsueZk FR8orkxBaxfvS/N9EOZKtcjHEQDTxEMtbY4s3L7hrAH6DvlrnIDpmRQhJlsgqkUcboac Lu2kmMb8bzvLzRbg9mmZBVspdAfChAvfpkRAE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZsPwh37hvij43xRQSio2wa18sRLsUk6totLTfhAOI7AZ63jSWH1Ai/e+Ffu5WN3eIb 3J0C0xhzOnMhXvy6FMq+xMgLztNNBu1eLL0QMjsnn5FWqtW43UaFSlKSHJemjWvARzGo MG+QymMgLIh3AKbv1hggZJgGeo991ZBz4jZew= MIME-Version: 1.0 Received: by 10.216.188.20 with SMTP id z20mr5658139wem.66.1304959603613; Mon, 09 May 2011 09:46:43 -0700 (PDT) Received: by 10.216.175.206 with HTTP; Mon, 9 May 2011 09:46:43 -0700 (PDT) Date: Mon, 9 May 2011 22:16:43 +0530 Message-ID: From: quamar niyaz To: freebsd-ipfw@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: DummyNet configuration for opportunistic Links for emulating DTN X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 17:17:31 -0000 Hi, I am working on a application which is meant for Delay Tolerant Network. I want to emulate the opportunistic link availability for the data sending nodes using dummyNet . One scenario, suppose from source node to destination node let's say a data link is available at around 9 a.m. morning and the latency of the link from source node to destination node is 1hr. So if a request for upload comes around 8 a.m. at the sending node then the data should start reaching to the destination node after 10 a.m. as the link between the nodes comes at 9 and the latency is 1 hr so delivery time at the destination node(9 a.m. +1hr. = 10.am.). In other words sending node should hold the data in its buffer till 10 a.m as the nodes are actually in my 100 Mbps LAN so for emulating this the sender must start sending the data after 10 a.m. Can the buffer holds such large amount of data e.g. 500 MB for an hour. Or I have to modify the buffer size if yes, to which file i have to modify and then build dummynet. Or simply writing a batch scripts is fine for this. Please let me know. Thanks in advance -- With regards, Quamar Niyaz Research Associate, Indian Institute of Technology, Delhi New Delhi-16 http://www.cse.iitd.ernet.in/~niyaz From owner-freebsd-ipfw@FreeBSD.ORG Mon May 9 20:35:05 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 523BB106566B for ; Mon, 9 May 2011 20:35:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 17F0B8FC17 for ; Mon, 9 May 2011 20:35:04 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id D399173027; Mon, 9 May 2011 22:50:29 +0200 (CEST) Date: Mon, 9 May 2011 22:50:29 +0200 From: Luigi Rizzo To: quamar niyaz Message-ID: <20110509205029.GC39097@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-ipfw@freebsd.org Subject: Re: DummyNet configuration for opportunistic Links for emulating DTN X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 20:35:05 -0000 On Mon, May 09, 2011 at 10:16:43PM +0530, quamar niyaz wrote: > Hi, > > I am working on a application which is meant for Delay Tolerant Network. I > want to emulate the opportunistic link availability for the data sending > nodes using dummyNet . One scenario, suppose from source node to > destination node let's say a data link is available at around 9 a.m. morning > and the latency of the link from source node to destination node is 1hr. So > if a request for upload comes around 8 a.m. at the sending node then the > data should start reaching to the destination node after 10 a.m. as the link > between the nodes comes at 9 and the latency is 1 hr so delivery time at the > destination node(9 a.m. +1hr. = 10.am.). In other words sending node should > hold the data in its buffer till 10 a.m as the nodes are actually in my 100 > Mbps LAN so for emulating this the sender must start sending the data after > 10 a.m. > > Can the buffer holds such large amount of data e.g. 500 MB for an hour. Or I > have to modify the buffer size if yes, to which file i have to modify and > then build dummynet. Or simply writing a batch scripts is fine for this. > Please let me know. Thanks in advance this kind of stuff belongs to the application layer, not in the link layer. It is not just a matter of buffering, but the fact that your application will likely want to choose what to send when the link becomes available. cheers luigi From owner-freebsd-ipfw@FreeBSD.ORG Mon May 9 20:58:31 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BA27106566C for ; Mon, 9 May 2011 20:58:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id D56158FC17 for ; Mon, 9 May 2011 20:58:30 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p49KwS1g051877 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 9 May 2011 13:58:29 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DC8556F.8050600@freebsd.org> Date: Mon, 09 May 2011 13:58:23 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: quamar niyaz References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ipfw@freebsd.org Subject: Re: DummyNet configuration for opportunistic Links for emulating DTN X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2011 20:58:31 -0000 On 5/9/11 9:46 AM, quamar niyaz wrote: > Hi, > > I am working on a application which is meant for Delay Tolerant Network. I > want to emulate the opportunistic link availability for the data sending > nodes using dummyNet . One scenario, suppose from source node to > destination node let's say a data link is available at around 9 a.m. morning > and the latency of the link from source node to destination node is 1hr. So > if a request for upload comes around 8 a.m. at the sending node then the > data should start reaching to the destination node after 10 a.m. as the link > between the nodes comes at 9 and the latency is 1 hr so delivery time at the > destination node(9 a.m. +1hr. = 10.am.). In other words sending node should > hold the data in its buffer till 10 a.m as the nodes are actually in my 100 > Mbps LAN so for emulating this the sender must start sending the data after > 10 a.m. > > Can the buffer holds such large amount of data e.g. 500 MB for an hour. Or I > have to modify the buffer size if yes, to which file i have to modify and > then build dummynet. Or simply writing a batch scripts is fine for this. > Please let me know. Thanks in advance > pull the packets offline using divert, ng, pcap or similar and store them on disk, then reinject them later. From owner-freebsd-ipfw@FreeBSD.ORG Thu May 12 16:07:42 2011 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C000C106564A for ; Thu, 12 May 2011 16:07:42 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27]) by mx1.freebsd.org (Postfix) with ESMTP id 7BFE18FC1A for ; Thu, 12 May 2011 16:07:42 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.75 (FreeBSD)) (envelope-from ) id 1QKXrn-000Aqy-Ng for freebsd-ipfw@freebsd.org; Thu, 12 May 2011 17:31:55 +0200 Date: Thu, 12 May 2011 17:29:25 +0200 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <1562548807.20110512172925@nitronet.pl> To: Luigi Rizzo MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false Cc: Brandon Gooch , freebsd-ipfw@freebsd.org, Jack Vogel , freebsd-net@freebsd.org Subject: Re: X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2011 16:07:42 -0000 Hi guys and lists, Hope I won't bring bad luck on myself by posting this too early, but here goes. Apparently during the last 3 weeks my bi-weekly crashing problem has been solved. That, or world built without openssl was the reason. $ uprecords # Uptime | System Boot up ----------------------------+--------------------------------------------------- -> 1 18 days, 09:06:00 | FreeBSD 8.2-STABLE Sun Apr 24 08:22:05 2011 2 16 days, 07:06:18 | FreeBSD 8.2-STABLE Tue Apr 5 06:13:14 2011 3 15 days, 08:27:58 | FreeBSD 8.2-STABLE Sun Mar 20 20:42:15 2011 4 15 days, 05:42:23 | FreeBSD 8.2-PRERELEASE Wed Dec 22 16:19:55 2010 5 14 days, 22:31:42 | FreeBSD 8.2-PRERELEASE Sun Jan 9 03:07:59 2011 6 14 days, 05:25:46 | FreeBSD 8.2-PRERELEASE Mon Jan 24 01:55:34 2011 7 13 days, 15:04:37 | FreeBSD 8.2-STABLE Mon Mar 7 05:34:55 2011 8 13 days, 00:49:00 | FreeBSD 8.2-PRERELEASE Sat Feb 19 23:47:06 2011 9 12 days, 15:42:45 | FreeBSD 8.2-PRERELEASE Mon Feb 7 07:30:07 2011 10 2 days, 18:57:20 | FreeBSD 8.2-STABLE Thu Apr 21 13:22:53 2011 ----------------------------+--------------------------------------------------- NewRec 2 days, 01:59:41 | since Tue May 10 15:28:23 2011 up 140 days, 13:41:21 | since Wed Dec 22 16:19:55 2010 down 0 days, -10:-26:-4 | since Wed Dec 22 16:19:55 2010 %up 100.311 | since Wed Dec 22 16:19:55 2010 Cheers. :) From owner-freebsd-ipfw@FreeBSD.ORG Fri May 13 09:52:51 2011 Return-Path: Delivered-To: freebsd-ipfw@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F4121065670; Fri, 13 May 2011 09:52:51 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EA9D08FC1E; Fri, 13 May 2011 09:52:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4D9qoPZ023035; Fri, 13 May 2011 09:52:50 GMT (envelope-from ae@freefall.freebsd.org) Received: (from ae@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4D9qoFe023031; Fri, 13 May 2011 09:52:50 GMT (envelope-from ae) Date: Fri, 13 May 2011 09:52:50 GMT Message-Id: <201105130952.p4D9qoFe023031@freefall.freebsd.org> To: lijimlee@gmail.com, ae@FreeBSD.org, freebsd-ipfw@FreeBSD.org From: ae@FreeBSD.org Cc: Subject: Re: bin/156838: [dummynet] ipfw(8): "ipfw pipe show" shows wrong dummynet pipe delay when hz is not 1000 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2011 09:52:51 -0000 Synopsis: [dummynet] ipfw(8): "ipfw pipe show" shows wrong dummynet pipe delay when hz is not 1000 State-Changed-From-To: patched->closed State-Changed-By: ae State-Changed-When: Fri May 13 09:52:22 UTC 2011 State-Changed-Why: Merged to stable/8. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=156838 From owner-freebsd-ipfw@FreeBSD.ORG Fri May 13 10:00:22 2011 Return-Path: Delivered-To: freebsd-ipfw@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 423A31065674 for ; Fri, 13 May 2011 10:00:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 185008FC13 for ; Fri, 13 May 2011 10:00:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4DA0L0p023315 for ; Fri, 13 May 2011 10:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4DA0LEJ023314; Fri, 13 May 2011 10:00:21 GMT (envelope-from gnats) Date: Fri, 13 May 2011 10:00:21 GMT Message-Id: <201105131000.p4DA0LEJ023314@freefall.freebsd.org> To: freebsd-ipfw@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: bin/156838: commit references a PR X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2011 10:00:22 -0000 The following reply was made to PR bin/156838; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/156838: commit references a PR Date: Fri, 13 May 2011 09:52:18 +0000 (UTC) Author: ae Date: Fri May 13 09:52:04 2011 New Revision: 221831 URL: http://svn.freebsd.org/changeset/base/221831 Log: MFC r221521: Convert delay parameter back to ms when reporting to user. PR: 156838 Modified: stable/8/sys/netinet/ipfw/ip_dn_glue.c stable/8/sys/netinet/ipfw/ip_dummynet.c Directory Properties: stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) Modified: stable/8/sys/netinet/ipfw/ip_dn_glue.c ============================================================================== --- stable/8/sys/netinet/ipfw/ip_dn_glue.c Fri May 13 07:21:41 2011 (r221830) +++ stable/8/sys/netinet/ipfw/ip_dn_glue.c Fri May 13 09:52:04 2011 (r221831) @@ -624,7 +624,7 @@ dn_c_copy_pipe(struct dn_schk *s, struct /* These 4 field are the same in pipe7 and pipe8 */ pipe7->next.sle_next = (struct dn_pipe7 *)DN_IS_PIPE; pipe7->bandwidth = l->bandwidth; - pipe7->delay = l->delay; + pipe7->delay = l->delay * 1000 / hz; pipe7->pipe_nr = l->link_nr - DN_MAX_ID; if (!is7) { Modified: stable/8/sys/netinet/ipfw/ip_dummynet.c ============================================================================== --- stable/8/sys/netinet/ipfw/ip_dummynet.c Fri May 13 07:21:41 2011 (r221830) +++ stable/8/sys/netinet/ipfw/ip_dummynet.c Fri May 13 09:52:04 2011 (r221831) @@ -807,6 +807,7 @@ copy_obj(char **start, char *end, void * /* Adjust burst parameter for link */ struct dn_link *l = (struct dn_link *)*start; l->burst = div64(l->burst, 8 * hz); + l->delay = l->delay * 1000 / hz; } else if (o->type == DN_SCH) { /* Set id->id to the number of instances */ struct dn_schk *s = _o; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org"