On 07/07/2010 15:57, Roger Lynn wrote: > It would be useful if it was possible to specify source and destination > ports separately in /etc/shorewall/tcpri
I'll provide a use case for for this bug, which I haven't previously, for future reference in case it is ever reviewed, or maybe there's a better way of doing what I would like (or maybe I'm just wrong). The reason for the bug is that I would like to give outgoing email (ie to a remote port 25) a lower priority than other traffic, while not affecting the command responses to incoming mail (ie traffic from local port 25). This should mean that my mail server appears responsive by quickly sending small command responses to servers trying to send me mail, but that potentially large outgoing emails shouldn't hog my ADSL connection which has relatively small upstream bandwidth. As I mentioned in another email, the other method for configuring traffic shaping appears to be excessively complicated for my needs. Thanks, Roger -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
