On Thu, 11 Dec 2014 10:58:18 +0200, Ahmed Kamal wrote: > I am trying to debug this over ssh (freebsd shell) .. While I'm quite > experienced with Linux, I'm new to BSDs .. Can someone guide me into > running a few commands to discover what's wrong .. Thanks a lot folks
For me at least, there are too many questions arising to speculate much. I know nothing about pfSense except what I can find on its website, and that's pretty scant on what's going on under the hood without actually digging into sources. I don't even know how and in what order packets are processed by pf and ipfw+dummynet, so don't count me of much use. Presumably you're running a pfSense 2.2 beta, or the just released RC? If so it's FreeBSD 10.1 based, while earlier releases are based on 8.2; you should show at least 'uname -a' contents, and in this case output of 'ipfw show' including rules feeding the pipe might demystify. 'ifconfig' re interface/s concerned (100Mbit? 10Gbit?), stuff that may matter .. But anyway, this seems confirmed as a pfSense bug by Chris Buechler's last comment on the bug URL you quote below: "dummynet burst on stock FreeBSD 10.1 does indeed work how I'd expect it to work. Ours doesn't have any impact whatsoever, with the exact same pipe config that has the expected behavior on 10.1. This has never worked, and there are too many 2.2 target issues already, so I just commented out the burst portion from the GUI bits. Can revisit later." And indeed, unless solved by you and whatever pfSense testers you can muster in the next week or so, it seems burst won't be in pfSense 2.2. One thing struck me comparing the burst description in ipfw(8) and this: https://redmine.pfsense.org/attachments/download/851/2013-09-18_110224.png and linked from another bug I snipped one stanza of 30-limiters-config.txt: <queue> <name>Limiter1</name> <number>1</number> <qlimit/> <plr/> <description/> <bandwidth> <item> <bw>5</bw> <burst/> <bwscale>Mb</bwscale> <bwsched>none</bwsched> </item> </bandwidth> <enabled>on</enabled> <buckets/> <mask>none</mask> <maskbits/> <maskbitsv6/> <delay>0</delay> </queue> but none of the 30 entries showed burst config .. I'm wondering whether they're using bytes as the units (as in your pipe show below) or whether the '100' in the image above would be specified as Mbits, seeing the bw is given in Mbit/s - or what? ie can you show your config for this in the XML form used by pfSense? And then, if you can find the PHP code that calculates and updates that config, and whatever code that reads that and runs 'ipfw pipe config', you'll maybe find the issue, or at least provide something to chew on. And just checking: you have a normally 3Mbit/s pipe you want to let the first 50Mbytes burst at full speed? Which would take how many seconds? cheers, Ian > On Fri, Dec 5, 2014 at 9:51 PM, Ahmed Kamal <email.ahmedka...@googlemail.com > > wrote: > > > Hi folks, > > > > Any thoughts on why "burst" is not having any effect? I'd really > > appreciate any feedback .. Thanks > > > > On Thu, Dec 4, 2014 at 12:18 AM, Ahmed Kamal < > > email.ahmedka...@googlemail.com> wrote: > > > >> Hi, > >> > >> I am using pfsense (hope this is not frowned upon) to configure ipfw > >> limiting. I am finding that rate limiting is working great, however the > >> "burst" parameter does not seem to have any effect at all. I found this > >> bug > >> open https://redmine.pfsense.org/issues/3933 .. Based on the milestone, > >> I'm not expecting a speedy fix. > >> > >> I would like to help debug whats wrong, I am pasting below the output of > >> "ipfw pipe show" I am hoping a more experienced eye can spot a > >> misconfiguration .. Thanks for the help > >> > >> # ipfw pipe show > >> > >> 00002: 3.000 Mbit/s 0 ms burst 50000000 > >> q131074 50 sl. 0 flows (1 buckets) sched 65538 weight 0 lmax 0 pri 0 > >> droptail > >> sched 65538 type FIFO flags 0x1 256 buckets 27 active > >> mask: 0x00 0x00000000/0x0000 -> 0xffffffff/0x0000 > >> BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes > >> Pkt/Byte Drp > >> 19 ip 0.0.0.0/0 10.0.0.19/0 13 19396 0 > >> 0 0 > >> 55 ip 0.0.0.0/0 10.0.0.55/0 51 6504 0 > >> 0 0 > >> 78 ip 0.0.0.0/0 10.0.0.78/0 1 52 0 > >> 0 0 > >> 81 ip 0.0.0.0/0 10.0.0.81/0 565 136618 0 > >> 0 0 > >> 83 ip 0.0.0.0/0 10.0.0.83/0 74 14998 0 > >> 0 0 > >> 90 ip 0.0.0.0/0 10.0.0.90/0 21 2011 0 > >> 0 0 > >> 100 ip 0.0.0.0/0 10.0.0.100/0 4465 2173866 0 > >> 0 0 > >> 101 ip 0.0.0.0/0 10.0.0.101/0 1077 1268015 0 > >> 0 0 > >> 110 ip 0.0.0.0/0 10.0.0.110/0 53 6269 0 > >> 0 0 > >> 124 ip 0.0.0.0/0 10.0.0.124/0 15 2064 0 > >> 0 0 > >> 134 ip 0.0.0.0/0 10.0.0.134/0 637 134530 0 > >> 0 0 > >> 135 ip 0.0.0.0/0 10.0.0.135/0 343 63025 0 > >> 0 0 > >> 143 ip 0.0.0.0/0 10.0.0.143/0 32 3109 0 > >> 0 0 > >> 145 ip 0.0.0.0/0 10.0.0.145/0 250 117755 0 > >> 0 0 > >> 147 ip 0.0.0.0/0 10.0.0.147/0 62037 85170555 0 > >> 0 347 > >> 150 ip 0.0.0.0/0 10.0.0.150/0 322 71834 0 > >> 0 0 > >> 152 ip 0.0.0.0/0 10.0.0.152/0 433 242323 0 > >> 0 0 > >> 156 ip 0.0.0.0/0 10.0.0.156/0 147 72501 0 > >> 0 0 > >> 174 ip 0.0.0.0/0 10.0.0.174/0 1635 1202725 0 > >> 0 0 > >> 180 ip 0.0.0.0/0 10.0.0.180/0 847 325265 0 > >> 0 0 > >> 183 ip 0.0.0.0/0 10.0.0.183/0 94 21052 0 > >> 0 0 > >> 187 ip 0.0.0.0/0 10.0.0.187/0 2 274 0 > >> 0 0 > >> 191 ip 0.0.0.0/0 54.76.66.39/0 1 40 0 > >> 0 0 > >> 193 ip 0.0.0.0/0 10.0.0.193/0 127 33068 0 > >> 0 0 > >> 197 ip 0.0.0.0/0 10.0.0.197/0 1 141 0 > >> 0 0 > >> 198 ip 0.0.0.0/0 10.0.0.198/0 58 15346 0 > >> 0 0 > >> 199 ip 0.0.0.0/0 10.0.0.199/0 4078 5472882 0 > >> 0 0 > >> > > > > > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org" > _______________________________________________ freebsd-ipfw@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw To unsubscribe, send any mail to "freebsd-ipfw-unsubscr...@freebsd.org"