Yes, making a copy and running it from post-firewall is the accepted practice. Here's how I currently do mine:
This will test if my version of wshaper exists and is an executable. If it is, it will call it and pass the ports as well. If not, it will call the original wshaper and pass just the speeds.Code:SPEEDS="2980 500" PORTS="20 21 22 25 110 143 80 443 587 995 5050 1863 5222 6667" [ -x /opt/app/local/bin/wshaper ] && \ /opt/app/local/bin/wshaper start $1 $SPEEDS "" "" "" "" "$PORTS" || \ /sbin/wshaper start $1 $SPEEDS
Of course, you should use speed values as appropriate for your connection. The ports are my own choices and you may find them useful: from left to right, we have FTP, SSH, SMTP, POP3, IMAP, HTTP, HTTPS, secure POP3 and SMTP, a few messenger transfer ports and finally IRC DCC.
As for the "u32" yes, it should have an u there. Mine does, I have no idea why it turned up missing it on the forum.



Reply With Quote


