From owner-freebsd-ipfw@FreeBSD.ORG Mon Nov 23 11:06:58 2009 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 28BF91065698 for ; Mon, 23 Nov 2009 11:06:58 +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 0CA4D8FC08 for ; Mon, 23 Nov 2009 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nANB6vat070165 for ; Mon, 23 Nov 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nANB6vD8070163 for freebsd-ipfw@FreeBSD.org; Mon, 23 Nov 2009 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Nov 2009 11:06:57 GMT Message-Id: <200911231106.nANB6vD8070163@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, 23 Nov 2009 11:06:58 -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 -------------------------------------------------------------------------------- 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/132553 ipfw [ipfw] ipfw doesn't understand ftp-data port 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 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 (cor 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 kern/117234 ipfw [ipfw] [patch] ipfw send_pkt() and ipfw_tick() don't s 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 bin/115172 ipfw [patch] ipfw(8) list show some rules with a wrong form o docs/113803 ipfw [patch] ipfw(8) - don't get bitten by the fwd rule p kern/113388 ipfw [ipfw] [patch] Addition actions with rules within spec o kern/112708 ipfw [ipfw] ipfw is seems to be broken to limit number of c o kern/112561 ipfw [ipfw] ipfw fwd does not work with some TCP packets o kern/107305 ipfw [ipfw] ipfw fwd doesn't seem to work 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/97504 ipfw [ipfw] IPFW Rules bug 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 kern/82724 ipfw [ipfw] [patch] [request] Add setnexthop and defaultrou s kern/80642 ipfw [ipfw] [patch] ipfw small patch - new RULE OPTION 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 63 problems total. From owner-freebsd-ipfw@FreeBSD.ORG Tue Nov 24 18:01:59 2009 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 2F05B106568F; Tue, 24 Nov 2009 18:01:59 +0000 (UTC) (envelope-from ceache@gmail.com) Received: from mail-ew0-f221.google.com (mail-ew0-f221.google.com [209.85.219.221]) by mx1.freebsd.org (Postfix) with ESMTP id 89F298FC27; Tue, 24 Nov 2009 18:01:57 +0000 (UTC) Received: by ewy21 with SMTP id 21so793790ewy.13 for ; Tue, 24 Nov 2009 10:01:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type:content-transfer-encoding; bh=5G7CF/S/fbf1z8Mzf+a5os2apakHH5861W0ajc3176U=; b=Kdr53/YbkiCoQKrttuWmORsdmiH/0g/z8BvSXlHNe3GVAQTUFfDwOYbkwjKiiPCKMu FMY6EG0S2xvXBTyMa9DgWyHsFn5r3pqWFzNz0e50FDgx7kMvruLCBdcaV3eKxZhtLx+u 6HNiChSq85AioN3s5eTU7mw42XdvZC+4Cs4lM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=ZPTseO3OvjGdlpGp2DQrCr9KEqzu7jFLPsBsDcbcZhH7ZLLKP4cLX7QPnc2302srzK 5jMC2vEGR/juZbp7BxascIe93nFy08Ucty+KDmopC3ypknGi1qx04pgDCHgIBPyIAKgV OZlsJCOWjgJ0hY4nHDo72OGT9pk+3eIrSYDdI= MIME-Version: 1.0 Received: by 10.213.109.156 with SMTP id j28mr5426224ebp.79.1259084451157; Tue, 24 Nov 2009 09:40:51 -0800 (PST) From: Charles Henri de Boysson Date: Tue, 24 Nov 2009 12:40:31 -0500 Message-ID: <184b04b20911240940g36621d69hf3ca160a6d122ecc@mail.gmail.com> To: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Subject: Performance issue with new pipe profile feature in FreeBSD 8.0 RELEASE 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: Tue, 24 Nov 2009 18:01:59 -0000 Hi, I have a simple setup with two computer connected via a FreeBSD bridge running 8.0 RELEASE. I am trying to use dummynet to simulate a wireless network between the two and for that I wanted to use the pipe profile feature of FreeBSD 8.0. But as I was experimenting with the pipe profile feature I ran into some is= sues. I have setup ipfw to send traffic coming for either interface of the bridge to a respective pipe as follow: # ipfw show 00100 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 allow ip from any to an= y via lo0 00200 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 deny ip from any to 127= .0.0.0/8 00300 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 deny ip from 127.0.0.0/= 8 to any 01000 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 pipe 1 ip from any to a= ny via vr0 layer2 01100 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 pipe 101 ip from any to= any via vr4 layer2 65000 =C2=A07089 =C2=A0 =C2=A0716987 allow ip from any to any 65535 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 deny ip from any to any When I setup my pipes as follow: # ipfw pipe 1 config bw 10Mbit delay 25 mask proto 0 # ipfw pipe 101 config bw 10Mbit delay 25 mask proto 0 # ipfw pipe show 00001: =C2=A010.000 Mbit/s =C2=A0 25 ms =C2=A0 50 sl. 0 queues (1 buckets) = droptail burst: 0 Byte 00101: =C2=A010.000 Mbit/s =C2=A0 25 ms =C2=A0 50 sl. 0 queues (1 buckets) = droptail burst: 0 Byte With this setup, when I try to pass traffic through the bridge with iperf, I obtain the desired speed: iperf reports about 9.7Mbits/sec in UDP mode and 9.5 in TCP mode (I copied and pasted the iperf runs at the end of this email). The problem arise when I setup pipe 1 (the downlink) with an equivalent profile (I tried to simplify it as much as possible). # ipfw pipe 1 config profile test.pipeconf mask proto 0 # ipfw pipe show 00001: 10.000 Mbit/s 0 ms 50 sl. 0 queues (1 buckets) droptail burst: 0 Byte profile: name "test" loss 1.000000 samples 2 00101: 10.000 Mbit/s 25 ms 50 sl. 0 queues (1 buckets) droptail burst: 0 Byte # cat test.pipeconf name test bw 10Mbit loss-level 1.0 samples 2 prob delay 0.0 25 1.0 25 The same iperf TCP tests then collapse to about 500Kbit/s with the same settings (copy and pasted the output of iperf bellow) I can't figure out what is going on. There is no visible load on the bridge= . I have an unmodified GENERIC kernel with the following sysctl. net.link.bridge.ipfw: 1 kern.hz: 1000 The bridge configuration is as follow: bridge0: flags=3D8843 metric 0 mtu = 1500 ether 1a:1f:2e:42:74:8d id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: vr4 flags=3D143 =C2=A0 =C2=A0 =C2=A0 =C2=A0ifmaxaddr 0 port 6 priority 128 path cost 200000 member: vr0 flags=3D143 =C2=A0 =C2=A0 =C2=A0 =C2=A0ifmaxaddr 0 port 2 priority 128 path cost 200000 iperf runs without the profile set: % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 ------------------------------------------------------------ Client connecting to 10.0.0.254, TCP port 5001 Binding to local address 10.1.0.1 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-15.0 sec 17.0 MBytes 9.49 Mbits/sec % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit ------------------------------------------------------------ Client connecting to 10.0.0.254, UDP port 5001 Binding to local address 10.1.0.1 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-15.0 sec 18.8 MBytes 10.5 Mbits/sec [ 3] Sent 13382 datagrams [ 3] Server Report: [ 3] 0.0-15.1 sec 17.4 MBytes 9.72 Mbits/sec 0.822 ms 934/13381 (7%) [ 3] 0.0-15.1 sec 1 datagrams received out-of-order iperf runs with the profile set: % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 ------------------------------------------------------------ Client connecting to 10.0.0.254, TCP port 5001 Binding to local address 10.1.0.1 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-15.7 sec 968 KBytes 505 Kbits/sec % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit ------------------------------------------------------------ Client connecting to 10.0.0.254, UDP port 5001 Binding to local address 10.1.0.1 Sending 1470 byte datagrams UDP buffer size: 110 KByte (default) ------------------------------------------------------------ [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-15.0 sec 18.8 MBytes 10.5 Mbits/sec [ 3] Sent 13382 datagrams [ 3] Server Report: [ 3] 0.0-16.3 sec 893 KBytes 449 Kbits/sec 1.810 ms 12757/13379 (9= 5%) Let me know what other information you would need to help me debugging this= . In advance, thank you for your help -- Charles-Henri de Boysson From owner-freebsd-ipfw@FreeBSD.ORG Wed Nov 25 05:20:35 2009 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 9188010656B3; Wed, 25 Nov 2009 05:20:35 +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 0C4D78FC0C; Wed, 25 Nov 2009 05:20:34 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 0A872730DA; Wed, 25 Nov 2009 06:28:33 +0100 (CET) Date: Wed, 25 Nov 2009 06:28:33 +0100 From: Luigi Rizzo To: Charles Henri de Boysson Message-ID: <20091125052833.GA6726@onelab2.iet.unipi.it> References: <184b04b20911240940g36621d69hf3ca160a6d122ecc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <184b04b20911240940g36621d69hf3ca160a6d122ecc@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: Performance issue with new pipe profile feature in FreeBSD 8.0 RELEASE 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: Wed, 25 Nov 2009 05:20:35 -0000 Hi, there is no bug, the 'pipe profile' code is working correctly. In your mail below you are comparing two different things. "pipe config bw 10Mbit/s delay 25ms" means that _after shaping_ at 10Mbps, all traffic will be subject to an additional delay of 25ms. Each packet (1470 bytes) will take Length/Bandwidth sec to come out or 1470*8/10M = 1.176ms , but you won't see them until you wait another 25ms (7500km at the speed of light). "pipe config bw 10Mbit/s profile "test" ..." means that in addition to the Length/Bandwidth, _each packet transmission_ will consume some additional air-time as specified in the profile (25ms in your case) So, in your case with 1470bytes/pkt each transmission will take len/bw (1.176ms) + 25ms (extra air time) = 26.76ms That is 25 times more than the previous case and explains the reduced bandwidth you see. The 'delay profile' is effectively extra air time used for each transmission. The name is probably confusing, i should have called it 'extra-time' or 'overhead' and not 'delay' cheers luigi On Tue, Nov 24, 2009 at 12:40:31PM -0500, Charles Henri de Boysson wrote: > Hi, > > I have a simple setup with two computer connected via a FreeBSD bridge > running 8.0 RELEASE. > I am trying to use dummynet to simulate a wireless network between the > two and for that I wanted to use the pipe profile feature of FreeBSD > 8.0. > But as I was experimenting with the pipe profile feature I ran into some issues. > > I have setup ipfw to send traffic coming for either interface of the > bridge to a respective pipe as follow: > > # ipfw show > 00100 ?? ?? 0 ?? ?? ?? ?? 0 allow ip from any to any via lo0 > 00200 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from any to 127.0.0.0/8 > 00300 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from 127.0.0.0/8 to any > 01000 ?? ?? 0 ?? ?? ?? ?? 0 pipe 1 ip from any to any via vr0 layer2 > 01100 ?? ?? 0 ?? ?? ?? ?? 0 pipe 101 ip from any to any via vr4 layer2 > 65000 ??7089 ?? ??716987 allow ip from any to any > 65535 ?? ?? 0 ?? ?? ?? ?? 0 deny ip from any to any > > When I setup my pipes as follow: > > # ipfw pipe 1 config bw 10Mbit delay 25 mask proto 0 > # ipfw pipe 101 config bw 10Mbit delay 25 mask proto 0 > # ipfw pipe show > > 00001: ??10.000 Mbit/s ?? 25 ms ?? 50 sl. 0 queues (1 buckets) droptail > burst: 0 Byte > 00101: ??10.000 Mbit/s ?? 25 ms ?? 50 sl. 0 queues (1 buckets) droptail > burst: 0 Byte > > With this setup, when I try to pass traffic through the bridge with > iperf, I obtain the desired speed: iperf reports about 9.7Mbits/sec in > UDP mode and 9.5 in TCP mode (I copied and pasted the iperf runs at > the end of this email). > > The problem arise when I setup pipe 1 (the downlink) with an > equivalent profile (I tried to simplify it as much as possible). > > # ipfw pipe 1 config profile test.pipeconf mask proto 0 > # ipfw pipe show > 00001: 10.000 Mbit/s 0 ms 50 sl. 0 queues (1 buckets) droptail > burst: 0 Byte > profile: name "test" loss 1.000000 samples 2 > 00101: 10.000 Mbit/s 25 ms 50 sl. 0 queues (1 buckets) droptail > burst: 0 Byte > > # cat test.pipeconf > name test > bw 10Mbit > loss-level 1.0 > samples 2 > prob delay > 0.0 25 > 1.0 25 > > The same iperf TCP tests then collapse to about 500Kbit/s with the > same settings (copy and pasted the output of iperf bellow) > > I can't figure out what is going on. There is no visible load on the bridge. > I have an unmodified GENERIC kernel with the following sysctl. > > net.link.bridge.ipfw: 1 > kern.hz: 1000 > > The bridge configuration is as follow: > > bridge0: flags=8843 metric 0 mtu 1500 > ether 1a:1f:2e:42:74:8d > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: vr4 flags=143 > ?? ?? ?? ??ifmaxaddr 0 port 6 priority 128 path cost 200000 > member: vr0 flags=143 > ?? ?? ?? ??ifmaxaddr 0 port 2 priority 128 path cost 200000 > > > iperf runs without the profile set: > % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 > ------------------------------------------------------------ > Client connecting to 10.0.0.254, TCP port 5001 > Binding to local address 10.1.0.1 > TCP window size: 16.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-15.0 sec 17.0 MBytes 9.49 Mbits/sec > > % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit > ------------------------------------------------------------ > Client connecting to 10.0.0.254, UDP port 5001 > Binding to local address 10.1.0.1 > Sending 1470 byte datagrams > UDP buffer size: 110 KByte (default) > ------------------------------------------------------------ > [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-15.0 sec 18.8 MBytes 10.5 Mbits/sec > [ 3] Sent 13382 datagrams > [ 3] Server Report: > [ 3] 0.0-15.1 sec 17.4 MBytes 9.72 Mbits/sec 0.822 ms 934/13381 (7%) > [ 3] 0.0-15.1 sec 1 datagrams received out-of-order > > > iperf runs with the profile set: > % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 > ------------------------------------------------------------ > Client connecting to 10.0.0.254, TCP port 5001 > Binding to local address 10.1.0.1 > TCP window size: 16.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-15.7 sec 968 KBytes 505 Kbits/sec > > % iperf -B 10.1.0.1 -c 10.0.0.254 -t 15 -u -b 10Mbit > ------------------------------------------------------------ > Client connecting to 10.0.0.254, UDP port 5001 > Binding to local address 10.1.0.1 > Sending 1470 byte datagrams > UDP buffer size: 110 KByte (default) > ------------------------------------------------------------ > [ 3] local 10.1.0.1 port 5001 connected with 10.0.0.254 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-15.0 sec 18.8 MBytes 10.5 Mbits/sec > [ 3] Sent 13382 datagrams > [ 3] Server Report: > [ 3] 0.0-16.3 sec 893 KBytes 449 Kbits/sec 1.810 ms 12757/13379 (95%) > > > Let me know what other information you would need to help me debugging this. > In advance, thank you for your help > > -- > Charles-Henri de Boysson > _______________________________________________ > 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"