Displaying 3 results from an estimated 3 matches for "mark_in_forward".
2002 Dec 21
0
Shorewall 1.3.12 Beta 2
...ulogd (available from
http://www.gnumonks.org/projects/ulogd) and log all Shorewall
messages to a separate log file.
6) If you are running a kernel that has a FORWARD chain in the mangle
table ("shorewall show mangle" will show you the chains in the
mangle table), you can set MARK_IN_FORWARD=Yes in
shorewall.conf. This allows for marking input packets based on their
destination even when you are using Masquerading or SNAT.
7) I have cluttered up the /etc/shorewall directory with empty ''init'',
''start'', ''stop'' and ''...
2002 Dec 27
10
Shorewall 1.3.12 Released
...to run ulogd (available from
www.gnumonks.org/projects/ulogd) and log all Shorewall messages to
a separate log file.
6) If you are running a kernel that has a FORWARD chain in the mangle
table ("shorewall show mangle" will show you the chains in the
mangle table), you can set MARK_IN_FORWARD=Yes in
shorewall.conf. This allows for marking inbound packets based on
their destination even when you are using Masquerading or SNAT.
7) I have cluttered up the /etc/shorewall directory with empty ''init'',
''start'', ''stop'' and '...
2002 Dec 19
4
Shorewall 1.3.12 Beta1
...to run ulogd (available from
www.gnumonks.org/projects/ulogd) and log all Shorewall messages to
a separate log file.
6) If you are running a kernel that has a FORWARD chain in the mangle
table ("shorewall show mangle" will show you the chains in the
mangle table), you can set MARK_IN_FORWARD=Yes in
shorewall.conf. This allows for marking incoming packets based on their
destination even when you are using Masquerading or SNAT.
7) Since adding commands to files that don''t already exist seems to be a
challenging notion for some users, I have cluttered up the
/etc/sho...