Date: Sun, 17 Oct 2004 23:49:21 -0400 From: synrat <synrat@wirewalk.org> To: freebsd-questions@freebsd.org Subject: Re: dummynet Message-ID: <41733D41.6@wirewalk.org> In-Reply-To: <4172D346.4070601@mykitchentable.net> References: <416B29BC.6080108@wirewalk.org> <4172D346.4070601@mykitchentable.net>
next in thread | previous in thread | raw e-mail | index | archive | help
yeah it kinda seems broken. i can see the pipes being
hit by traffic, but no bandwidth limitation is done whatsoever.
I tried specifying dedicated port based pipes, that didn't work,
I tried using queues for port specification while specifying pipes
with the the same port numbers, that didn't work. I tried connecting
pipes to the queues, no result as well.
for example, to limit outgoing ftp, I tried this,
${fwcmd} add pipe 6 tcp from ${oip} 21 to any out xmit ${oif}
${fwcmd} pipe 6 config bw $2Kbit/s
no effect.
${fwcmd} add pipe 6 tcp from ${oip} 21 to any out xmit ${oif}
${fwcmd} pipe 6 config bw $2Kbit/s
${fwcmd} add queue 6 tcp from ${oip} 21 to any out
no effect.
${fwcmd} add pipe 6 tcp from ${oip} 21 to any out xmit ${oif}
${fwcmd} pipe 6 config bw $2Kbit/s
${fwcmd} add queue 6 tcp from ${oip} 21 to any out
${fwcmd} queue 6 config pipe 6
setsockopt error.
I guess it craps out when trying to bind queue to the pipe. Why ?? who
knows.... I really can't make much sense from what I've read about
dummynet in ipfw and dummynet man pages, if anyone knows of a good
manual, please let me know.
Drew Tomlinson wrote:
> On 10/11/2004 5:47 PM synrat wrote:
>
>> Can someone tell me about a good way to troubleshoot pipes/queues or
>> point me in the rigtt direction. I'm trying to restrict outgoing ftp
>> traffic and create some pipes for VOIP. dummynet and pipe rules load
>> fine ( and are in the kernel ) but seem to have no effect. I did read
>> the manual pages 20 times over. I tried adding pipes before doing
>> "config bw" on them, but that didn't make any difference.
>> thanx a lot in advance.
>
>
> I have tried using DUMMYNET also and don't see any effect. If you find
> an answer, please let me know. It's my goal to give highest priority to
> ssh connection, next highest priority to the traffic originating on
> machine "bigdaddy" port 8080, and then all remaining traffic gets passed
> when there's nothing else going on. I have DSL with a 128K uplink.
> Here is my rule set in case someone can find my error:
>
> # Flush before we define
> $fwcmd -f queue flush
> $fwcmd -f pipe flush
>
> $fwcmd pipe 1 config queue 128Kbyte
> $fwcmd queue 1 config pipe 1 weight 85 queue 8Kbyte
> $fwcmd queue 2 config pipe 1 weight 1 queue 112Kbyte
> $fwcmd queue 3 config pipe 1 weight 100 queue 8Kbyte
>
> $fwcmd add queue 1 ip from bigdaddy 8080 to any out via $oif
> $fwcmd add queue 3 ip from any 22 to any out via $oif
> $fwcmd add queue 2 ip from not bigdaddy not 8080 to any out via $oif
> $fwcmd add queue 2 ip from bigdaddy not 8080 to any out via $oif
>
> And I have these options compiled into my kernel:
>
> options IPFIREWALL
> options DUMMYNET
> options HZ=1000
>
> Thanks,
>
> Drew
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41733D41.6>