extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-24 08:33:40 +01:00
Code Issues Packages Projects Releases Wiki Activity

typo and date

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3078 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
judas_iscariote 2005-11-27 01:04:36 +00:00
parent a97a9bf59e
commit 37f238c36a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall-docs2/traffic_shaping.xml
View File

@ -21,7 +21,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2005-11-21</pubdate> <pubdate>2005-11-26</pubdate>
<copyright> <copyright>
<year>2001-2004</year> <year>2001-2004</year>
@ -107,7 +107,7 @@
<filename>/etc/shorewall/tcdevices</filename> file below). The next <filename>/etc/shorewall/tcdevices</filename> file below). The next
possible bottleneck might come if the packet leaves on another interface, possible bottleneck might come if the packet leaves on another interface,
so this will be the place where queuing might occur. So, defining queues so this will be the place where queuing might occur. So, defining queues
for incoming packages is not very useful, you just want to have it for incoming packets is not very useful, you just want to have it
forwarded to the outgoing interface as fast as possible.</para> forwarded to the outgoing interface as fast as possible.</para>
<para>There is one exception, though. Limiting incoming traffic to a value <para>There is one exception, though. Limiting incoming traffic to a value